1 Comment

Agile Development or Traditional Waterfall Approach?

by Phillip Smith

Our clients rely on us, their IT team, to move them to a future state of better technology, better business process integration, and stronger competitive advantage. Our challenge is to get them there as quickly and inexpensively as possible.

Facing up to that challenge means that IT organizations must look for better ways to do things.  New efficiencies can be found in many areas: staffing, training, monitoring of status, cost, tools, planning, and the list goes on. But here I’ll address the “approach”—specifically, the decision of whether to use waterfall or agile in the organization of your project events.

Project managers should avoid any personal bias toward waterfall or toward agile. Every project is different, and some will fit better with waterfall while others will fit better with agile.  The decision is no different than deciding whether to use a hammer or a screwdriver: you need to know what problem you are solving, and then reach for the correct tool. Continue reading