The Agile Balanced Scorecard – Tracking the Reliability of an Agile Software Development Team

Reliability is one of the four performance measures that you should consider when building an Agile Balanced Scorecard. The other three are Value, Velocity and Quality.

Using Velocity to measure the Productivity of an Agile Development Team

Although you can not use Velocity to measure the productivity of one team compared to another, you can use velocity to help track the relative productivity of the same team from one sprint to another assuming the value of a point stays the same over time.

Calculating the ROI of Implementing Agile Practices – Agile increases output and efficiency

So, it’s no secret that one of the big benefits of ‘going agile’ is the ability/opportunity to track and optimise team performance.

The big question from a programme management and business perspective is:

How do you measure the operational costs/savings associated with improved efficiency or increased disruption within an Agile Software Development team?

Does Agile Programme Management Exist?

So, the following questions are justified:

* What is Agile Programme Management?
* What is Agile Portfolio Management?
* Is it possible to efficiently and effectively manage a Programme of Software Development Projects in an Agile way?

Minimising the impact of Sprint disruptions

One of the biggest challenges we’ve faced is trying to balance project work or product development with business-as-usual (BAU) work that can’t necessarily be anticipated – how do you manage the risk of disruption?