Explanation - how can you have a design milestone as the last piece of work on a project?

Explanation  - how can you have a design milestone as the last piece of work on a project?   13-16th Dec.

Further to Friday's WIS notes, you had a couple of items you would like more information on:

 1.            FIN092  Corporate Planner PICCL 10 regarding priority change 'WIS comments: PM to explain what milestones will follow the Technical Design milestone' The remaining milestone is the 'Deployment Signoff and Closure Milestone' which has a due date of today. The report is being circulated for Closure currently and I will be chasing it up on Wednesday to see if there are any remaining points holding this project up.

WIS Query  I think the question about the FIN092 project was, how can you have a design milestone as the last piece of work on a project?  Normally a design milestone is signed off before the build.  As I understand it, this milestone is to document the design learnt from the implementation.  It would be useful to have the explanation documented somewhere - e.g. in the description of the milestone itself

Answer This project has had to be carried out in a very unusual manner as Corporate Planner only exists in LIVE and there were FEC and TRAC Return  deadlines for mid October. That was the essential requirement that we had to achieve before progressing any other work.

This meant that the documentation for the Corporate Planner system had never been documented as it had not been supported by IS Apps officially before. This project ensured that the requirements of going through a usual process of Dev, Test, and  Live were not done and the documentation had to cover what was needed to support the Management Accountants in Corporate Planner.

So it was at the end of the project that some other notes had to be completed, sorting out to enable Tech Man and Apps Support to be able to support the Corporate Planner Team. It was only when this was completed that the project could move to Closure