Scrum Tool Home

Online Scrum Software Development Blog

Digg This! Post on Facebook! Post on Yahoo! Post on Reddit Post on Delicious Stumble This! Tweet This! Post on Google

Thursday, August 5, 2010

The Advantages of Agile Scrum Software Development

When you start working on a project which will be developing software, you will quickly discover that the development methodology used will have a major part to play in the speed and quality of the code developed. Since Agile Scrum methodology is so widely used it is important that you understand the advantages and disadvantages of it so that you are able to determine whether it is the best fit for your project deliverables.

  • Agile scrum helps the company in saving time and money.
  • Scrum methodology enables project’s where the business requirements documentation is hard to quantify to be successfully developed.
  • Fast moving, cutting edge developments can be quickly coded and tested using this method, as a mistake can be easily rectified.
  • It is a lightly controlled method which insists on frequent updating of the progress in work through regular meetings. Thus there is clear visibility of the project development.
  • Like any other agile methodology, this is also iterative in nature. It requires continuous feedback from the user.
  • Due to short sprints and constant feedback, it becomes easier to cope with the changes.
  • Daily meetings make it possible to measure individual productivity. This leads to the improvement in the productivity of each of the team members.
  • Issues are identified well in advance through the daily meetings and hence can be resolved in speedily
  • It is easier to deliver a quality product in a scheduled time.
  • Agile Scrum can work with any technology/ programming language but is particularly useful for fast moving web 2.0 or new media projects.
  • The overhead cost in terms of process and management is minimal thus leading to a quicker, cheaper result.

In a nutshell this means that you can get development started fast, but with the caveat that the project scope statement is "flexible" and not fully defined. Hence this can be one of the major causes of scope creep if not managed properly.