Value Driven Delivery

This content is syndicated from LeadingAnswers: Leadership and Agile Project Management Blog by Mike Griffiths. To view the original post in full, click here.

(This post, a draft sample from my upcoming PMI-ACP Prep book, takes a look at the “Value Driven Delivery” domain.)
Value, specifically the delivery of business value, is a core component of agile methods. This concept is woven into the agile DNA with its inclusion in the Agile Values (“Working software over comprehensive documentation”) and the Agile Principles (“Working software is delivered frequently” and “Working software is the principal measure of progress”). The focus on delivering value drives much of the agile activities and decision making on a project, and it manifests itself in many of the Tools and Techniques (T&T) and Knowledge and Skills (K&S) used. The focus on value is such an essential component of agile methods that the “Value Driven Delivery” domain has the most T&T and K&S of any of the 6 domains. This means we are starting with the biggest section early in this book.

What Is Value Driven Delivery?
Let’s start by defining value-driven delivery. The reason projects are undertaken is to generate business value, be it to produce a benefit or improve a service. Even safety and regulatory compliance projects can be expressed in terms of business value by considering the business risk and impact of not undertaking them. If value then is the reason for doing projects, value driven delivery is the focus of the project throughout the project planning, execution, and control processes.

It is the big picture view, the wearing of the sponsor’s hat when making decisions. By the project manager and team assuming this viewpoint, there is an opportunity to incorporate unique technical insights, such as technical dependencies or risk reduction steps, into the selection of features for a release that the sponsor may not be aware of. However value driven delivery remains a guiding vision for much local decision making, the selecting of choices that maximize the value delivered to the business or customer.

Risks as Anti-value
Risks are closely related to value. We can think of project risks as anti-value, i.e., things that can erode, remove, or reduce value if they are to occur. If value is the heads side of a coin, then risks are the tails side. To maximize value we must also minimize risks, since risks potentially reduce value. This is why the Value Driven Delivery domain addresses many risk reduction concepts and techniques.

Here’s another way to think about this concept. Consider value driven delivery to be like credits or deposits being paid into your bank account. Risks, or at least risks occurring (issues), are then like withdrawals or charges being taken out of your account. We want to maximize the inflow and minimize the outflow to create the most value.

Eat your Dessert First - Early Value Delivery
Agile methods promote early value delivery. This means aiming to deliver the highest value portions of the project as soon as possible. There are a number of reasons for this approach. First, life is short, weird stuff happens, and the longer you run a project, the greater the horizon of risk for failure, reduced benefits, opportunity erosion, etc. So to maximize success, aim to deliver as much good stuff as soon as you can before things change or go sideways on you.

The second major reason is that stakeholder satisfaction plays a huge role in project success. Engaged, committed sponsors and business representatives who support a project are vital to removing project obstacles and defining success. All project teams are on a “trial” period when they start, as sponsors may not be convinced the team can deliver. By delivering high value early, the team demonstrates an understanding of the stakeholders’ needs, shows a recognition for the most important aspects of the project, and displays an ability to deliver. Results raise stakeholders’ confidence, build rapport, and get stakeholders on board early, creating virtuous circles of support.

Chartering – Chartering in agile projects has the same general goal, but a different level of detail and set of assumptions. The goal of a Charter is still to describe the project at a high level, gain agreement into the W5+ (What, Why, Who, When, Where and How) attributes of the project and give authority to proceed. However, since agile methods are often used on projects with uncertainty around requirements / technology, and high rates of change, there is typically less certainty around scope.

In general agile charters have less detail, are shorter documents, and focus more on how the project will be run than what exactly will be built. This is because when aiming at a static target (unchanging requirements / technology) it is appropriate to plan, plan some more and then execute. In the dynamic and moving target environment of an agile project lots and lots of planning may not be appropriate if elements of the project are likely to change. So, when aiming at a moving target, we need to allow for mid flight adjustments and ensure the processes (prioritization, demos, retrospectives, etc) are in place to allow for them.

Elements of agile that may be different for an organization, for instance, welcoming changes and then prioritization of approved changes into the backlog, should be clearly outlines in the charter. This is especially important if the organization is new to agile and this may be a departure from how changes were handled in the past...

“This article is taken from the upcoming RMC “PMI-ACPsm Exam Prep” guide. Sign-up for notifications and pre-order offers here. This article is protected under copyright © 2011; all rights reserved. Except as permitted under the United States Copyright Act of 1979, no part of this article may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system, without the prior written permission of RMC Publications, Inc. You can link to the article here from another website, but not reproduce the content elsewhere.”

2 Responses to “Value Driven Delivery”

  1. Keydrick says:

    More posts of this quatliy. Not the usual c***, please

  2. Kelly Waters says:

    Ironic that you spelt quality wrong, especially given the nature of your comment :)

Leave a Reply

What is 5 + 6 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”