Agile Series Part 1: The "Typical" Agile Project
After spending the past few weeks working with the Agile projects in QSM’s historical database, I’ve become interested in Agile Development Theory, particularly due to its popularity. While spending days at a time examining our database, I’m left with numerous data-driven questions. Therefore, I thought I would take this opportunity to write a series of Agile-related blog posts.
QSM’s database contains over 100 Agile projects from the U.S. and abroad. The projects include a variety of application types and their top three programming languages were JAVA, C++, and VB.NET. Seeing this, I thought it might be interesting to examine the “typical” Agile project according to our data.
So what does the “typical” Agile project look like? For consistency purposes, I limited the sample to IT systems projects completed in the last six years. I measured the Duration, Effort, Average Staff, and MTTD at various project sizes to see how they compare.
Below are two figures that give demographic information about our “typical” Agile projects:
This scatter plot shows the individual Agile projects compared against QSM’s Business Agile trends.
Size (SLOC) |
Duration (Months) |
Effort (PHR) |
Average Staff |