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 has no requirements gathering  Agile has no requirements gathering   Waterfall Scope is the same   Waterfall Scope is the same

Again on a recent project we were told by a very experienced manager that in his view scope is not important on an agile project; you can change your mind on a whim and dart off into different areas of the business when the mood takes you.

Well Let us think about this statement. Can this be true? In the words of the famously wise and erudite anti-hero from the sitcom of the same name Mr. Blackadder: Yes… and No. Let us try again shall we?

Yes, you can change your mind on a whim and dart off into a different area of the business when the mood takes you. However, this will be performed with business approval, with their direction and the change will be based on sound business judgment. However you are not expected to be darting off into an area of the business outside the original scope of the project and there is good reason for this.

Organisations are often large beasts. When you define your project, a learned group of your organisations personnel within the change board assessed the change and the proposal and felt that, within that particular part of the business, this particular change warranted financial and other resource to deliver the proposed benefits. They will be knowledgeable of other similar projects in neighbouring business areas already financed to deliver similar or maybe conflicting functionality for sound business reasons. The basis for acknowledging the project you defined was performed using the scope provided.

Almost certainly going outside a boundary established under such logic will likely influence the costs or benefits and could undesirably contest the basis for the acknowledgement of the original project. However, if a decision to extend or change scope is based on this business knowledge and this is confirmed to be the proposed will of the project and the business, then the agile approach supports this intention. Document any changes this makes to the Delivery Plan and Release Plan, as well as to a new version of the Approved Change Proposal and move onto other more financially beneficial project work.


 Agile has no requirements gathering     Agile has no requirements gathering   Waterfall Scope is the same    Waterfall Scope is the same

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
Scope is not important in Agile


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
Topic: 429  Page: 431/444  Progress: 97.1%
 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.