
Groom backlog for agile requirements by comparing agile and waterfall approaches, detailing the steps from high level gold screen to fine-grained requirements, with interactive Q&A.
Explore waterfall as a proven, highly repeatable process for clear requirements, and recognize its drawbacks—no value until the end, minimal customer involvement, and heavy upfront planning.
Learn how to start agile product development with planning, backlog creation, roadmaps, and release planning, delivering a minimum viable product (MVP) through sprints while contrasting agile with waterfall.
Explore Scrum's transparency, inspection, and adaptation, with daily stand-ups and sprint reviews; learn XP paired programming and Lean's demand-driven, value-focused build that stops production if something goes bad.
Kanban visualizes the workflow and grooming steps, moving each story card from coarse to fine across eight steps, while limiting work in progress to improve throughput and reduce bottlenecks.
Compare agile and waterfall requirements, highlighting upfront documentation in waterfall versus just-in-time backlog items—epics and stories—in agile, with changes managed between sprints.
Explore forms of business requirements, focusing on user stories with acceptance criteria, and distinguish epics from stories while planning by teams to align with sprint capacity.
Define backlog concepts as a repository for requirements across product, release, and sprint backlogs, and prioritize high-value items with epics and user stories guided by INVEST criteria and acceptance criteria.
Groom the backlog by refining high-level requirements into fine-grained stories with enough detail for the team, using size and value to prioritize across product, release, and sprint planning.
Master backlog grooming: prioritize by business value, size with small, medium, large, and break epics into stories. Track cycle time and process efficiency to improve sprint readiness.
Flesh out requirements with acceptance criteria and UI details. Collaborate on technical design, estimate story points, prioritize for the sprint, and map value with a kanban board.
Apply best practices for backlog grooming through weekly collaboration between customers and the development team, using cost of delay and item relationships to set priorities and ensure release readiness.
Refine the backlog with the customer in mind to produce two sprints of ready stories aligned to team velocity, and define ready and done criteria through business-technical collaboration.
Have you or your Agile teams had trouble refining requirements on an Agile project? Are your teams struggling with user stories and tasks that are too large for them to handle well? If so, you and your teams need more guidance to implement backlog / user story grooming.
Backlog grooming is a step-by-step process of taking high-level (“coarse-grained”) requirements and refining them to lower-level user stories and tasks (“fine-grained”) that are ready to put into a sprint. Backlog grooming is typically a product owner role that requires skill in prioritizing requirements and breaking down requirements with the help of the customer and development team.
In this course, attendees will learn how to work the process to achieve fine-grained requirements that are ready just in time. The key to success is leveraging tools and techniques as well as the expertise of your team to refine requirements iteratively.
After completing the course, attendees will be able to
Explain how backlog grooming works.
Understand the difference between coarse-grained and fine-grained requirements.
Start grooming backlogs on their projects right away.