Guest View: WetAgile combines agile and waterfall



Email    print   
April 1, 2010 —  (Page 1 of 5)
Have you noticed how some organizations claim to be agile, but when you peel back the layers, they’re really a waterfall shop with aspirations of agility?

As a consultant, when given the choice, I usually chose agile over waterfall methods. However, we often end up using the methodology that is in place at the client site… and most development organizations are still waterfall shops.

So why do so many organizations aspire to become agile, yet are still only implementing a few aspects of it? Most likely, they’re not given enough time to plan the process of becoming agile. Or, it may be because agile processes are usually introduced by the development community in a bottom-up style that isn’t understood or appreciated by the top-down management. The result: Many teams end up implementing a hybrid methodology.

Hybrid approaches to solving problems are not all bad.

Let’s call waterfall shops that either aspire to be agile or are in the transition process “WetAgile.” Individuals can also be described as WetAgile, too. For example, perhaps you’re an aspiring agile guru doing so many waterfall projects that you find yourself implementing agile practices that you most believe your waterfall team can easily embrace.

When I look back at some of my own most productive teams, they all had one thing in common: Each project team was using one or more agile processes.

For example, we recently completed a large electronic content management implementation for a client. The team consisted of highly skilled Java developers who had just completed product training. Soon after their training class, the developers moved on to their programming tasks, but they had difficulties figuring out how to wire it all together. They quickly discovered that working together was faster than working independently.

Although I would like take credit for telling them to work together, it was something that they tried on their own. They started with one developer searching the product knowledge base while the other developer implemented code fragments. Within a few days, they were sitting side-by-side, coding and refactoring each other’s code.



Related Search Term(s): agile

Pages 1 2 3 4 5 


Share this link: http://sdt.bz/34245
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Finding the right tool for the agile job
Experts emphasize that tools should bolster the agile process above all else Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb