After a past experience with Scrum I wanted to write about the conditions under which Scrum projects can fail. A Google search located a presentation from Joseph Pelrine and Jiri Lundak describing a workshop they ran to reveal why Scrum projects fail (http://tinyurl.com/9j2az6). Pelrine and Lundak’s workshop starts by considering the conditions for project failure. This seems like an important first-step but I realized the question may be misleading.
I’m going to use a different approach by asking the question; under what conditions is Scrum applicable? Why ask the question? I was watching Ken Schwaber’s Google Tech Talk video titled ‘Scrum et al’ (http://tinyurl.com/j58cr). 29 minutes into the video Ken states 30-35% of Scrum implementations succeed. What happened to the other 65-70% of Scrum implementations?
After further consideration the question can be broadened to other tools/techniques/methodologies for running software projects, for example; under what conditions are Gantt charts applicable? or, when is waterfall development applicable?
Changing the question helps me address other persistent questions like; why do we still use Gantt charts? Why is waterfall development still used?
Take a look at your own project; what tools, techniques and methodologies are you using? Now comes the hard question; why do you use them?
December 31, 2008 at 3:15 pm |
Neither my father or grandfather were software engineers, but both always told me the same thing growing up: “use the right tool for the job.”
Using the correct tool allows you to focus your energy where it’s important. Software or otherwise, all of the successful projects I’ve been a part of had one thing in common–use the tools that will help you deliver, throw the rest away. Don’t use C++ for a task when a simple shell script will do. Don’t use a screwdriver as a chisel. Don’t blindly apply a software methodology to your project where it doesn’t fit.
Part of the problem with agile development methodologies is that they’re only very recently becoming popular, and as such we’re just figuring out what parts work and what parts get in the way in a given environment.
January 4, 2009 at 4:50 pm |
Having the right tool for the job is a key component of project success; regardless of the project E.g. software or home-improvement.
The insight I’m reaching is we have to understand what the job entails. Stay tuned on my next blog-entries because I’m going to address understanding the job. Your comment about using a methodology where it doesn’t fit is salient; I’m going to propose a definition of ‘fit’ that can help us select a methodology/approach to software projects that may help.