Article

Strengths of Agile methodology...Appropriate to all project models?

Agile methodologies are becoming famous, useful and well-known by all organizations. However,
what new do they bring us against traditional models? That's an interesting issue to focus on.
I'm sure you will agree with me when I say that waterfall methods have always been successful.
Starting with a requirement definition, followed by an analysis/design and finishing with an
implementation/testing phase, defines most of the project approaches. Thanks to that , it lets us plan
and control the delivery date of the project. Normally, teams work with this plan in a
communicative mode with business department in order to well understand their needs.
Nevertheless, projects face changes that need to be re-planned. Depending on the alteration projects
assume them taking the risk of exceeding road maps and exerting pressure to development teams.
Agile methodologies such as Scrum or Canban show us the importance to stop and to establish a
strong communication with business stakeholders during project's milestones. Therefore, it provides
iterative phases called sprints that start with requirement planning, then product refinement, next
product retrospective and finally product review. As everyone can imagine business takes part of the
team and communication is a must. Business shares and controls project information and also
review if product is being built according what they expect. Furthermore, teams adapt to business
involving a motivated situation and wonderful work climate.
So what's the answer between waterfall or agile? On a personal note, I have had fantastic
experiences with agile methods where teams feel motivated and deliver high quality products.
Despite this, waterfall will always be one of the most methodologies used that need to be adapted
into these new models. After all, teams adapt to every situation where they feel comfortable to
work.
Alvaro Pariente.