Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Capture in workshop  Capture in workshop   Prioritised Story Board   Prioritised Story Board

Lifecycle   »   Requirements   »   User Stories


We should bear this technique in mind however we will also remember we are not trying to specify detailed processes, we are trying to define an agile element called a user story. It is useful to get the user story definition down to a single sentence and a single verb but often this is not possible or advisable.

So let us look at what we are trying to achieve when we define a user story. When defining a user story we are trying to maintain the idea and ethos of an original requirement or objective whilst trying to shape this into a structure which makes it easier to estimate and to deliver. We achieve this by using the collaboration principles of our workshop.

The user requirements workshop demands the attendance of senior business stakeholders but also the attendance of an experienced estimator. If you can secure the attendance of an estimator experienced in defining and estimating user stories, naturally this is more useful.

You will agree with your estimator as soon as the workshop has reached a level of detail sufficient for estimation. A summary of user stories at the end of the decomposition of each requirement or objective will seek to ensure your workshop has encapsulated the idea and ethos of the requirement or objective.

At the end of your summary, if one or more of your stakeholders feel there are gaps and that the idea and ethos has not been encapsulated, capture all inconsistencies on a flip chart and these should be summarised at the end of the workshop. If inconsistencies still exist at the end of the summary, a plan with actions, owners and delivery date needs to be delivered to demonstrate to your workshop stakeholders that being inconsistencies will be attended. Our objective at this point is to create and develop a Prioritised Story Board.

Buffer



 Capture in workshop     Capture in workshop   Prioritised Story Board    Prioritised Story Board



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
User Stories






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 229  Page: 238/444  Progress: 53.6%
 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.