User Story
Aug. 17, 2009•0 likes•9,993 views
Download to read offline
Report
Technology
Entertainment & Humor
This presentation describe What is the need for user stories in Agile project? What is a story? Why story? What is criteria for a good story? What are not stories? Prerequisite? Knowledge of Scrum and it’s terms
Sunil JakkarajuFollow
More Related Content
What's hot
Writing Good User Stories (Hint: It's not about writing)one80
User stories in agile software developmentSandra Svanidzaitė, PhD, CBAP
User Stories FundamentalsMoisés Armani Ramírez
User Stories explainedMartin Lapointe, M.T.I.
Effective user stories for your agile or Scrum teamDigitalCatapultDevelopmentPractices
Epics and User StoriesManish Agrawal, CSP®
Similar to User Story
User StoriesJames Peckham
The Whole Story of The User StoryXPDays
Better Software Keynote The Complete Developer 07Enthiosys Inc
Better Software Keynote The Complete Developer 07Enthiosys Inc
Are You Cut Out For Consultingjacobs5628
Are you cut out for consultingjacobs5628
Recently uploaded
Document Understanding as Cloud APIs and Generative AI Pre-labeling Extractio...DianaGray10
Product Listing Presentation_Cathy.pptxCatarinaTorrenuevaMa
info_session_gdsc_tmsl .pptxNikitaSingh741518
Connecting Africa.docxEric Annan
h2 meet pdf test.pdfJohnLee971654
Keynote: Two years at the British Library... and counting / Alan Danskin (Bri...CILIP MDG
User Story
- 1.
- 2.
- 3.
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 24. A user can view information about each job that is matched by a search
- 25.
- 26.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47. Company can pay for a job posting with a visa card
- 48. Company can pay for a job posting with a master card
- 49. Company can pay for a job posting with an American Express
- 50. Good
- 51. Company can pay for a job posting with a credit card
- 52. Also good
- 53. Company can pay for a job posting with one type of a credit card
- 54.
- 55.
- 56.
- 57. Not
- 58. All connections to the database are through a connection pool
- 59. All error handling and logging is done through a set of common classes.
- 60. If there’s a technical story put it in terms the business can understand
- 61. Up to fifty users should be able to use the application with a five-user database license
- 62.
- 63. Lack technical knowledge
- 64.
- 65.
- 66.
- 67.
- 68. A novice user is able to complete common workflows without training
- 69. A user must not have to wait long for a screen to appear.
- 70. New screens appear within two seconds in 95% of all cases.
- 71. Strive for 99% automation
- 72. Automate on the code not just the UI.
- 73. Fit is good (Fitnesse)
- 74.
- 75.
- 76.
- 77.
- 78.
- 79.
- 80.
- 81.
- 82. A resume can be posted by a job seeker
- 83. Good
- 84.
- 85. But they can suggest
- 86. Which maybe is write them then get signoff
- 87. Offer advice
- 88.
- 89.
- 90.
- 91.
Editor's Notes
- Software requirements is a communication problem.Software Engineer != Construction.Building software is side effect of discovering the customer’s problems.
- The communication problem is between those who want the software and those who build the software
- If either side dominates the business loses.
- The functionality and dates are mandated with little regard for reality or whether the developers understand the requirements.
- … technical jargon replaces the language of business and developers lose the opportunity to learn from listening.
- We need a way of working together so that resource allocation becomes a shared problemProject fails when the problem of resource allocation falls too far to one side
- We cannot predict a software schedule. Estimation is the calculated approximation of a result which is usable even if input data may be incomplete or uncertain (Wikipedia). Estimation is prediction NOT planning. Typical first estimate is off by factor of 4 0.25x to 4x. They should be naturally realigned as we gather more information during the project.
- Human beings in general are bad at absolute estimates. They are good at relative estimation.
- We make decisions based on the information we have, but do it often
- Rather than making one all-encompassing set of decisions, we spread decision making across project
- Card – Stories are traditionally written on note cards. Cards may be annotated with estimates, notes, etc
- Conversation – Details behind the story come out during conversations with product owner
- Confirmation – Acceptance tests confirm the story was coded correctly
- Stories that are big are called EPIC. They can potentially be broken down into smaller stories. Epics are listed in the product backlog for future sprints / iterations.
- A collection of related user stories
- If the requirements are written down then At best the customer will get what was written. Customer may make lot of assumptions while writing the requirements.
- Stories support and encourage iterative development. Encourage deferring the detail until you have the best understanding of what you really need.
- Intentionally left blank.Think what points might go in this slide
- A user story is request for valuable stuffPromise for future conversationIn scrum it goes into product backlog item.
- Identifies who the user is, what they want to do and why?
- This mnemonic helps determining whether a story is acceptable or not.
- If there is lot of dependency it might suggest we are breaking work in horizontal layers (in tiers – Database, db layer, business logic, UI)Agile methodology suggest to breaking work in vertical layers (slice through tiers)If not independent, it make product backlog difficult to manage multiple layers of dependency.If dependency is unavoidable, then prioritize dependent stories after the stories they depend on.Or use mocking architecture, decouple dependency.
- Story should be request for value.Should not dictate what they want.Advantage is it will avoid biased opinion Eg: By how many runs will England win against India. This mean we are assuming that England will win.Too much detail turns user story into contract which is taking away self-organization capability of scrum team.
- Identifying value is key part of writing the story.Everything in scrum is value driven.
- Common reasons why they’re not estimableLack domain knowledgeCan discuss with business people and learnLack technical knowledgeCan spike on the story to learn more about itTwo stories, one for the spike one for the real workStory is too big – cannot commit to big stories.Sometimes useful to write the epic to be a placeholder for some glossed over part of a system.Pulled from thin air estimate!Or break it down.
- Small stories are easier to estimate.A story that is too big to do in single sprint is an “EPIC”
- Cross cutting concerns: compliance with corporate needs. External regulations.