Process
A process is what a team actually does to build software: the steps, who performs them, and how anyone knows a step is finished. This area covers how to define one, how to measure it without damaging it, and how to choose the shape a project runs in.
Three groups of pages, in the order they are taught:
- Basics — where process thinking came from, how to define and measure a process, and what measurement does to the people being measured.
- Lifecycles — the phase structures a project can run in, from waterfall through to the risk-driven spiral, and when each is the right shape.
- Frameworks — Scrum, XP, Kanban and the rest: reusable structures of roles, events and practices, how they scale, and how to choose between them.
If you read only one thing here, make it process metrics. Choosing what to measure is a design problem; deciding who sees the result is a management one, and it is the second that goes wrong.
Acknowledgments
These pages adapt material from lectures by Eduardo Miranda and David Root [1] on software project management.
References
- D. Root,Managing Software Development. Carnegie Mellon University / Innopolis University lecture series, 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.