User Stories

3 Days

requirementsgherkinuml
agilerequirement

Intermediate

developertesterproduct ownerscrum masteranalyst

In this program, participants learn to create good user stories at editorial, structural and content level. This program starts with defining requirements, its structure in form of user stories and continues on to explain what makes them good or bad. Estimation in form of user story points is well explained in program. Program includes examples and hands-on including anti-patterns and grooming.

Audience

Program is primarily for Analysts and agile team members who are directly involved with requirement maintenance

Prerequisites

Participants must have experience of SDLC as requirements analyst, business analyst, product owner, scrum master or member of agile team.

Topics
Requirements
  • Define System
  • What is Requirement?
  • Problems and Opportunities
  • Organization in context
  • Analysis Vs Design
  • Stakeholders and Vision
  • Users and Stories
  • Functional and Supplementary
  • Glossary
User Stories
  • Story, Epic, Theme, Task
  • Sprints and Versions
  • Elements of user story
  • User story template
  • Priority, Names, Numbers
  • User story points
  • Points Vs Hours
  • Planning Poker
  • Mapping stories
  • Tests and Acceptance Criteria
  • BDD and Gherkin
  • Grooming & Splitting
More
  • Structured English
  • User story smells
  • INVEST principles
  • Correct, Complete, Verifiable,
  • Unambiguous, Executable,
  • Traceable, Feasibility
  • Strategy
  • Business and Root Cause Analysis
  • Develop stories
  • Solution Validation
  • Workshop, Brainstorming, Q&A, Interview
  • Guidelines & checklist
More
  • Complexity Management
  • What Vs How
  • Modularity and Simplicity
  • One at a time
  • DRY
  • Hierarchy
  • Abstraction
  • Version Control
  • Information Analysis
  • Data Dictionary
  • Reification
  • Archetype
  • Business Rules
  • Modelling And Visualization
  • Text Vs Model
  • Flow and Activity
  • Block diagram
  • Class Diagram
  • Sequence Diagram
  • State Machine
  • Interface
  • Decision Tables and Tree
Exclusions

Scope/Project/Expectation management, Tooling, Detailed UML, Use Cases, Unrelated areas of Agile/Scrum

Anything not mentioned in Topics

Software Requirements

Word Processor

Internet Requirements

Good unrestricted internet connection is required.

Hardware Requirements

Laptop capable to run MS Office

Classroom Requirements

Projector with HDMI, White Board, Markers with Eraser

Online Requirements

Appropriate meeting software e.g. Zoom, MS Teams Please make sure that camera, speaker and mic are working

If you have any query, please contact now.