What’s wrong with designating feature work as good, bad, and ugly? How should you categorize feature work and why?
An opinion column for developers. Brutally honest, no pulled punches.
What’s wrong with designating feature work as good, bad, and ugly? How should you categorize feature work and why?
Why do multi-team postmortems often devolve into blame games and inaction? How do you run a 90-minute postmortem in which every person and topic is heard, and owners are assigned to improvements?
Why are war rooms needed? What are the mechanics of running war room?
What’s happened since the Windows division switched to a functional org structure? How many different group managers do we need?
How do business considerations impact your group? Is your group delivering enough value to offset its incurred costs?
What do people get wrong about an MVP? Is your project too special to ship an MVP?
What role do legal, HR, and finance play? How can they help you be more effective, efficient, and successful?
Which meetings should you cancel, and which should you shorten? How do you force people to review documents and make decisions without meetings?
Whats the right size for a team that delivers continuously? How do you get the most productivity for the least cost?
How does reducing inventory improve quality and agility? What can you do to reduce inventory?