Stage planning

Chapter 12

Stage planning is where we map out the detailed course of action for a stage to be permermed at the start of each stage delivery cycle. The project team creates an individual stage plan that describes how to conduct detailed design, coding, technical reviews, tests, integration and other activities during the stage. The most labor intensive planning activity is the creation of a list of miniature milestones, which helps the team track progress throughout the stage.

Each stage in a project using the staged delivery approach is essentially a miniature project.

w2std7a

Squidward with the rest of the sponge bob squarepants staff ready to begin stage planning. Colorized circa 1999.

  • Stage planning is a taxiing task, we want to make milestones for the next activities.
    • Requirements updates. in the early stages requirements to be implemented during the stages should be exactly what the project team specified during prototyping and requirements development. Later time should be allocated at the beginning of each stage to evaluate possible changes to requirements.
    • Detailed design. This is to be done near the beginning of each stage, developers flesh out the detailed design.
    • Construction.
    • Test case creation. This is to be created at the same time that the developers are working on a stages construction.
    • User documentation updates. The user manual/requirements specification is updated to describe the as-build software.
    • Technical reviews. This begin in earnest during the post-architecture period.
    • Defect corrections. Developers correct the defects uncovered by testing and reviews.
    • Technical reviews. 
    • Technical coordination. Meetings between developers, testers and architecture designers.
    • Risk management. The project manager should review the project current top 10 risks list and determinate whether the current project plan adequately addresses the current risk.
    • Project tracking.
    • Integration.

jqeu7xq

Tired yet? Have a picture of a cute doggo.

In addition to their project tracking benefit, miniature milestones help the team to focus on the most important tasks. When only long-term milestones are used. the developers can easily lose a day here or a week there people spend time on detours that seem interesting or productive in some vague sense but fail to move the project forward.

How does a project get to be a year late?… One day at a time.

Frederick P. Brooks.

To close this chapter I would like to add that all of this planning is a warning for the future of the release of the project to always documents the milestones and document the ones that have been reached. If we do as follow future can’t stop us.yvvy86j

Squidward dealing with the humans inner fears. 

Bibliography

McConnell, S. (1998). Software Project Survival Guide. Microsoft Press.

Author: enroblog

Computer science student at ITESM

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: