A Standup report leads our case study ScrumMaster to arrange for his Scrum team to use Coding Dojos to build confidence and pay down Technical Debt.
Notes from a Tool User
Scrum by Example – Stop Digging New Holes
Our case study Scrum Team is accumulating Technical Debt and needs to adjust Velocity and review Definition of Done, Unit Testing and Restructuring Legacy Code.
Scrum By Example – Technical Debt is Slowing the Team
Our ScrumMaster pulls up the CFD for the current release… and notices that the rate at which stories are being selected has slowed down in the past few sprints.
Scrum By Example – The Team Gets Bottlenecked
A ScrumMaster Tales case study of an Agile team that relies on one specialized developer for all tasks, which becomes a bottleneck for the sprint.
A Rebuttal of Groupthink
In a New York Times article: “The Rise of the New Groupthink” this week Susan Cain claims that teams and collaborative work give rise to groupthink. Groupthink is not out of the question, as Christopher Chabris and Daniel Simons demonstrate in “The Invisible Gorilla” group think is a risk – cite the example of the […]
Scrum by Example – Impediments are Holding Back the Team
Our case study Scrum team learns than impediments are anything stopping the team from delivering value. Resolve problems faster by making subtle issues visible.
When to stop holding retrospectives?
Are your Scrum developers getting bored of Agile retrospectives? Retrospectives should be interesting, effective, and help the team improve.
Learning Scrum through Games
How to introduce the basic concepts of Scrum in 60 minutes? I invited teams to create Children’s Books of the Goldilocks story.