Twice now in my career I’ve done a massive rewrite to replace an existing product. In both cases, it didn’t end well. Each time, the new product was competing with an existing product that was making the company money. So, of course, the existing product got enhancements on a rickety structure, and on the new […]
technical debt
Scrum by Example – ScrumMaster for Three Teams? What are the Alternatives?
A company adds teams but wants to keep the same number of ScrumMasters. Smart move or disaster? This case study examines how to handle such a situation.
Scrum by Example – Technical User Stories or The Team Try to Pull a Fast One on the Product Owner
Should a technical issue be a User Story in the Product Backlog? How Agile teams can handle system tech problems within Scrum.
Scrum By Example – The Team Learn How to Learn
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.
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.