Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 User Stories  User Stories   User Story Changes   User Story Changes

So your workshop has examined the requirements or objectives, decomposed them into user stories, defined them in terms that can be estimated and developed, confirmed that the processes encapsulate the requirements or objectives and delivered a plan to investigate any gaps that your workshop stakeholders and identified.

If you have developed and delivered a set of user stories acceptable to your user community and to your estimator, described them in every day business language, with enough detail so they can be estimated and developed, without too much detail to allow adjustments and interpretation then you have done well. However you have not yet fully succeeded. Now you will prioritise the user stories.

This is a straightforward assignment to assign MoSCoW rules and document the appropriate priorities to the relevant user stories. In SCRUM projects, the stories are written on small cards that can be pinned up on boards around the development room. We do not mandate this approach; simply write them down on the list, in a document or spreadsheet. It is the fit for purpose solution we seek and as long as the development team can access the list that is acceptable and makes the room look less untidy. All this of course is a personal decision for the project team and, if an array of cards helps demonstrate progress and show outstanding work swiftly, then this the fit for purpose solution for you and your team.

We are often asked, at this point in the project, should each of the user stories be converted into use cases. Our answer is always the same. If your development landscape demands it, it is important. However if this conversion is not demanded, in our experience, you save a lot of rework and redevelopment of the use cases when the user stories are interpreted and adjusted. If you do not need to perform use case conversion leave the user stories as they are.


 User Stories     User Stories   User Story Changes    User Story Changes

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
Prioritised Story Board


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
Topic: 230  Page: 239/444  Progress: 53.8%
 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.