Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Writing User Stories : Agile Way of Capturing Requirements


Published on

User Stories , Good Reading material for people preparing for PMI-ACP or Interested in knowing details of User Stories.

Published in: Technology

Writing User Stories : Agile Way of Capturing Requirements

  1. 1. User Stories & AgileAnalysis Saket Bansal PMP, PMI-ACP, CSM , ITIL-F 1
  2. 2. User StoriesEpics and Themes A Good User Stories Writing User Stories Responsibilities 2
  3. 3.  A user story describes functionality that will be valuable to either a user or purchaser of a system or software. 3
  4. 4.  Is • An agreements between customers and team members to discuss detail requirements during an iteration • Emphasize verbal rather than written communication. • Right size for planning Is not • A Requirement document, requirement need to be captured by discussion , if discussion is not possible then should be augmented by documentation 4
  5. 5.  Card: • Stories are traditionally written on note cards • Card may be annotated with Notes , Estimates etc, Conversation : • Details behind the story come out during conversations with product owner/customer. Confirmation • Acceptance tests confirms a story was coded correctly 5
  6. 6. As a (role) I want (something) so that (benefit).As aWho wants this piece of functionalityI wantWhat the user wantsSo thatWhy the user wants it 6
  7. 7. As a Exam AdministratorAs a Student I want to I should be able totake practice test so that publish new Exam soI know my readiness for that test takers can takeexam. it. As a Administrator IAs a Student I want to should be able tosee how I am doing in manage question bankpractice test so that I can so that I can retire easyplan my future study. questions. 7
  8. 8. As a Student I want totake practice test sothat I know myreadiness for exam. •Does system allows user to select number of questions •Does system allows user to take test in multiple sessions •Does system provides facility to time the exam, is if configurable ? •Do we need to save the test history? 8
  9. 9. As a Student I want totake practice test sothat I know myreadiness for exam. •Verify that test taker can select questions in multiple of 10 with max limit of 100 •Verify that registers user can do the test in multiple sessions. •Verify that User can see how he has performed in test at later date. 9
  10. 10. As a Test taker I can select the number of questions so that i get that many questions in testAs a Student I want to As a Test taker Itake practice test so should be able to holdthat I know my the test so the I canreadiness for exam resume it at later stage As a Test taker I want to save my test results so that I can review them at later date 10
  11. 11. User StoriesEpics and Themes A Good User Stories Writing User Stories Responsibilities 11
  12. 12.  Epic , Is a large User Story, They are too big to implement in a single iteration and therefore they need to be disaggregated into smaller user stories at some point Theme : Theme is a set of related user stories that may be combined together and treated as a single entity for either estimating or release planning. 12
  13. 13.  In some cases epic may equal a theme. However we write an epic as a placeholder for big features we want to add someday , while themes serve the purpose of grouping together a set of related stories Epics come from top-down planning while themes are created bottom. There is no hierarchy relation between Theme and Epic Epics are usually bigger than theme , but in some cases theme may have more than one epic in it. 13
  14. 14. As a Job Seeker I should be able to search for jobs by keywords and location so that I can find theAs a Job Seeker I suitable matchshould be able tosearch for a job sothat I can find suitablematch As a Job Seeker i should be able to view information about each job that is matched by a search so that I can get details of listed Job 14
  15. 15. As a Head PMO, I would like to see list of projects which are behind schedule so that I can take corrective actions As a Head PMO, I As a PMO Head, I would like to see list if would like to review upcoming milestones project performance in any running against time so that I projects so that I As a PMO Head, I can take corrective would like to review ensure resources on actions time.performance of ongoing projects so that I cantake corrective actions As a PMO Head, I As a Head PMO, I would like to review would like to see list Project performance of projects which has Epic against budget so that I missed last 3 can take corrective milestone dates so actions that I can identify the risky projects. Epic User Story 15
  16. 16. A Job Seeker can fill out a resume form. Technical Division Information on a resume form is written to the database.A Job Seeker can A Job Seeker can submit post a resume a resume that includes only basic information such as name, address, education history Slice the cake A Job Seeker can submit Epic a resume that includes all information an employer may want to see. 16
  17. 17. An epic that comprises Compound Story multiple shorter storiesEpic Inherently large and Complex Story cannot easily be disaggregated 17
  18. 18. Splitting across data Split along the boundaries of the data boundaries supported by the story. Splitting on Based on the operations that are Operational performed within the Boundaries story. Epic : Creating two versions of the story: one with andCompound Removing Cross one without support for Cutting Concern Story the cross-cutting concern. Don’t meet Separate the functional performance and nonfunctional constraints aspects Split into smaller Split Stories of Mixed stories if the smaller Priority stories have different priorities 18
  19. 19. Research and determine the Investigation feasibility (TimeBoxed Spike)Epic : Complex Story Add that Development functionality to the product. (User Story) 19
  20. 20. User StoriesEpics and Themes A Good User StoriesWriting User Stories Responsibilities 20
  21. 21.  Independent • Avoid Introducing dependencies between stories Negotiable • Stories are negotiable. they are not written contracts or requirements Valuable to users or customers • Story must be valued by the users / Purchaser Estimatable • Developers should be able to estimate it. Small • Stories should be rightly sized , Too large or too small cannot be used in planning. Testable • Stories must be written so as to be testable. Successfully passing its tests proves that a story has been successfully developed. 21
  22. 22.  Is a Closed stories Has User Role Written for One user Does not focus too much on UI Has acceptance tests 22
  23. 23. User StoriesEpics and Themes A Good User Stories Writing User StoriesResponsibilities 23
  24. 24. Identify Initial asset of Identify User Personas Identify actions /User Roles for important User interactions User Roles , also identify Persona or role can have Extreme Characters with system • Set of User Roles • User Personas • Epic Stories • Extreme Characters 24
  25. 25.  A user role is a collection of defining attributes thatcharacterize a group of users and their interactions with thesystem. Its an aggregate individual users Role Modeling Steps • Brainstorm set of user roles relevant for our system • Organize and consolidate roles • Refine the roles 25
  26. 26. Ajay• Deals in Sr. Positions• Specialized in Law Firms recruitmentSally• Deals in Project Management• Specialized in IT Projects ManagersSunita• Deals in Entry level Recruitment• Specialized in call Center Recruitment 26
  27. 27. For some of the important user roleswe should create a persona . A  Namepersona is an imaginary  Picturerepresentation of a user role.  Education & Experience  Likes / Dislikes  Demographic Information  Not to map to the real user 27
  28. 28.  Users with exaggerated personalities may lead to new stories 28
  29. 29. Includes developers , users ,product customers, productowner , anyone who cancontributeShould be conducted prior torelease planningUse CardsDiscussion remain at a highlevel 29
  30. 30. User StoriesEpics and Themes A Good User Stories Writing User Stories Responsibilities 30
  31. 31. 31
  32. 32.  Identify appropriate user roles. Participate in the process of identifying user roles and personas. Write Stories. When writing stories ensure that each story can be associated with at least one user role or persona. If you need help in writing the stories, you are responsible for scheduling and running story-writing workshops. 32
  33. 33.  Participate in the process of identifying user roles and personas. Participate in Writing Stories. 33
  34. 34. 34
  35. 35.  Writing the acceptance tests. Write tests as many which adds value and clarification to the story. Executing the acceptance tests. 35
  36. 36.  Responsible for automating the execution of acceptance tests if required You are responsible for thinking about additional acceptance tests You are responsible for unit testing your code so that acceptance tests do not need to be specified for all the minutiae of a story 36
  37. 37. User StoriesEpics and Themes A Good User Stories Writing User Stories Responsibilities 37
  38. 38. User Stories Applied for Agile software Development-Mike Cohn 38
  39. 39. Check with us formore informative and interesting presentations… 39
  40. 40.  Provide Agile & Scrum training Provide face to face and online training of PMI-ACP (Agile Certified Practitioner) certification program Help Organizations in adapting agile Helps organizations in setting up project governing office. Get training calendar at 40
  41. 41. Saket BansalSaket.Bansal@iZenBridge.comM: 9910802561Web: www.iZenBridge.comLinkedIn: 41
  42. 42. Did you get your answers? Drop us a note! 42