Is agile suitable for all projects?

At some point in your agile journey you begin to ask and/or hear this question: “Is agile suitable for all projects?”

Here are some of the responses I’ve heard from both those who are still learning about agile and those who have a lot of agile experience:

  • Agile isn’t necessary when you have a known problem and a known solution.
  • Agile doesn’t work in regulated environments.
  • Agile doesn’t work in government.
  • Agile can’t work in a large enterprise.
  • etc.

In my opinion and experience all of these answers are borne out of legitimate concerns but none of these responses are valid. Let me explain why.

One of the significant differences between traditional projects and agile projects are the short feedback loops. These short feedback loops allow teams to validate assumptions sooner, identify and deal with risks and issues sooner, find and correct defects sooner, and deliver a solution sooner. Agile will be implemented differently based on the project types identified in the responses above, but I believe that all projects will benefit from agile’s short feedback loops. To say otherwise assumes that we always get it right the first time – even in the uncommon situation where the solution is 100% known, we get everything right the first time about 0% of the time. Agile helps us discover that sooner so that we can correct our mistakes.

Additionally, any project can benefit from increased trust amongst team members, increased trust between teams and customers, increased trust between teams and management, and increased trust of project status.

In my opinion and experience, the only question you need to ask has nothing to do with the type of project, the type of problem, or the type of solution. Instead, here is the key question:

Does the team want to use agile and have the support to do it?

If the answer is yes, then it can work. If the answer is no, it is not likely to work.

P.S. Here are some examples of agile being used in projects and organizations where “agile won’t work”:

Agile in a regulated environment.
Abbot Labs experience report
– Development of a nucleic acid purification platform and companion real-time analyzer
Agile in a Regulated Environment – Linkedin Group

Agile in government.
Public sector case study
– Social Security domain, software to support change in legislation.
Manitoba Parks Reservation Service
– Agile case study as told by Terry Bunio.

Agile in a large enterprise.
The agile experience at John Deere’s Intelligent Solutions Group
.- presentation by Chad Holdorf at Much Ado About Agile VI – Vancouver 2011.

Agile with a known solution and a known problem.
I recently completed a project with a known solution and a known problem – converting a VB6 application to dotnet “as is”. We used agile and the project was very successful.

Re-posted from

About WinnipegAgilist

Steve Rogalsky - An agilist and team member at Protegra with a passion for agile and lean principles and practices. Green bar addict, agile player/coach, teacher, dad, husband. Email: steve.rogalsky at protegra dot com


No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: