Value Points – Estimating the relative value of a User Story

Value Points can be used to measure the relative value of stories using a Fibonnaci Sequence. Although not appropriate or particularly necessary in all cases e.g. primarily when you have an omni-present Product Manager, these can be a useful way to prioritise and convey relative importance to a team. This approach becomes increasingly useful as teams scale to cover multiple projects combined with Business As Usual activities.

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?

Velocity can be used to measure the output of any team…

var dzone_style=”2″;Velocity is a measure of how much work a team can complete in a set period of time.  It is measured in Story Points and although it was originally created for use in Software Development scenarios, it can be used in just about every type of team scenario.
Velocity can be measured assuming you have… :

1 team (1 [...]

Lean, Scrum, Scrum of Scrums and Epic Boards!

So, when do you use Scrum practices, when should you consider Lean practices and when should you consider using Epic Boards?