Nov 20, 2011
Welcome to the Software Process and Measurement Cast 161!
The SPaMCAST 161 provides an overview of a pallet of metrics tailored to agile projects. The essay begins:
When talking about metrics to measure agile processes one should begin by defining “why” you want to measure followed immediately by “what” we will do with the data when we know it. As I have noted before there are only two reasons to measure. The first is to generate specific behaviors and secondly to predict the future. Organizational goals provide the rational for what to measure and the type of measure determines whether it drives behavior or provides direction.
Interested in the PMO Leader of the Year award? Check out www.leadingsuccessfulpmos.com
The PMO Leader of the Year Award will be presented to the PMO Leader, nominated by their PMO team, who shows the most excellent leadership and understanding of what a PMO can deliver to a business.
A panel of independent judges will review all submissions to consider how each nominee has led their PMO over at least the last 12 months and how they plan to grow the PMO under their stewardship in the coming months.
Interested in becoming a radio star?
Are you interested in writing and reading reviewing tools or books? Drop me a note at email@example.com if you have an opinion!
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."
Have you bought your copy?
Contact information for the Software Process and Measurement
SPaMCAST 162 features my interview with Rafal Los on security and metrics desinged for security practices!