(Continued from Kanban Portfolio view and the 3 core rules. This is the conclusion of Part 2 in the Scrum Alone is Not Enough series.) 2. Limit Work In Progress We know from queuing theory, psychology of multi-tasking, and empirical evidence (Rally study, my summary of the Rally Study) that more Work in Progress means less work gets done overall. […]
Scrum
Kanban Portfolio View
(Presented as Part 2 in the Scrum Alone is Not Enough series.) Do you know what projects your Team is working on? Do you know what the Teams around you are working on? Does everyone in your organization know? In almost every organization that I visit, the answer is a resounding no. Scrum may have been […]
Scrum Alone is Not Enough
To be successful with Scrum in the long term you need more than the basic framework. This is intentional. Scrum provides the structure as a starting point, but it’s designed to work well when applied with other effective patterns. Like the Design Patterns movement of the late ’90s, a pattern can be used by itself […]
Welcome to the High-Performance Teams Game
Your team is working on the World’s Smallest Online Bookstore, a site that provides the best results (just a few) for every search, not every result on earth. We’re a vulture capital funded company, so if we don’t deliver, our funding will be cut. So begins the opening of the High-Performance Teams Game. My goal […]
It’s not Scrum if…
A lighthearted look at what can go wrong when Scrum is misapplied. Without spirit, passion, and engagement, things go sideways.
Early Feedback Reduces Anger and Frustration
Have you seen a developer react after they’ve spent three days writing a feature, only to have the tester say, “Um… no” in a Post Mortem (a meeting about a project after it has finished) that went badly wrong – with lots of finger pointing and anger? Recently in a CSM Class an attendee helped […]
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.