Planning
A plan is a set of documented agreements on what will be delivered, when, and by whom [1]. This area runs from the commitments a sponsor sees down to the tasks a team schedules, in the order they are usually made. How progress is measured against the plan belongs to Tracking.
- Planning approaches: why teams plan, and how predictive and agile plans differ.
- Milestone planning: results a sponsor can check, and how they get their dates.
- Activity planning: turning milestones into tasks and dependencies.
- Critical path: which tasks set the end date, and how much the others can slip.
- Gantt charts: the plan on a calendar, and what the chart hides.
- PERT and merge bias: three-point estimates, and why parallel paths finish late.
- Design Structure Matrix: work whose information loops back.
- Critical chain: scheduling around scarce people with pooled buffers.
- Resource planning: the hours that exist, levelling, and adding people late.
- Release planning: choosing what goes into each release when the date is fixed.
Acknowledgments
These pages adapt material from lectures by Eduardo Miranda [1] on software project management.
References
- E. Miranda,“Managing Software Development.” 2014.
Disclaimer: AI is used for text summarization, polishing and explaining. Authors have verified all facts and claims. In case of an error, feel free to file an issue.