Troubleshooting large-scale new product development embedded software projects
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
| Hi-index | 0.00 |
To maximize the velocity of business value delivery Alistair Cockburn talks of having a process that is "barely sufficient." At Landmark Graphics we developed some guidelines as to what "barely sufficient" means for our various software projects. We examined over 60 projects and observed two primary attributes that influenced the type of process used: complexity and uncertainty. We provide a scoring model for plotting projects onto a four quadrant graph, which we use to categorize projects into dogs-simple projects with low uncertainty, colts-simple projects with high uncertainty, cows-complex projects with low uncertainty, or bulls-complex projects with high uncertainty. We adapt our agile process from a core set of barely sufficient practices that all projects use and add processes and practices according to a project's profile. One key benefit of this approach has been identifying project drivers and providing early guidance to project teams so that they can start with a process that is close to appropriate.