Whats wrong with having too many PMs? How do you optimally pace your team?
An opinion column for developers. Brutally honest, no pulled punches.
Whats wrong with having too many PMs? How do you optimally pace your team?
When is stabilization between milestones needed? How can stabilization lower quality, productivity, and morale?
How long can you wait to make a decision? What role does preparation play in making ambiguous decisions?
Whats a quick yet responsible way to read your e-mail? How do you write a short yet effective checklist?
Why are general solutions so tempting and yet so evil? How can you avoid temptation and deliver more value?
Should you have a dedicated SE team or should the core team code and test updates? How do you prevent the core team from being randomized?
How do you optimize properly? What should you optimize against?
Why do are we moving to distributed development? What three things make distributed development dysfunctional?
Why are most specs nearly impossible to review, use, and maintain? How can we make specs better?
Is spec writing a waste of time? Can formal specs be made obsolete?