Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Roles and responsibilities Commitment  Roles and responsibilities Commitment   Technical working Commitment   Technical working Commitment

The business team will satisfy the business working demands of the project.

This is so simple but so important. You need your business people when you need them. You need your business to answer questions immediately. There will be times when business representatives are unable to answer a question immediately or even answer it at all. This is not ideal. What you need is the support of your business sponsor to make sure you have knowledgeable business representatives, empowered and experienced to resolve day-to-day project challenges and questions. It is a simple, but therefore a vital, Commitment.

The Commitment requires definition and will define what the business working demands of the project are. The whole Toolkit is based on the principle of business led ideas during the development and the project cannot deliver it without their input, judgments and decisions.

We can imagine a series of scenarios where the lack of business input will impact our project delivery. We need business subject matter experts present during our estimating stages. We want to make sure we have identified the full scope, the level of quality and depth of the deliverables and the amount of effort to derive them. We need them to assess and decide on the level of risk and the mitigation of that risk.

We will demand business involvement in the planning stages, in the identification of our key requirements, in the setting of priorities, in the validation of fit for purpose deliverables and in the sign off and implementation of our final delivery. If we choose to perform a review of the delivery and of the processes to achieve this, we will need business involvement too.

Your business representatives will be available and accessible to the team, able to decide for them when points of order, business policy, procedure, project priority and questions arise. They will be able to do this for themselves without constant need to revert to their peers or management. The business team also need to have appropriate skills and expertise to carry out their role as well as suitable soft skills such as communication, negotiation, an ability to work under pressure and work effectively with other project members respectfully.

There are a number of ways you can record and monitor this. We use a method to record project events based on business attendance. It is important to point out at this juncture that, of course, simple attendance by a business team member is not enough. You need value adding contributions.

We described earlier that we need business representatives knowledgeable, empowered and experienced to provide this added value. By agreeing to this Commitment the owner of this Commitment takes accountability for the provision of this type of learned personnel.

The method has Failure To Assist (FTA) events. The project needs to spend some time to identify project events where failure may take place. We have identified the main ones earlier in this Commitment. But your list is the list for your project and some time spent creating the list is important if you want to monitor performance of the Commitment.

State the project business attendance events and define a FTA Threshold. Then manage it. The threshold is set in collaboration between the project sponsor and project manager. Your project has defined its business scope so your business sponsor knows the type of skills your project requires and the business subject matter areas to support.

Failure to provide enough skilled personnel to assist the events is classed as an FTA event, added to the latest number of FTA events for the project and compared to the FTA threshold. In our experience, when a threshold goes into double figures there is a problem. Believe the adage: double is trouble.

By monitoring the FTA events and communicating the total to the business sponsor you are seeking to reduce the frequency of such failure events. This will have the effect of promoting the genuine and enthusiastic involvement of the business. Thus you deliver an enthusiastic collaboration which has a greater chance of successful delivery and two concepts that work.

We tried another method which was simply based on email. We would simply email when business attendance was deemed to be expected (though of course not agreed and written down) but did not occur. We found that although it was easier to perform it tended to have less of an effect. Maybe this is due to the fact that many managers receive acres of email and it is not seen as something out of the ordinary. A manager waving an FTA threshold and a list of failure events is something unusual and draws attention, maybe?

So we made Commitment demands on the business, now it is our technical community.

Buffer



 Roles and responsibilities Commitment     Roles and responsibilities Commitment   Technical working Commitment    Technical working 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 working Commitment






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 258  Page: 385/444  Progress: 86.7%
 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 (http://www.bigagiletoolkit.com/) 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.