| |
|
|
Course Outline
|
This 2 day workshop is targeted at Product Owners, Customers, Business Analysts, Subject Matter Experts, Testers and Developers who want to express user needs in the form of User Stories.
User Story is a fundamental planning, communication and tracking tool used by most Agile teams. Once we have identified and defined the project vision, next we need to capture and break down initial user needs into User Stories. Few agile teams try to prioritize after all the user needs are broken down into user stories. In this workshop we'll look at how we build user personas and prioritize right away using personas instead of just doing low level prioritization.
In this session we'll highlight how User stories have their own lifecycle and how they evolve over the project's lifecycle?
|
By the end of this workshop, participants will
- Know how to write effective stories; with a useful sample template for writing user stories
- Learn about the six attributes of a good story and how to achieve them
- Grasp how stories make for better, simpler, nimbler development
- Understand the importance of User personas and how to prioritize stories using them
- Know how to build Story trees (in practice story lists are impractical) and let the stories evolve over the project's lifecycle
- Understand the fundamentals of Acceptance Criteria and Tests
- See how user stories drives acceptance criteria and automated acceptance tests : Acceptance test driven development
- Understand the importance of sophistication knobs on each story and how to use a grading approach to developing stories
- Practice by creating the first cut of stories and acceptance tests for a real open source project
|
| In this workshop we'll cover the following concepts related to User Stories: |
- Fundamental of User Stories: The properties of good stories; their use; lifecycle of stories; level of detail; stories' incremental nature
- Ron Jeffies' 3 Cs and William Wake's INVEST Principle
- Story writing workshop
- Patterns and Anti-patterns : Examples from real projects
- Striking a balance between upfront analysis and just-in-time pull based analysis
- Acceptance Test Driven Development - The why, when and the how?
- Acceptance testing workshop
- Acceptance Test Driven Development patterns and anti-patterns
|
|
|
