Better Requirements for Scrum
Better Requirements for Scrum is Producore’s course that radically improves the outcomes for Scrum teams. Anyone who participates in, works with, or manages Scrum teams, from developers to executive management can attend this course and bring the benefits of what they learned back to their organization. It is delivered online and is available as a public course and can be scheduled privately for your internal team as well.
Why Register?
Regularly failing to meet sprint commitments happens far too often for Scrum teams but it’s the effect, not the cause. Think back to your most recent difficult sprint. Did you experience any of the following?- Time wasted on rework causing delays
- Old functionality broken by new (regressions)
- Bugs from missing details or misunderstandings
- Time wasted creating unnecessary functionality
- Critical requirement was wrong because it was built from incorrect tribal knowledge
- Having to rewrite requirements from scratch for changes to existing functionality
- Low confidence in safety of changes
- Finding requirements for existing/legacy code next to impossible
- Code, tests, and requirements drifting apart over time
- Team blindsided by external dependency
- Mid-sprint scope creep
- Necessary functionality only discovered after work already started
- Rework because requirements change mid-implementation
- Having to go back to the PO or stakeholders frequently during implementation to get requirements clarified
- Team builds something that turns out to be wrong because of a misunderstanding
- Insufficient details in requirements when implementation begins
- Knowledge about how a system should work (past and present) is not properly captured
- Implementation often begins on a work item before it is truly ready
What You Will Learn
In order for the course to have its intended effect, we start by making sure everyone is clear on:- What the root causes of our problems are
- What Scrum is
- What kinds of additions Scrum permits
- Store and maintain requirements in a product knowledgebase
- Use persisted requirements to drive implementation
- Give every work item its own doneness and readiness criteria
- Give Scrum teams the time and processes to be involved in requirements maturation
- Allow requirements to mature to readiness without deadlines
- Give Scrum permission to not accept work items they don’t understand completely
- Ensure Scrum teams do not commit to work items until they are ready
- Give Product Owners permission to not accept items that do not meet their definition of done
Format of this Course
This course entails 12 hours of training. In can be delivered in one of three formats:- Two days in two 7-hour sessions, each with a 1-hour lunch break.
- Four days, each with a single 3-hour session.
- Six days, each with a single two-hour session.