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? […]
Red-Yellow-Green Status Reports and Other Models – How They Should and Shouldn’t Be Used
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? […]
How Escape Rooms Teach About Teams
Mark and his wife, Doris, along with a small group of their friends, have become very good at solving challenges and escaping locked rooms. In their first escape room in 2015, they were two puzzles away from success but failed to get out. So they changed the team membership. Over the years, they failed another […]
Sprint Goals Provide Purpose
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 […]
Agile Retrospectives
What is the difference between an Agile Retrospective and a Post Mortem? Retrospectives are the foundation of Continuous Improvement and Short Feedback loops.
What is the Recommended Scrum Team Size?
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 […]