User Story Training Course Overview
This User Story Training course will provide you and your Agile team with the knowledge and skills required to develop effective user stories, acceptance tests and map your current requirements using this agile approach.
User stories are the most common means of representing requirements for Agile Scrum projects and are written from the perspective of the system user or purchaser. Acceptance tests are written to clarify and verify the behaviour of user stories.
User Story Training course audience
This User Story training course is for those who have a fundamental understanding and experience with Agile or Iterative development and the Scrum approach.
What you will be able to do after this User Story Training
Scrum Masters Inc User Story training will enable all participants with what they need to identify and develop effective user stories and comprehensive product backlogs.
How to develop a user story that contains all of the key information, define acceptance tests, map their current requirements process to an Agile approach, use a variety of lightweight techniques to identify and size a backlog of user stories and determine how to handle non-user story components like business rules and non-functional requirements.
Receive weekly Agile transformation tips sent to your inbox at no charge.
1 Day User Story Training Course outline
Introduction
- User stories vs/and from requirements
- User stories as a way to illicit requirements
Crafting User Stories
- Including who, what and why
- The importance of the “benefit to the user” in the story
- The 3 C’s process
- Introduction to the INVEST principle and how to use it
Evolution of User Stories
- Getting started with epics
- Splitting epics into stories
Acceptance Tests
- Making sure nothing is broken and acceptance criteria is met
- Why automation is necessary,
Gathering Agile Requirements
- Lightweight techniques to eliminate waste and maximize
productivity
User Roles and Personas
- Characteristics of an effective user representative
- What to avoid
Product Backlog Content
- Epic stories
- User stories
- Business rules
- Usability, Reliability, Performance, Supportability (BURPS)
- Non-functional stories and defects
Non-functional Requirements
- Identifying them as scenario based acceptance criteria or on the product backlog
Business Rules
- Embedding them in the user story
- Avoiding the cowboy approach
- Documenting design decisions
User Story Cadence
- When we gather them, prioritize, size, implement, test and close them
- Contrast with Waterfall
Optional Day Two
Workshop to build your User Stories with knowledge from Day One
- The result of the Day Two is to take your Project and to either rewrite current User Stories or to take new requirements and write new User Stories.
- At the end of the second day your team will have a set of User Stories that can be taken directly to the Sprint Planning meeting.
Three steps to get started
- Fill out the form and we will contact you to schedule a 30 min preliminary training assessment to see if this course has what you need to be successful
- If it is a good fit, then book and attend the Agile Team Training with one of our Agile Coaches
- Let you and your fellow team members accelerate your Agile team development deliverables.
User Story Training Course logistics
- 9AM – 5:0PM – one day
- Virtual Lead Instructor using Zoom and e-learning tools
- Only provided as a private offering
- Price – $3,750 USD
- Option second day $2,000
- 14 participants max.