The Self Evident Truths of Project Management: Truth #4 - “We don’t do business cases to justify projects..."
- 19 May, 2009 09:40
- Comments 1
The Self Evident Truths of Project Management: Truth #4 - “We don’t do business cases to justify projects; we do projects to deliver business cases!”
Often the only connection between a business case and the project plan is the same project name on the cover page!
Business cases are used to ‘justify the project’ to get approval and funding. Then their work is done and they’re put on the shelf. They may be taken off the shelf again if a ‘post implementation review’ goes out to search for any benefits, but that’s about all.
Many projects even set up a small team to ‘generate the business case’ so that this job doesn’t get in the way of the project and its delivery.
Madness. Talk about upside down thinking. The business case should not be seen as peripheral to the project but should be seen its focal point — this (value) is what you’re trying to deliver.
The problem is that most business cases don’t define ‘what you’re trying to deliver’. They define the costs with just enough (financial) benefits to justify the investment. As a result the business case is largely irrelevant to the project.
So, we’ve got to change the business case and make it value-focused; centred around the value proposition. Then we’ve got to make the project plan value-focused; focused on delivering the value proposition. (Then we’ve got to track and measure the value’s realization, but that’s another story.)
So, we’ve got to go back to basics and reinvent the business case, to restore it to its original purpose — to define in detail the case, in terms of the business outcomes, benefits and value to be delivered, for investing in the project.
Then we can plan our project to deliver this value.
In doing this we can easily compute how much it costs to deliver each business outcome and its associated benefits and thereby optimise the investment — eliminating low value/high cost outcomes. We can objectively apply the 90-60 rule (obtaining 90% of the value for 60% of the cost).
We can then track the realisation of each agreed outcome, benefit and value through the project plan and from the business case.
As a result we can generate more net value for less cost. Sounds sensible doesn’t it? Focusing on value wins. It’s that simple.
© Jed Simms, Australia 2009. Jed@valuedeliverymanagement.com
Further support and useful tools to help you manage your investments, projects and portfolio are available from valuedeliverymanagement.com.
For the previous article in this series visit The Self Evident Truths of Project Management: Truth #3 - ‘Tangible’ Means ‘Measurable’ (Not Just ‘Financially Measurable’).
For other series of project management articles by Jed Simms visit How Do You Know if Your PMO is Successful and "PMO: What’s In A Name?".
Jed Simms is CIO magazine's project management columnist. Simms, founder of projects and benefits delivery research firm Capability Management, is also the developer of specialised project management and project governance Web site valuedeliverymanagement.com
Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.
- Bookmark this page
- Share this article
- Got more on this story? Email CIO
- Follow CIO on twitter
- Business Process Management, Service-Oriented Architecture, and Web 2.0: Business Transformation or Train Wreck?
- The Pathways ICT Leadership Development Program | Turning today’s ICT professionals into tomorrow’s business leaders | 2012 Course Curriculum
- Introduction to Storage Security
- Case Study - TNT Express successfully reduces their paper usage and costs using a new document solution
- FIBRE CHANNEL SOLUTIONS GUIDE - state of the fibre channel industry
-
iPad initiative for pupils in WA
-
All Systems Down
-
NBN to deliver disability support services to regional Australia
-
Beware of malicious QR codes: Report
-
Should you consider a generic top level domain?
-
Oracle IT Modernization Series Modernization: The Path to SOA
More and more organizations are looking to service-oriented architecture (SOA) as the basis of their future computer architecture. Recognizing that legacy application design and implementation approaches have led to applications that are costly to operate and maintain, hard to change, and rely on a dwindling set of skills, organizations are hoping that SOA provides a key component of the answer to these problems. Read on. -
Case Study: Understand How Edith Cowan University has Regained Control of their Storage Environment
Storage infrastructures continue to grow at alarming rates - up to 60% or more, annually. Like many organisations, Edith Cowan University was facing such rapid data growth, with its storage system capacity projected to double each year. Using IBM Tivoli storage solutions, the university has been able to reduce the number of physical disks required and make better use of their existing storage capacity, helping them to make more efficient use of the space in their data centre and reduce their spend on power and cooling. They now make space-efficient snapshots for failover and are able to recover systems in hours instead of days. -
IBM agility@scale™: Become as Agile as You Can Be
Agile software development is an evolutionary, highly collaborative, quality focused approach to software development where potentially shippable working software is produced on a regular basis. Agile software development processes include Scrum, Extreme programming (XP), Disciplined Agile Delivery (DAD) and Agile Modeling (AM), to name a few. Although agile approaches are often equated to the development of Web-based applications, in reality they’re also being applied to mobile applications, fat-client applications, business intelligence (BI) systems and even mainframe applications. They’re being applied by a range of organizations, including but not limited to e-commerce companies, financial companies, manufacturers, retailers and government agencies.
-
Objects, Abstraction, Data Structures and Design
-
Excel Charts
-
Creating Web Graphics for Dummies
-
Photoshop Elements 5 Workflow
-
The Unofficial Guide to Outlook 2007
-
Building J2EE Applications with IBM Websphere
-
Mac OS X Panther Timesaving Techniques for Dummies
-
Syndicating Web Sites with RSS Feeds for Dummies
-
Virtualizing Microsoft Tier 1 Applications with Vmware Vsphere 4









Comments
Project Management Hut
Unique point of view...
The
Unique point of view...
The business case, itself being a project, is something quite common when it comes to large projects.
I have published an article on <a href='http://www.pmhut.com/building-a-projects-business-case'>building the business case</a>, going through this article, it is very obvious that sometimes it takes a lot of time to come up with all the data to justify a project, so, justifying a project can indeed turn into a project itself, although the business case of the latter is obvious...
Post new comment