Business Cases in an Agile World
The business case doesn’t have a great reputation. More often than not it’s viewed or treated as a sales pitch designed to get a project approved. In these cases, it might play down the costs and risks while overselling the expected benefits. That leaves project managers with too little time and too few people to deliver too many elements, and it leaves executives expecting the kind of contribution to their objectives that cannot possibly happen.
Fortunately, things are changing. Business cases are becoming more agile. I don’t specifically mean business cases for ‘large A’ Agile project delivery methods; I’m referring to ‘small a’ agile techniques and approaches being applied to the development of business cases, regardless of the approach being used to deliver that project. Here is where there are opportunities for all of us to improve the way business cases are done, perhaps even getting to the point where they are appreciated for the contribution they make to a successful project outcome.
A living document
The first thing I want to look at is the idea that a business case is a living document. I know that in theory this is what all business cases should be anyway, but in reality, that’s not what happens. Traditionally a business case is written with the intent of getting the project approved with a certain set of
Please log in or sign up below to read the rest of the article.