Overview
A lot of projects fail due to poor requirement gathering, inadequate planning and analysis. Traditional requirement documents often do not help gather complete requirements accurately, especially in the rapidly changing environments. This user story workshop discusses how to define and manage the requirements effectively. The workshop also demonstrates alternative ways of documenting requirements and managing changes. Using these, participants would be able to implement less ‘heavy’ processes in their projects that would benefit from quick changes.
What You'll Learn
- Learn to adapt quickly and positively to rapidly changing business needs and priorities
- Learn how to collaborate on requirements for a project
- Align development to business needs to deliver business value rapidly
- Explore the benefits of using Agile methods to communicate requirements
- Understand the five levels of planning in Agile
- Use Agile requirements as an effective basis for planning and testing
- Understand the characteristics of a well-written Agile requirement
- Learn how to plan frequent releases for customers to realize the benefits quickly
- Learn the mapping techniques for identifying the stories of larger releases
- Minimize risks of delivering ineffective solutions by gathering feedback frequently
Curriculum
- What is Agile?
- Why Agile?
- Agile vs. Waterfall
- Why a well-written story is beneficial
- Analyst activities of Waterfall that translate to Agile
- Differences when aligning to Agile
- How the analyst role aligns with the Agile manifesto
- Understanding user personas
- Using user personas inside a story
- Determining user experience
- Identifying roles
- What is a user story
- Role, goal, benefit
- Acceptance criteria best practices
- Examples
- INVEST overview
- Other types of backlog items
- What is a spike?
- How to use them
- Example
- Non-functional (tech debt)
- What is a non-functional requirement?
- How to use them
- Example
- Defects
- Ways to manage defects
- Example
- Vision
- Roadmap
- Features
- Epics
- Product backlog
- Prioritization techniques
- Process mapping
- Story mapping
- Story writing sessions
- Backlog grooming
- Relative sizing
- Definition of Ready
- Story preparation of Kanban
- Backlog prioritization
- Release planning
- Real world workshop
Who should attend
The course is beneficial for all members of Agile teams, though they are the most valuable for Product Owners or members of the development teams, or professionals with a focus on grooming the product backlog. The course is highly recommended for:
- Business analysts
- Requirement analysts
- Business systems analysts
- Product Owners
- Business customers
- Users or partners
- Quality assurance professionals
- Systems testers
- User acceptance testers
- System/application analysts
- Architects
- Designers
- Developers
- Anyone who wishes to enhance their understanding and ability to author and elaborate on user stories
Prerequisites
There are no mandatory prerequisites for this course. However, completing the Foundation of Agile course prior to taking up this course would be beneficial.
