Integral Agile Journal
Posted on: September 6th, 2014
In this series of posts, I will discuss common (and not so-common) problems faced by teams and their leadership trying to adopt Agile practices.
Posted on: July 25th, 2014
Thesis: agile methods can save you money. Are you getting your share? Systematic adoption of agile methods can substantially reduce your project costs; however it can be hard to get these results right away. Most new agile teams don’t see these results until the 3rd or subsequent project. That’s where we come in.
Posted on: June 20th, 2014
The worst thing any team can do is to raise expectations through early success, but be unable to sustain the pace. This happens to many Agile teams due to some simple mistakes made in tracking Team Velocity. As a result of these painful misses, some organizations are getting a bad taste for Agile, and are once again looking to the next big idea to get the performance they want.
Let’s look at the formula for velocity: Velocity = Story Points Accepted/1 sprint
Pitfall #1: Story Points Accepted.
Posted on: April 7th, 2014
Velocity is the primary measure of the performance of an Agile team.
The Agile manifesto values “Finished Software” as the primary deliverable of a team, and team velocity is an agile metric that measures that directly.
Measuring Team Velocity:
Posted on: February 3rd, 2014
This series of articles delves into the sticky topic of Agile metrics. Let me state right off the bat that this is NOT focused on measuring the performance of an Agile team for purposes of benchmarking or report-card scoring, although you will get some nice data for this purpose if you follow along.