Agile User Stories
- 1. Page 1Classification: Restricted Business Analysis Training Agile- User Stories
- 2. Page 2Classification: Restricted Agenda • AGILE - DEFINITION • AGILE - BENEFITS • AGILE - INVEST CRITERION • AGILE - FORMAT • AGILE - SIZE OF A USER STORY • AGILE - USAGE OF STORIES • AGILE - COMMON STORY MISTAKES • AGILE - SUPPORTING ARTIFACTS • CA Agile Central: User Story
- 3. A user story represents a small piece of business value that a team can deliver in an iteration. DEFINITION • The brief description of the need • The conversations that happen during backlog grooming and iteration planning to solidify the details • The tests that confirm the story's satisfactory completion 3 STEPS Keep yourself expressing business value Avoid introducing detail too early that would prevent design options and inappropriately lock developers into one solution Avoid the appearance of false completeness and clarity Get to small enough chunks that invite negotiation and movement in the backlog Leave the technical functions to the architect, developers, testers, and so on BENEFITS
- 4. Independent : We want to be able to develop in any sequence Negotiable : Avoid too much detail; keep them flexible so the team can adjust how much of the story to implement. Valuable : Users or customers get some value from the story. Estimable : The team must be able to use them for planning. Small : Large stories are harder to estimate and plan. By the time of iteration planning, the story should be able to be designed, coded, and tested within the iteration. Testable : Document acceptance criteria, or the definition of done for the story, which lead to test cases. INVEST CRITERION As a <user type>, I want to <function> so that <benefit> Example: As a consumer, I want shopping cart functionality to easily purchase items online. As an executive, I want to generate a report to understand which departments need to improve their productivity. FORMAT
- 5. • A story should be small enough to be coded and tested within an iteration—ideally just a few days. • When a story is too large, it is called an epic. • Backlog items tend to start as epics when they are lower priority. For release planning, epics should be broken down into smaller chunks, but not so small that you have moved into detailed design. SIZE OF A USER STORY BROAD: • A team member can view iteration status. DETAILED: • A team member can view a table of stories with rank, name, size, package, owner, and status. • A team member can click a red button to expand the table to include detail, which lists all the tasks, with rank, name, estimate, owner, status. PERFECT: • A team member can view the iteration's stories and their status with main fields. • A team member can view the current burndown chart on the status page, and can click it for a larger view. • A team member can view or hide the tasks under the stories. • A team member can edit a task from the iteration status page. EXAMPLE
- 6. • How do I add details to a user story ? • How Definition of Done is Validated ? • Who converts Acceptance Criteria's to Acceptance Test ? • Is it Product owners responsibility to list as many acceptance criteria as possible in order to clarify the intent of the story ? Answer Key: Acceptance Criteria . Acceptance Criteria . QA . Yes Q&A CREATION: The customer, customer proxy, product owner, and anyone else who identifies a need for the product can contribute user stories. OWNERSHIP AND MAINTATINANCE: The product owner owns the user stories and is responsible for writing, gathering, maintaining, and prioritizing. USAGE: Developers, testers, technical writers use user stories to be able to know what to implement and when they are done. Product owners track overall progress based on the status of the user stories. Management tends to track user stories rolled up to epics or features. USAGE OF STORIES
- 7. Too formal or too much detail. • Product owners with good intentions often try to write extremely detailed user stories. If a team sees a story at iteration planning that looks like an IEEE requirements document, they often assume that all the details are there and will skip the detailed conversation. Technical tasks masquerading as stories. • Much of the power of Agile comes from having a working increment of software at the end of each iteration. If your stories are really just technical tasks, you often do not end up with working software at the end of each iteration, and you lose flexibility in prioritization. Skipping the conversation. • Stories are intentionally vague before iteration planning. If you skip the acceptance criteria conversation, you risk moving in the wrong direction, missing edge cases or overlooking customer needs. COMMON STORY MISTAKES
- 8. TECHNQUES: story maps, workflow diagrams, storyboards, sketches, and mockups. TECHNICAL REQUIREMENTS: Include architectural element like a component or details like what a service should do Support by Technical User Stories Include UML NOTE: User stories is worthwhile when you develop software that’s likely to be reused. User stories are not about documenting requirements; they want to enable you to move fast and develop software as quickly as possible—not to impose any overhead. SUPPORTING ARTIFACTS
- 9. CA Agile Central: User Story
- 10. THANK YOU!