Scrum Kata
For helping software developers continuously work on their craft, there exist coding dojos where a group of craftspeople will solve katas together. Why not do the same thing as Agile Coach or Scrum Master?
Don’t wait and start to improve your skills by continuously challenging and pushing your Scrum Mastery skills.
We’ve got you covered with the questions, now go out there and practice!
Want to submit your own questions? Awesome - click the Button and we’ll tell you how!
Katas
Table of contents
- #Cancelled Sprint
- #No DoD
- #time-boxing
- Advice on the Scrum Team size
- Apply & Devise
- Artifact Knowledge
- Birth of an Increment
- Cherry-Picking Scrum
- Coaching Cross-Functionality
- Committing to uncertainty
- Conclude & Start
- Consensus as base for decisions
- Container Event
- Danger or not?
- Decisions based on the Artifacts
- Developers don’t prepare for Refinement
- Different times for the Daily
- DoD with multiple teams
- Does size matter?
- Done or Not Done
- Emancipating from Scrum?
- Enabler for Improvement
- Engaged Group of People
- Explain Scrum to ...
- External knowledge needed
- Failure to renegotiate Scope
- Focus on Scrum Values for new Team
- Guidance to top management
- Harmful Scrum?
- Holding each other accountable
- Impact on Value
- Implement TIA
- Improving transparency over the Artifacts
- Inspecting the Outcome
- Key stakeholder missing Sprint Review
- Make lack of skills transparent
- Making the emergent process visible
- Measuring Product Value
- Metrics in complex environment
- Multiple Whys in Sprint Goal
- No need for Daily?
- No other meetings
- Not all developers on Daily
- Not enough details for a Daily Scrum?
- Not enough skills to deliver a Done increment
- Order vs. Priority
- Other Goals of Sprint
- Over-running the time-box
- PO challenges the estimate from Developers
- PO’s over-care of the product backlog
- Passing ownership from PO to Developers
- Performance review by Scrum Master
- Postponing Sprint Planning
- Predictability, Risk and Scrum
- Process improvement vs Organisational policy
- Reinforcing Commitments
- Relationships and interactions in Scrum
- Relative Efficacy
- Remaining Work
- Representing Artifacts
- Requirements are not clear but PO is very busy
- Scrum Master as Impediment Remover
- Scrum Value Indicators
- Scrum and Waste
- Self-Empowered Teams
- Skill Acquisition in the Product Backlog
- Skipping Retrospective upon CEO’s request
- Status and progress updates for PO on Daily
- Sum of the Increments
- Swapping planned items due to complexity
- Targets and Goals
- Three artifacts of the Scrum framework
- Time lag for outcome
- Time over
- Unexpected finding right before the Sprint Review
- Urgent items vs process improvement
- Use of forecasting
- Use of the Product Backlog
- Useful, valuable Increment
- Velocity in Scrum Guide
- Wasteful events
- What Definition of Done is
- What Product Backlog Refinement is
- What Sprint Review is
- What is effectiveness?