Project Management
Parts I–VII covered the technical craft of building a digital product. This Part covers the process discipline that determines whether that craft is pointed at the right problem, delivered on a workable timeline, and coordinated across a team — requirements, roadmaps, agile process, and quality assurance as an organizational function.
Start Part VIII — 8.1Requirements Gathering & Discovery
The stage every failed project skipped, and every successful one spent real time on.
8.2Roadmaps & Wireframes
Two artifacts that translate discovery into something concrete enough to plan and build against.
8.3User Stories & Backlogs
The unit of work that keeps a team focused on user value rather than technical tasks in isolation.
8.4Agile, Scrum & Kanban
Three related but distinct terms that get used interchangeably far more often than they should.
8.5Sprints & Milestones
The rhythm that turns a backlog into actual, regularly-shipped progress.
8.6Risk Management
Identifying what could go wrong while there's still time to do something about it.
8.7Quality Assurance Processes
Quality as an organizational process, not just the automated tests covered in Part VII.
8.8Stakeholder Management
The Part's closing chapter — a project can be technically excellent and still fail if the people who need to be aligned aren't.