15 49.0138 8.38624 1 0 4000 1 http://blog.zilicus.com 800 true

Waterfall / Traditional or Agile Project Management Approach? Which one is right for you? – Part II

Traditional or Agile Project Management Approach? Which one is right for you?

There are certain principles and differences between agile and traditional project management approaches. We looked at those in previous post Waterfall / Traditional or Agile Project Management Approach? We should also understand that purest form of traditional (or heavy) or agile project management may be applicable to certain industries or specific kind of projects. In real practice, the line between these two may blur.

Yet, if you have to consider these two approaches distinctly and make a decision – let’s look at project aspects, or project scenarios that can help you choose between traditional or agile project management approach

traditional or agile project management approach

#

Project Aspect/ Scenario

Use Agile Project Management

Use Waterfall Project Management

1

Project complexity, duration, size

If smaller – can use agile

If larger –Waterfall approach can be useful

2

Does key stakeholder (primarily customer) has upfront clarity of requirements as
well clear idea about final outcome before project is kicked off

If answer is no, go agile way

If answer yes, then waterfall is more suitable

3

Does customer requirement, project scope is changing or expected to change through project
lifecycle

If answer is frequently, then agile approach is better.

If answer is not often, then waterfall can be a choice.

4

Expected/required ongoing customer engagement throughout project lifecycle – high

Go agile.

No

5

High level customer engagement– Primarily expected in the beginning and during User Acceptance Testing (UAT) phases. Intermittent and low level engagement expected during project execution

Agile may not be most preferred choice

Go for waterfall approach

6

Is your team adaptive, skilled (or trained to be) for frequent scope changes/ dynamic/rapid delivery model

If yes then Go for Agile

If not ready, then take it slow

7

Extent of Interface and integration with external processes, systems

If basic – Yes

If complicated and significantly interdependent – take waterfall approach

8

Desired Time to Market

If short and with rapid incremental improvement expected- Yes

If all deliverables expected in a stipulated timeline – Yes

9

If project documentation for audit and compliance purpose are required

No

Yes

 

For any of these approaches to succeed, it is important to have

Post by Dhan Wagholikar

About Zilicus

Zilicus offers the best project portfolio management tool ZilicusPM, with robust project management tools capabilities and easy ways to track project management KPI,

Know more about project portfolio management, Gantt chart, best project management tool, project management office, project management tips, project planning guide, project risk management, project scope management, effective project management, project manager guides and know more about Project Portfolio Management Software, Project Management Software Guide.

 

Share:
PREVIOUS POST
Agile Vs Waterfall Project Management Approach
NEXT POST
Being a Project Manager Part-I
ABOUT
Dhan

I am a co-founder of Zilicus Solution and I write about project management, collaboration, productivity, project management software, cloud computing, requirement management and business empowerment.

1 Comment

LEAVE A REPLY