Changing the way a business operates is a daunting task. It involves assessing and understanding the strengths and weaknesses of the current organization, identifying solutions to the weaknesses without compromising the strengths and, ultimately, changing the way people work. Above all, people tend to be resistant to change — and this is the most common issue that arises when adopting a new methodology.
Agile methods are powerful tools when used properly — but as with all tools, they can be misused. The critics of agile methods are many and vocal, calling Agile a poorly thought-out “shortcut” that fails to get the job done. And with 90% of projects failing to meet objectives, the criticism is valid. So is Agile just hype or is there something to it? And if there is, why are project success ratios so abysmal? Here’s the scoop on why Agile doesn’t work and what to do about it.
People have lost sight of the fact that Scrum is not a methodology. I see comments such as “Scrum is killing agile” and it drives home, with emphasis, that there’s a huge disconnect between understanding what an agile methodology is and what Scrum is (and I know I’m beating a dead horse, but it’s important [...]
Scrum can be remarkably beneficial in many kinds of software projects. But, as with any process, methodology or management technique, when used inappropriately it can cause more problems that it solves. In this article I’ll discuss some of the common misconceptions and “lessons learned” as related to Scrum.
I have a prediction. If you take the Nokia “Scrum Test” you are going to score somewhere less than 7. That means you aren’t doing Scrum, you’re doing “ScrumButt:”
A ScrumButt is a sort of like Scrum implementation… but some changes that were too painful have been left out… Companies in this category tend to only [...]
According to an informal poll conducted by Cranky PM, Agile methods (Scrum in particular) has been penetrating deeply into the enterprise. Specifically, in 2006, you reported that a sizable majority of product development used a waterfall methodology (55%), with Scrum garnering a mere 7%. In 2008, the picture is very different. Scrum and its Agile cousins [...]
Recently I tried out a variant on methodology that I’ll dub Rational Scrum. I’ve been trying to put together a few thoughts about the overall process for months, and finally found some time for it.
Just as people have specializations, so do processes. Applying one process to all situations is just as wrong as calling your [...]
Looking for a fast-paced, easy to digest introduction to Scrum? Check out Hyrax International LLC’s Scrum Workshop or contact me directly to discuss an on-site Rational Scrum workshop. Recently updated for 2010, this workshop will get your whole team up to speed and using Scrum in record time.
Choosing the right tools to get the job done is time consuming. Development process is not a simple, one-size-fits-all equation. Project teams have a wide array of techniques available to them — but it’s important to remember that its the project, not the manager, that chooses the methodology. Understanding the sometimes subtle and not so subtle variations between methodologies is critical. Choosing a methodology that works for the team and accommodates project needs is, at best, tricky. (Reposted from my original article.)