Waltzing with Bears
About this book
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 reserves, and it makes the case for expressing a delivery date as a distribution rather than as a single confident number. There is a chapter on the risks that turn up on nearly every software project, including specification breakdown, scope inflation and turnover. The authors are blunt that a project with no risks worth managing is a project not worth doing.
Description via Product Digest.
Topics
Related concepts
- The external environmentEnterprise environmental factors and organisational process assets in plain terms, the routes by which market, regulatory, supply chain, geopolitical and economic change reach a project, and what to do about the things a project cannot control.
- Project risk managementRisk is uncertainty with an effect on an objective, and the effect may be positive, so the same identification, analysis and response machinery serves threats and opportunities alike.
- Issues and the RAID logRisks, assumptions, issues and dependencies in one place, why the boundary between a risk and an issue is the one that matters, and what keeps a log usable.