Agile Metrics

Abstract Chp. 9

Scrum is a popular project management framework for agile projects. Scrum projects are typically managed quite informally, with the only metrics used being various velocity metrics and burndown charts. Because these metrics only measure the speed of delivery, not the project’s cost or the business value it generates, many project managers are resistant to Scrum. One of the major differences between traditional and agile projects is that traditional projects focus on delivering software that satisfies requirements, while agile projects focus on maximizing ROI through continuous feedback and re-planning. That is, the focus of agile projects is on business value rather than conformance to requirements, and so Earned Business Value (EBV) metrics can be crucial. Of course, it is also important to know how efficient and effective the team is in doing the work that provides Business Value, so Earned Value Management (EVM) metrics are also applicable. In fact, EVM metrics are easier to calculate and understand in agile environments than in traditional ones. In this paper, we describe how to use three management metrics – Cost Performance Index (CPI), Schedule Performance Index (SPI), and Earned Business Value (EBV) – to provide information to help manage an agile project. We also demonstrate (through a simulation) that (even) large changes in the SPI and CPI metrics don’t necessarily mean a significant change in EBV.



ore to follow …

Amazon Wish ListBitty BrowserBlogger PostLinkedInPlaxo PulseRedditWordPressTwitterStumbleUponSlashdotTechnorati FavoritesPingHuggGoogle ReaderGoogle BookmarksDeliciousBlinklistFacebookShare