USER STORIES TRAINING
This 1-day hands-on User Stories training course prepares your team to use the User Story technique to effectively manage your requirements.
The User Stories training course covers who develops user stories, how to find user stories, how to write user stories, the importance of acceptance criteria, good vs. bad user stories, relative size estimation, planning poker, measuring team velocity, use of velocity in planning, and managing changing requirements.
The User Story technique is the most popular requirements approach used by Agile teams. User Stories are a lightweight approach to capturing the essence of requirements while encouraging conversations to better understand the details.
To make it real, the course includes exercises where attendees write user stories from their specific work context. The course ends with a project simulation where sub-teams identify and write user stories, build a prioritized backlog, and perform sprint planning and release planning.
The class instructor has more than 20-years experience using Agile and User Stories. He will share case studies, situational advice, and practical application recommendations throughout the course.
To read more about Agile, visit here. To read more about User Stories, visit here. To read more about what all is involved in an Agile transformation, visit here.
What You Receive
- User Story workbook
- Readiness to implement the User Story technique in your organization
- Eligibility for 8 PDUs towards continuing education requirements
Outline
- Agile Requirements
- Origins of User Stories
- Benefits
- Who, What, Why, and How
- Good vs. Bad User Stories
- User Story Workshops
- Estimating User Stories
- Splitting User Stories
- Velocity
- Use of Velocity in Planning
- Managing Requirement Changes
- Project Simulation
- BONUS: Practical Advice, Tips, and Techniques from the Agile World!
Learning Objectives
- Analyze why a high-level lightweight requirements technique is best for changing requirements
- Apply the User Story technique in your work situation
- Apply relative size estimation
- Compare and contrast varying levels of user story quality
- Break down large user stories into smaller right-sized user stories
- Create sprint plans and release plans based on derived velocity
“The introduction of Agile methods had a tremendous impact on our team productivity, and now we are able to demonstrate meaningful progress on our projects every 2 weeks.”
Senior Staff Engineer, Samsung Telecom America