Duration
2 days
Overview
In an agile process, the main focus must always be on the end-user. And understanding what their requirements are and how they can be fulfilled occupy front and center in the agile framework process. To help do that, organizations use user stories.
A User Story is the description of a product feature or requirement from a user's perspective. Based on my experience, it is the simplest way to capture requirements which focus on adding value and help businesses to deliver early return on investment!
Whether you are a product owner, scrum master, business analyst, team member, business stakeholder or simply someone who wants the answer to the question "what is a user story", this is the place to start. If you are preparing to become an agile product owner or agile business analyst then this class is for you.
Benefits
- Concise overview of Agile User Stories - Including How to write a user story description, acceptance criteria to capture the detail, the purpose of epics and themes in dealing with large or vague requirements and how to split stories along with the reasons why user stories are favored over traditional methods of capturing requirements.
- The facts based on real industry experience and agile expertise - The correct terminology and use of User stories is essential to mastering it. My experience in industry and extensive research into the topic has been used to give you a solid grounding in the most concise way possible.
- Agile Product Owners / Agile Business Analyst preparation - I tell you the exact theory and give you templates to prepare you for writing user stories in the real world, business or work place without having to do a face to face course saving you hundreds if not thousands of dollars
- What User Stories are and concrete strategies for creating lightweight user stories that truly capture customer’s needs - The six attributes of a good story and how to achieve them. A useful template for writing user stories.
Who Should Attend
- Project & Program Managers
- Analysts, Programmers, Testers
- IT Manager/Directors
- Product Managers
- Project Management Related Professionals
COURSE OUTINE
DAY 1
Introduction to User Stories
- User stories vs/and from requirements
- User stories as a way to illicit requirements
User Roles and Personas
- Characteristics of an effective user representative
- What to avoid
- Dealing and capturing customers
Crafting User Stories
- Including who, what and why
- The importance of the “benefit to the user” in the story
- The 3 C’s process
- Six attributes of a good story
- Introduction to the INVEST principle and how to use it
Product Backlog Content
- Epic stories
- User stories
- Business rules
- Usability, Reliability, Performance, Supportability (BURPS)
- Non-functional stories and defects
Evolution of User Stories
- Getting started with epics
- Splitting epics into stories
- Identifying them as scenario based acceptance criteria or on the product backlog
- Making sure nothing is broken and acceptance criteria is met
- Why automation is necessary
DAY 2
Business Rules
- Embedding them in the user story
- Avoiding the cowboy approach
- Documenting design decisions
Gathering Agile Requirements
- Lightweight techniques to eliminate waste and maximize productivity
- User Story Cadence
- When we gather them, prioritize, size, implement, test and close them
- Contrast with Waterfall
Build your User Stories with knowledge from Course (Template)
- 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.
Programme scope, delivery arrangements and suitability are confirmed during enquiry.