In this article the author shares his thoughts and experience gathered while working together with DEV teams, trying to make sense of metrics. He introduces the practice of Metrics-Driven-Development: using metrics to drive the entire application development.
While there are many methods that use stories as a means for prioritizing development, there's a basic divide that asks whether it should be done with numbers or without. There are arguments on both sides, but instead of examining these, people tend to fall into one side naturally. Once there, they can become quickly entrenched in the belief that the other camp is foolishly mistaken.
Building on their work on Real Options, Chris Matts and Olav Maassen are writing a graphic novel to explain the concepts and share their knowledge in the area. They discussed the novel, the process of producing it and the crowdsourcing model of funding with Shane Hastie from InfoQ. A sample chapter is available for InfoQ readers to download.
Our panel of leading experts explores some of the challenges and thought processes that go into making their apps as scalable and performant as possible. 1
Developers and the business use numbers differently, leading to poor communication. Here the "Spirit of Agile" tells a developer the trick: translate non-computational issues into number language. 3
Based on traditional Earned Value Management (EVM) metrics, AgileEVM is adapted for an Agile PM context. It allows Agile and traditional projects to be tracked within a single program. 7
Kenji Hiranabe shows how to track project status using Kanban Boards from three viewpoints (Time, Task, and Team) to enhance self-organization and collaboration. 15
Traditional budgets demand committments based on variables beyond managers' control. To support the adaptive organization, Jim Highsmith proposes a two-part model for project and team performance.