Is Agile actually Agile?
In 2010 Dr. Dobb’s IT Project Success Rate survey* put success rates for agile/iterative projects at around 60%, and traditional waterfall projects at 47%.
Why is there only a 47% success rate for projects using the traditional waterfall method?
Teams do their best in understanding the requirements; business analysts creates requirement documents and then development teams start with initial requirements, and according to their own understandings, they create the product. At the end of the project when they deliver the product to their clients, the Client is not happy and satisfied, thus leading to failure of the project.
The two main root causes of this are:
- Everyday Changes in Market and
- Lack of Communication which leads to misunderstanding the requirements.
Organizations need to accept this everyday change in market. They need to mould their development processes accordingly. This is one of the strengths of following the Agile method.
Scrum is all about “How we accept changes? How we respond to changes?”.
Communication plays a vital role in any project. Meeting with client in a certain amount of time and inspecting a product and improving it, leads to customer satisfaction and trust. Thus, leads to good relationships between development teams and their clients.
IT Hands has adopted the Agile process successfully. It follows a simple approach of “Inspect & Adapt”.
Scrum focuses on delivering functional bits of the application to client as soon as they are ready. Everyone on the team including the product owner, “Inspect” those functional bits of the application and “Adapt” the changes required in that.
This process goes with incremental approach of moving towards the completion of the project with getting each functional bit completed and approved from the client. Contact us to learn more about Agile software development.
* http://agileoperations.net/index.php?/archives/90-Agile-success-rates.html
