Difference between revisions of "Development Planning"
(→What) |
|||
| Line 3: | Line 3: | ||
Development plan | Development plan | ||
| − | [[Image: | + | [[Image:DevelopmentPlanning.png|300px]] |
== How == | == How == | ||
Revision as of 21:17, 6 January 2013
What
Development plan
How
The dish
Development Plan
Ingredients
- All artifacts produced in the Preproject Phase so far.
- Experiences and metrics from previously performed projects.
Process
From the documentation produced and experience gained during the Preproject Phase compile a table containing the activities that should be performed during the Launch Phase. Create a table with three columns. Name the first column Name, the second Estimated cost and the third Prerequisites.
From the description of the objects-to-analyse examine previous projects to obtain experience about the time needed to analyse and describe an object alike; include any other cost required (prototype development, meetings with the customer, or user representatives, purchase of components, external testing or verification, etc). Eventually, do this work in cooperation with a more experienced colleague or the project management. While taking this journey in the past, also note what prerequisites (meeting rooms, projectors, tools, testing facilities, etc) were necessary to analyse the object and note those found in the Prerequisites' column.
When all objects-to-analyse which have predecessors, have estimates and possibly prerequisites filled, it it time to look at the few left open. Apparently, there has not previously in the company's history been objects alike and therefore some extra effort is needed to get a relative estimate.
To estimate on objects that have no previous predecessor in the company's history, you typically examine the object description thoroughly and decompose the object into smaller pieces describing each piece more detailed. Redo this work until the object has been decomposed into satisfactory small pieces that can be estimated with the necessary precision.
If the analysis involves a larger project that could not be analysed within a few weeks, then spilt the analysis into timeboxes just as the development is timeboxed. Then decide the length of the timeboxes. Typically, a timebox period should be in the time frame of 2 to 4 weeks.
Each timebox should contain a deployment of the analysis results attained so far. It is important to deliver results to the customer frequently both to ensure that the customer realises that the developer is working on the matter and most importantly to get feedback from the customer.
If the estimates are within 1 to 3 weeks, there is normally no need to set up a more sophisticated development plan in a project management tool. On the contrary it could be a waste of time.
If the estimates suggest a longer Launch Phase, create a project in the project management tool with the activities scheduled relative to project start.
Why
The Development Plan expresses the expectations the developer has to the realisation of the project.
The plan is necessary for several reasons including estimation of cost, resource planning and project progress follow-up.
The first use of the Development Plan is the estimation of the cost realising the project.
Secondly, when the customer accepts the quote, development can start when all necessary resources are available. Resources are typically staff, but can also include other types of resources like development equipment, test facilities, prototype production facilities, etc.
During development the Development Plan is the basis for the project management.
Example
An example of an incomplete development plan.
