The engineering manager’s lament by Eric Ries:
In teams that have a business culture, the MBA’s pick time. After all, our startup is on a fixed budget. They set deadlines, schedules, and launch plans, and expect the engineering team to do what it takes to hit them. If quality suffers, that’s just the way it is. Or, if they care a lot about quality, they will replace anyone who ships without quality. Unfortunately, threats work a lot better at incentivizing people to CYA than getting them to write quality software.
* Practice five why’s to get to the root cause of future problems. Use those opportunities to add tests or alerts that would have prevented that problem. Make the investment proportional to the problem caused, so that everyone (even the business leaders) feels good about it.
Excellent post, focused on software development but with usable information for anyone seeking to improve management practices.
Related: Amazon S3 Failure Analysis – IT Talent Shortage, or Management Failure? – Future Directions for Agile Management – Why Extrinsic Motivation Fails – If Tech Companies Made Sudoku