Strategy, discovery, metrics, growth, pricing, design, delivery and leadership. Each entry says when it is the right one to pick up.
Flyvbjerg spent decades assembling a database of large projects and their outcomes, and with Gardner turns that evidence into a short set of rules. The central finding is that big projects fail because planning is rushed and delivery is slow, when the reliable pattern is the reverse.
Kendrick works through risk in the order you meet it on a project, starting with scope risk, then schedule and resource risk, then the analysis and response planning that follow.
Shostack turns threat modelling into something a delivery team can do rather than something a specialist performs on their behalf. The method is built around a short sequence of questions, starting with what you are building and …
DeMarco and Lister on why software organisations avoid naming their risks and what that avoidance costs them. The book sets out a working risk management process covering identification, exposure, containment and the use of risk …