Long ago there were a set of small books from the Software Program Managers Network and Norm Brown's work on Industrial Strength Management Strategies, which was absorbed by an organization which is no longer around. I have all the Little Books and they contain gems of wisdom that need restating in the presence of the current approaches to software development and hype around processes conjectured to fix problems.
The Software Program Managers Network produced books. I have 7 of them.
- Little Books of Configuration Management
- Project Breathalyzer
- Little Book of Bad Excuses
- Little of Testing Volume I and II
- Condensed Guide to Software Acquisition Practices
- Little Yellow Book of Software Management Questions
Let's start with formal risk management. There was a twitter post yesterday asking about the connection between Agile development and Risk Management. Agile is a participant in risk management but it is not risk management in and of itself.
From Bad Excuses book, here's a list for Risk Management and the Project Breathalyzer where these items live in a larger context
- What are the top ten risks as determined by the customer, technical, and program management?
- How are these risks identified?
- How are these risks resolved?
- How much money and time has bee set aside for risk mitigation?
- What risks would be classified as showstoppers and were these derived?
- How many risks are in the Risk Register? How recently has the Risk Register been updated?
- How many risks have been added in the last six months?
- Can a risk be named that was mitigated in the last six months?
- What risks are expected to be mitigated or resolved in the next six months?
- Are risks assessed and prioritized in terms of their likelihood of occurrence and the potential impact to the program?
- Are as many viewpoints as possible involved in the risk assessment process?
- What percentage of the risks impact the final delivery of the system?
- To date how many risks have been closed out?
- How are identified risks made visible to all project participants?
No matter the development method - agile or traditional - risk management is how adults manage projects (Tim Lister). No risk management no adults at the table.