Project management methodologies – Which one to choose?

Every project is a unique experience and so is Project Management. Management of a project is not particularly an easy task especially when there are so many methodologies available to choose from.  The traditional – Waterfall Project management, Extreme Project Management, Agile Project Management are at the top of the list. While a lot of organizations have chosen “a” method, some have become more confused than ever.

“Agile” has become as popular, common and sought-after term in  recent years. People hear that Agile methodologies have enabled organizations to respond quickly to changing markets, have resulted in improved efficiency and elated customer satisfaction. For Software Development projects, it sounds like not having the understanding of or visibility in Agile methods makes one feel left behind. Then what is it that makes people not so comfortable with shifting some of their projects, towards Agile.

Considering the Waterfall and Agile, though I do not feel Waterfall doesn’t work, here are some important points to know on how Agile is different from Waterfall and how it can be better for us.

 How and Why Agile helps:

What does Agile allow us over and above the traditional Waterfall Model? What does Agile Manifesto mean to us?

1. With Agile, clients can be involved during the development process: In modern age, for Software Development projects, client wants to be involved during the development as often as possible for adding their opinions and clarifying how exactly they expect their software to work.
2. With Agile, business analysts, designers, developers, stakeholders can work together and simultaneously. Traditionally, in waterfall, by the time the developers get to the project, the Designers and Architects may now have other projects on their priority list.
3. In waterfall, a requirement needing a design tweak during the development process has to be put on a future-items bucket based on the deadlines and budget. This at times leads to customer concerns. Here Agile allows us to keep evolving the design and even the requirement set.
4. Agile allows us to eliminate the processes which are a burden more than a benefit. Requirement or design change does not need lot of rework thus saving money and resources.
5. With Agile, a larger project can be broken down into smaller ones. A project can be done in multiple deliverables as part of smaller cycles called Sprints. This provides better clarity over deliverables. At the end of each sprint, a tested potentially deliverable product is released.
6. A product in front of user’s eye, triggers the thought process and allows him\her to provide useful feedback.
7. And YES, Agile can meet strict budget.

 So, looks like it is easy. Right? Agile is a mindset shift and does not need complete rewiring to have the teams go Agile.

Are we saying Agile replaces Waterfall then?

In my opinion, the answer is No. We are not saying that.

It is just that for most Software Development projects, Agile is a better method than Waterfall. Projects like Metro Railway Network Development would need the team to follow Waterfall model for the overall project and can have some modules designed and developed using Agile Methods.

We must find the best way to appropriately apply our knowledge, skills, tools and techniques to project activities and meet the project requirements.

Keep Building!!