Risk Posts

The Pied Piper of Requirements

Posted: February 28th, 2012 by Bob Prentiss. 2 Comments »

Pied PiperBobtheBAI see and hear it all the time – Business Analysts make reference to their business partners saying, “they never know what they want”, “they keep changing their requirements again and again”, or “once again I led them to water”. Powerful statements. Disturbing statements for many reasons. Is it a lack of maturity of the business, the BA, or both? I have worked with, mentored, or coached many BAs in this situation and often the response or story that comes back to me is that they (the BA) would not have any requirements at all without first “leading” their business partners to water. I certainly understand the frustration as eliciting requirements is not easy! However, when I do hear the “lead to water” type statements, the first thing that always comes to my mind is the story of the Pied Piper, and what a dangerous tale it is.

The Pied Piper. The dictionary defines the Pied Piper as “a leader who entices people to follow (especially to their doom)”. If only it were not for that second part! I encourage and teach that all BAs be leaders in their domain; however, the leadership of the Pied Piper is not the kind of leadership that really works long-term or one that should be emulated (ends in doom you know). The story of the Pied Piper is that the Piper is a rat-catcher hired by a town to lure away some rats (with a magic pipe). The town refuses to pay the Piper for said service and the Piper retaliates by luring their children away (just like the rats), never to be seen again. Very doom and gloom and no one wins.

Things We Know and Things We Don’t

Posted: September 27th, 2011 by Andrea Brockmeier. Comments »

Knowns-Unknowns_MatrixOn every project there are things we know and things we don’t know – Knowns and Unknowns.  Organizing your thoughts around those concepts can be a constructive approach to understanding a project as shown in the matrix.

The Known Knowns you handle via the plan, but what about those various flavors of Unknowns?  How do you normally account for those things in the project?  Often it’s with padding – estimates that include unidentified amounts of time and/or money just in case

Project Risks? So What?

Posted: June 14th, 2011 by Andrea Brockmeier. Comments »

So What?In my last ProjectBrief post, I talked about the importance of clearly identifying risks as events and making sure they aren’t simply stated as facts.  Here I’d like to briefly highlight the importance of including the consequence of those identified risks in the risk register.

Risk registers often include risks with little or no indication as to the consequence. Take a look at the register below, for example:

Risk Event Prob 1-5 Impact 1-5 Risk Score PxI
Scheduling classes on new site fails to work with the ISP’s new online scheduling services when going live. 3 5 15

What is a Risk?

Posted: May 24th, 2011 by Andrea Brockmeier. Comments »

Fire_Danger_RatingThese next few weeks I will be sharing thoughts about Project Risk Management. 

In my training experience, I find that most people know what risk management is, but many people struggle with identifying risks.  Often, people create a list of risks that includes things like “The infrastructure is outdated,” or “We aren’t sure how much Sam will be available for the project.” 

These are certainly concerns that we should be thinking about, but are they risks? I would suggest that no, they aren’t.  The first one is simply a statement of fact; the second one is an uncertainty.  Risks may derive from circumstances or uncertainties like these, but the most effective way to articulate a risk is to express it as an event.  It’s something that could happen