Digital Production Management - Risk vs Value
There are numerous gems I've learnt during the read, the one I'm going share today is actually an old concept to me, but a very valuable one. The process of risk vs value definition.
Using a simple diagram, which I've included below Mike describes the process of risk vs value assessment on a project.

Source: Mike Cohn "Agile Estimating and Planning"
Knowing this kind of information allows you to prioritise attention to your projects deliverables, with the high-risk/high-value items ideally being dealt with first. Perhaps low-value/high-risk items being dropped from your production schedule all together.
The arrow in the diagram illustrates the order of delivery priority, moving through three of the sections, but avoiding the high-risk/low-value section altogether.
The analysis of risk like this is usually most relevant on larger projects, although risk analysis in some form should always be considered when planning any project.
Risk can be broken down into many elements, but for the sake of the book Mike Cohn breaks risk down into the following types:
- Schedule risk - "We might not get this done by . . ."
- Cost risk - "We might not be able to buy/hire that resource for . . ."
- Functionality risk - "We might not be able to get that to work . . ."
I could write a whole post on risk, but I'm not going to go there today so back to the risk vs reward profiling.
I'm currently working with a very tight scheduled project of a relatively small scale, but prioritising tasks like this with this particular project was essential due to the immoveable delivery date. This can occur in web development often, usually when projects are just one element of a larger marketing campaign.
Larger projects can come with endless production wish lists that would deliver functionality beyond what was originally required. Sifting through these wish lists and matching them against the original project objectives and then classifying the risks against their delivery can be an invaluable operation.
The wish lists are not always just the creation of the client either; you'll often find development and design teams trying to add elements to a project they think might be desirable that could skew your delivery times.
Following this simple operation can ensure you deliver to your client what they originally wanted on time and to budget without being too distracted by "would be nice to have" additional elements that can be very time consuming.
Mike talks about this process in his chapter about prioritising themes. The other themes he covers when calculating project priorities are "New Knowledge" and "Cost", which combined with "Value" and "Risk" you should be able factor all elements of any project more accurately.
It's rare in any project we get the chance to include all the features and functionality that we might wish to, so considering these factors is essential.
It's simple process that a trained production/project manager can generally do by themselves at the early stages of a project kick off. But if your unsure of any element, go back to your team for further details.
Early stage planning like this can save a lot of worry later in projects; we should all take the time to consider risk vs value.
Related links:
Managing expectations - Keep everyone happy - Digital Signals http://www.digital-constructions.com/blog/2009/06/managing-expectations-keep-everyone.html
Have you got time? - Project managing time - Digital Signals http://www.digital-constructions.com/blog/2009/04/have-you-got-time-project-managing-time.html
Methodologies - Don't let yourself get boxed in by them - Digital Signals http://www.digital-constructions.com/blog/2009/08/methodologies-dont-let-yourself-get.html
Stay calm and be patient - The inner calm of project & account management - Digital Signals http://www.digital-constructions.com/blog/2009/10/stay-calm-and-be-patient-inner-calm-of.html
Labels: digital project management, production management, project management, risk analysis, value analysis
blog comments powered by Disqus





