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

Lifecycle   »   Requirements   »   Capture in workshop


The normal rules for setting up a workshop apply to the user requirements workshop also. If you need more information about setting up a workshop refer to the section in the Toolkit on the subject of facilitated workshops. The user requirements workshop will be performed at the same time as the Setup Planning Workshop: more information in the section on plans.

The objective of the user requirements workshop is to turn the user requirements into user stories and write them up along with appropriate acceptance criteria in the Prioritised Story Board. Sometimes, the project will not have user requirements at this stage. This is not a big problem. You can elicit user stories from business objectives if necessary. Either way, you will be using the workshop to uncover and direct the combined knowledge and experience of the team to converting high-level statements into more detailed statements. Remember, we are only trying to define parcels of identifiable and reviewable developments in sufficient detail so they can be started, developed, tracked, reviewed and delivered. We do not seek to develop a detailed specification. We wish to stay in the agile world and away from labour-intensive change-resistant traditional methods of the past.

During the workshop, you will take each of your user requirements or business objectives in turn and seek to gain agreement on it across the whole team before you seek to define it. Your project will benefit from measurable objectives defined in the Toolkit and these are simple enough to prepare if you answer the questions: Who, What, How and When? Who is involved to check or deliver the objective? What outcomes do you plan from the objective? How is progress towards the objective to be measured and when is the objective delivered?



You will gain a reliable consensus on the requirement or objective before you start so everyone knows and agrees the target. Once you have agreed the accuracy of your target then the process of understanding the activities to deliver that target can be achieved. What you are trying to achieve is decomposition of the requirement or objective.

You will achieve this by distinguishing between business functions and business processes. Functions describe what the organisation does and these can be further decomposed into processes which describe how these functions are achieved.

People get ate up about terms, so Let us clarify two of them.

Functions and processes are activities. If an activity can be actually performed, it is a process otherwise it is a function. This concept is especially important when you are seeking to decompose business objectives. The rule of thumb for defining processes is to use a verb to title the process. So for example a process would create a customer record, calculate a payment amount, update an invoice quantity or validate a summary total.

Buffer



 User Story Capture     User Story Capture   User Stories    User Stories



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
Capture in workshop






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 228  Page: 237/444  Progress: 53.4%
 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.