Agile Methodology

Agile Methodology

There are 6 stages to the Agile method, this will be explained below. The overall goal of each Agile method is to adapt, change and deliver working software as quickly as possible, however there are different variations on each methodology but all leading to the same goal. Each teams process flow may vary depending on the specifics project or situation.

The Agile Process Flow

1.      Concept – Projects are envisioned and prioritized

2.      Inception – Team members are identified and set tasks, all funding is put in place and initial environments and requirements are discussed.

3.      Iteration/Construction – The development team works to deliver working software based on iteration requirements and feedback

4.    Release – QA (Quality Assurance) testing, internal and external training, documentation development and final release of the software

5.    Production – On going support of the software

6.    Retirement – End of life activities, including customer notifications and moving onto the next project

Pros

Responding to change - this is considered one of the biggest advantages, agile development practices to bring development team and business to responding to changes. This method doesn’t force a set deadline for a team but must still be done within a certain time limit.

   ·         Customers get solutions to the problems they value most, sooner

   ·         Stakeholders can prioritize things in a progressive manor reflecting actual market conditions at a         given time

   ·         Developers feel valued, since they’re working on things that actually matter and will receive               frequent in-depth feedback from the very people using the product

Faster Review Cycles – The more each review is done for the project and had changes made, the more they’re done the better the quality of the project will be after each one and they’ll pick up on speed.

Greater Flexibility in releasing features – as agile methodologies have so many more reviews it allows greater flexibility with clients, allowing change requests

Cons

Lack of understanding – One of the drawbacks of agile development is that a lot of people might not understand what it means to be agile by making unsupported assumptions, by making it an agile project but not wanting to invest the time, money, or effort to actual educate management or employees about how he principles apply.

Flexibility can lead to Bad Behaviours – Another common problem, leading from a lack of formal training or understanding that can make people blame others due to issues or make dysfunctional choices made by the team.

Lack of Predictability – Agile methodologies can potentially take 12-24 months or potentially longer as there is so set roadwork on when it should be delivered by.