The Software Project Playbook Vol. 2: Plans, Processes and Templates for Every Stage: 5 (Software Engineering Project Management)

Every software project that fails does so for the same reason. Not because the code was wrong. Because the management was inadequate. The processes were absent, the documentation was improvised, the risks were unacknowledged until they became crises. Behind every blown deadline, every overrun budget, and every client relationship that quietly collapsed, there is the same uncomfortable truth: someone needed this book and did not have it.

The Software Project Playbook, Volume 2 is the operational command centre for software project managers who are serious about delivery. Where Volume 1 established the foundational architecture — the project plan, quality plan, requirements specification, test plan, and the core technical documentation suite — Volume 2 hands you the instruments of control. These are the processes, protocols, and ready-to-use templates that govern everything from the first conversation with a prospective client through to the final post-project review. If Volume 1 is the blueprint, Volume 2 is the construction manual.

Built on the bedrock of IEEE software engineering standards and refined across four decades of real-world practice, this is not theory dressed up as advice. David Tuffley PhD spent twenty years delivering software projects at the coalface before spending a further twenty at Griffith University teaching the disciplines that separate consistently successful teams from perpetually struggling ones. What you hold is the distillation of both lives.

Eighteen comprehensive parts walk you through every dimension of project control. You will learn to initiate projects with clarity and authority, produce requests for quote that attract the right partners, and apply estimating methods that hold up under scrutiny. The document production standards alone — covering everything from writing style to version control — will quietly transform the quality of every deliverable your team produces.

But it is in the harder terrain that this volume earns its keep. Risk management is not a checkbox here; it is a living process. Change control is not a bureaucratic hurdle; it is the mechanism that keeps scope creep from silently dismantling a budget. Issues management, progress control, status reporting, procurement, and the management of development environments are all treated with the same rigour — grounded in process, expressed in templates you can deploy immediately.

The book culminates in the project end report: the often-neglected discipline of learning institutionally from what just happened, so that the next project begins wiser than the last.

There is also a practical philosophy threaded through every section. This is not a book that asks you to demolish your organisation's existing culture and replace it with something imported. It asks you to understand what your team already does well, and then augment it with proven structure. Resistance dissolves when people see that quality management makes their work easier, not heavier.

Whether you are a project manager navigating your first serious engagement, a team lead who has grown weary of ad hoc chaos, or a development director building process maturity across an organisation, Volume 2 meets you where you are. It will become the most annotated, dog-eared, relied-upon reference on your desk.

(If you have not yet encountered Volume 1, it covers the essential technical documentation suite — from software project plans and quality plans through to test plans and formal reviews — and pairs naturally with this volume to give you complete end-to-end coverage.)