Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Agile Project Commitments  Agile Project Commitments   Project ownership Commitment   Project ownership Commitment

The business driver behind the proposed project has been clearly and unambiguously communicated, obvious, accessible and available to all project team members.

let us explain this. The business driver is the reason why we are doing the project. it is the goal, the objective and it is the final endpoint we are aiming for. It might be that the business driver is that the organisation requires a new and flexible marketing tool to deliver a measure of recognisable improvements in say an organisational brand. It is of course always important to quantify and clarify these sorts of statement to remove ambiguity.

So looking at this business driver we will want to know exactly which organisation we are talking about. We would want to know what we mean by the word new. Is this new to the organisation or is this new to the market place or is this new blue skies software? We would want to know what we mean by the word flexible. What level of flexibility do we demand? We would want to quantify the recognisable improvements. In other words what sort of improvements are we seeking and how are we going to demonstrate that we can recognise them? We would need to know a little bit more about the brand. What is the catchment area or focus group who will demonstrate the recognisable improvements in that brand?

Often times the driver is quite simple. We want a new customer system that works during business hours. that is a little easier to measure and demonstrate.

We would suggest that the business driver is at the very least sent in an e-mail to the project stakeholders. In this way it is communicated to all members of the team and they will be able to confirm they received and understood it. Maybe you will demand a reply to confirm?

You may want to go one further and have a poster printed which is displayed around the project rooms. You could have an electronic graphic produced which would be assigned as the wallpaper on your client workstations. The stakeholders could never contest that this level of communication was not visible! Whatever you choose to do to communicate the business driver is up to you. Evidently you will do it so as to eliminate debate about it.

Now the tough part is getting an Engagement Commitment Owner to own the Commitment. The Engagement Commitment Owner will know and be able to elucidate the business driver. They will be able to differentiate the business driver for other similar initiatives and defend it, if or when it is challenged or jeopardized. They will be able to clearly communicate the business driver and evidence that they have unambiguously done so. Finally they can make sure or delegate someone else to make sure the business driver is evident, reachable and on hand to the whole project team.

Frankly all someone needs to do is send this in an email to the team and spend a little time with selected team members making sure the message and objectives of the business driver are clear. Then, print out the key messages and pop them onto message boards around the office. That is the job done. This way the Owner does not Accept but they can Confirm this Commitment is achieved. It is their responsibility to make sure this is clearly provided to current personnel and new entrants to the project, going forward. Put like this, it is easy.

Right Let us look at another one.


 Agile Project Commitments     Agile Project Commitments   Project ownership Commitment    Project ownership Commitment

Glossary:     a  »   b  »   c  »   d  »   e  »   f  »   g  »   h  »   i  »   j  »   k  »   l  »   m  »   n  »   o  »   p  »   q  »   r  »   s  »   t  »   u  »   v  »   w  »   x  »   y  »   z

#personas  »   #artefacts  »   #archetypes  »   #patterns  »   #change  »   #personas  »   #increasingoutput  »   #reducingvariation  »   #improveefficiency  »   #abstraction  »   #predictionandcontrol  »   #management  »   #organisations  »   #socialnetworktheory  »   #failfast  »   #quality  »   #waste  »   #complexity  »   #learning  »   #adapt  »   #inspect  »   #improvement  »   #models  »   #complexadaptivesystems  »   #informationflow  »   #sytemsthinking  »   #butterflyeffect  »   #unpredictability  »   #chaos  »   #emergence  »   #emergentbehaviour  »   #distributedcontrol  »   #continuousimprovement  »   #complexityscience  »   #gametheory  »  
 Agile In 6 Steps    |    Projectivity    |    Instant Agile    |    Risks    |    Auditing Agile Projects 
Big Agile Toolkit Book (Amazon Japan)   |   Big Agile Toolkit Book (Barnes and Noble)
Buy the Big Agile Toolkit Book   |   Buy the Big Agile Toolkit Kindle eBook
Business driver Commitment


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
Topic: 255  Page: 382/444  Progress: 86.0%
 About    |    Author 
Follow @BigAgileToolkit

This content can be copied to third parties for personal use if you acknowledge the source of the material with website URL ( and Twitter hashtag (#BigAgileToolkit).
In all other cases, no part of bigagiletoolkit or associated text or website may be copied reproduced or redistributed in any form or by any means without prior permission in writing from the author.
Agile Project Governance for Cost Conscious Companies™

All rights reserved.