software-development

Why project teams should embrace Agile methodology

Imagine having spent thousands of dollars on a project, and then presenting an output to the business that doesn’t meet their expectations or the requirements.  This scenario often unfolds with the traditional waterfall project approach. Even if the project delivery team held a monthly demo (best case scenario in most cases), there is still the chance that project has gone adrift by a month. Even if you have a small team working on a project, that could still equate to thousands of dollars in sunk cost.  

In contrast, Agile methodology eliminates the traditional pitfalls of waterfall project methodologies with processes such as dividing project deliverables in manageable installments and engaging the end users in the full project cycle.  

Agile-methodology

There is a lot of context available on Agile principles and process, however, at a very high-level, the following are the basics of how Agile projects are run:

  1. Work is estimated for 2-weeks at a time (these intervals are called ‘sprints’).
  2. Status quo are parked outside the agile room; all project members are on an equal platform and each member has a specific role to play.
  3. At the beginning of each sprint there is a sprint planning session where  the deliverable is identified and each member writes down her/his tasks to perform in the next two weeks. Each task has an effort estimate (in days or points).
  4. Collaboration happens face to face in the project room (when applicable) and therefore, less time is wasted in electronic communication.
  5. There is a 10-15 minute daily scrum where each member identifies three things:
    • What they worked on the previous day
    • What will be they be working on the current day
    • Are there are roadblocks
  6. At the end of each sprint there is a product demo and a sprint retrospective.
    • This is a great time for the product owner to give her/his feedback. The feedback can be taken into account at the next sprint planning session, depending on the severity.
    • The sprint retrospective is a great time to identify what the team did well, what didn’t go so well, suggest improvements and register appreciations

Organizations and project teams sometimes find it very complicated or overwhelming to adapt Agile methodology, however, there is a pattern, and fortunately the paradigm becomes seamless after one or two sprints. The benefits of Agile are immense, from economics, to team engagement and speeding up project delivery.  

At Mantrax we are big advocates of Agile and we can help any team adopt this amazing development paradigm. If you're interested in going Agile, please reach out to us for a no-obligation consultation.

 

One Trackback:

[…] the full article on why projects teams should embrace Agile methodology and see the advantages it offers over waterfall project […]

Comments are closed.