My talk from Agile Vancouver is now online. In this talk I get audience members to put on costumes and act out skits demonstrating different ways to collaborate as a team to improve quality.
I was interviewed by Bob Payne when I was in Las Vegas speaking at Agile Development Practices earlier this year. You can listen to it here.
In the software development lifecycle there are two types of milestones that occur on the path to delivering working software. Let’s take a look at each.
The first is simply a marker to indicate that we have complete a major task or phase of the project. When this type of milestone occurs we automatically move on to the next phase or step of the project. Examples of this type of milestone are “Development Complete”, and “Show and Tell”.
The second type of milestone is one in which an evaluation is made. Based on the result of that evaluation the work either moves forward or some form of rework is required. Examples of this type of milestone are “Code Review”, “Functional Testing”, and “User Acceptance Testing”. It is this second type of milestone that we will focus on for this blog entry.
On September 28, 2010 I was the guest speaker at the Cleveland Agile Group. For those of you who asked, here are the slides from that talk.
Some time ago I experienced an all too common pattern when working with software development teams. This pattern has to do with the way development projects are prioritized and scheduled. In my opinion this pattern is one of the largest areas of waste in the software development field.