We might not be able to make Sprint Backlogs exciting, but we can make them more effective. Let’s look at what purpose they serve, and how to improve them. What is a Sprint Backlog A Sprint Backlog consists of a set of Product Backlog Items (PBIs) that the Developers think they can complete in the […]
Red-Yellow-Green status reports are a widely-used tool to help executives have a fast and simple understanding of the current state of a project through a visual model that makes it easy to spot patterns. Green means everything is good, yellow means there’s some risk, and red means the project is in serious trouble. Simple, right? […]
Go Beyond Merely Completing Work Lists A Sprint should be so much more than just completing a number of User Stories or fixing bugs. If your Sprints are merely about ticking off items on a scattered work list without having a shared understanding of why they’re important or what purpose they serve, your Development Team […]
What is the difference between an Agile Retrospective and a Post Mortem? Retrospectives are the foundation of Continuous Improvement and Short Feedback loops.
Nearly every client I work with asks me this question at some point. The Scrum Guide offers very limited guidance, suggesting 3-9 people per team (exclusive of ScrumMaster and Product Owner), without giving reasons or context for those numbers. There isn’t one, universally correct answer for optimal team size, but there are a number of […]
One of the more frequently asked questions in my Scrum workshops is around the difference between Definition of “Done” and Acceptance Criteria, and how they relate to User Stories. While Acceptance Criteria is a commonly understood concept in software development, Definition of “Done” is unique to Scrum. People get confused between these two things but […]