Even if Agile was initially considered as an anarchic approach due to practices like self-organization, the reality is that it requires a lot of discipline. Metrics is an important tool to assess the continuous improvement efforts of Scrum teams. However, setting a good metric program is not obvious. The book “The Agile Culture” contains interesting thoughts about what could make a metrics program fail.
This session is born of the hard lessons learned from years of working with diverse companies using metrics to improve their software development processes. Come learn from our successes and be warned by our failures. This session covers what makes an effective Agile metric, the pitfalls in designing metrics, and the basic principles for using metrics appropriately.
Technical debt is one of this great new metaphor that is applied to software development and more specially to agile project management approaches like Scrum. As its financial counterpart, technical debt is not necessary a bad thing as long as you are able to manage it wisely. In this article, Don Reinertsen will help you to put some numbers on the costs and benefits of your technical debt.
When you start scaling Agile, you might need more metrics to assess you software development process. In this article, Janani Rasanjali Liyanage proposes some metrics that adhere to Lean and Agile principles to measure business agility in terms of predictability, reliability and adaptability.
As Scrum is the most popular framework adopted by organizations adopting an Agile approach for project management, many companies are trying to find financial facts that justify its adoption. This article discusses the topic of evaluating the return on investment (ROI) of using Scrum and Agile project management approaches. It suggests some hints about mistakes to avoid and on how to get meaningful results from this activity.
“You can’t manage what you don’t measure” is an adage that is popular in project management. However, metrics programs are not easy to implement and have their dark sides. In their book “The Agile Culture: Leading through Trust and Ownership”, Pollyanna Pixton, Paul Gibson and Niel Nickolaisen provides some advice about implementing metrics, the Agile way.
At the end of each sprint, the Scrum team take some time to think about what could be improved in its Agile process. In this blog post, Natalie Warnert discusses how you could also use the retrospective meeting to look at story sizes after the sprint and determine if they were correctly sized as far as story points are concerned.