Task Descriptor: Plan the Project |
Define a coarse-grained plan for the project.
Based on Method Task: Plan Project
Purpose
To describe a roadmap that provides direction to the team and continually adapt it based on feedback and changes in the environment.
Relationships
Roles | Main: Project Manager | Additional: Analyst Architect Stakeholder Tester | Assisting:
Inputs | Mandatory: Vision Work Items List | Optional: Project Plan Risk List | External: None
Outputs | Project Plan Risk List Work Items List
Steps
Evaluate risks
The project manager evaluates project risks with the team and updates the Risk List. The risk list will aid the team in prioritization of what to do in which iteration. Higher-ranked risks are tackled and planned for earlier iterations then lower-ranked risks.
Determine project size and scope
Analyze the size and the Vision of the project, and whether it is realistic to deliver what is asked for within the constraints of the project. If the project is feature-driven, meaning that release criteria is defined as a set of features captured in the Work Items List, the team assesses the size of these work items, see Guideline: Agile Estimation. They then look at how many people they would need to complete these work items, which gives them a ballpark understanding of project duration, staffing profile, and scope. If the project instead is date-driven, the team assesses how much work can roughly be done in the time-frame given and using the available team, captured as a candidate list of work items. The end result of the two approaches is the same; a rough understanding of the size of the capabilities to be delivered, the size of the team, and expected time of completion.
Define length, number, and objectives of iterations
Determine iteration length, see Concept: Iteration, or use 4 weeks as default iteration length. Use iteration length to assess target velocity, see Guideline: Agile Estimation. Based on the target velocity and overall size of the project, calculate the number of iterations required. Determine 1-3 high-level objectives of each iteration, The goal is to create a high-level plan outlining how you can build the resulting application in the given set of iterations. The plan will change as you learn more, so time-box this analysis to a few hours or less. Use the Work Items List to outline what features to implement in what iteration, putting top priority work items first. This can be done rapidly by leveraging expected velocity and size estimate of work items. Produce a brief summary of your analysis in your plan by documenting 1-3 objectives for each iteration. Do not commit individual work items to the plan, since this will force too much re-planning. For some projects, you may have to wait until after the first iteration until you can provide a meaningful plan at this level of detail.
Map roles to team members
The project manager assigns project members (people) to roles according to a table like this:
Team Member | Analyst | Developer
John | X |
Judy |  | X
Jim | X | X
The project manager needs to make sure that the roles are staffed according to skills and interests and that every role is covered.
Properties
Multiple Occurrences |
Event-Driven |
Ongoing |
Optional |
Planned |
Repeatable |
More Information
Concepts | Milestones Risk Management Iteration
Guidelines | Agile Estimation
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. View copyright information here: OpenUP Copyright