Jun 17, 2012
Welcome to the Software Process and Measurement Cast 191!
The SPaMCAST 191 features part 2 of my essay "Who Owns Estimation In Agile Projects?" Haven't listened to Part 1? Click the link!
Part two begins:
What does ownership mean in terms of accountability and responsibility? When something belongs to you or is directly related to your actions, accountability and responsibility are directly inferable. Unfortunately, even though we are quick to assign ownership, responsibility and accountability we fail to ask, who really should own an estimate or whether they can be accountable for the estimate if they can’t do the work or control those that do. In corporate environments, ownership is generally not about ensuring the best flow of information but rather who can be pilloried when an estimate is missed. Sound like hyperbole? I recently heard a C level executive say “whose neck can I wring if we miss the date and the budget” when talking about a project, therefore a quick tour of the why estimates are created and who “should” own them in an agile environment is in order if for no other reason than health and human safety.
Shameless Ad for my book!
Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: "This book will prove that software projects should not be a tedious process, neither for you or your team."
News! . . . We also just got word that the SPM book has been adopted for a class at the University of West Flroida for the Fall.
Contact information for the Software Process and Measurement
The Software Process and Measurement Cast 192 features my interview with Mitch Lacey. We discuss his new book, The Scrum Field Guide. It was a great interview filled with useful advice.