Last Updated on Thursday, 06 January 2011 09:37 Written by Ing. Jerome van den Berg

Sadly it is a well know fact: after 9 months you have finished your development project but it is not what your customer wanted or needed. Now you have to spend a lot of money and time fixing the product. Wouldn't it be nice to avoid the risk of not meeting your customers’ expectations? Scrum can help you! The more traditional methods like Rational (RUP) or Waterfall let you spend a lot of time on creating the best set of requirements. This can take a lot of effort but can still present you with the same problem: not meeting the customers expectations.Scrum has a different approach. Still you need to know what your customer wants and you still have to spent time on getting the requirements detailed and prioritized. The prioritized items have to be detailed enough for the developers to get started. The developers can manage a maximum of 30 days of work during each development cycle (called a SPRINT). After each sprint the developers deliver a demo, showing off their accomplishments. This way your customers will see results after every sprint. This gets your customers excited, but also enables them to comment on the development. If there is a mismatch, you can adjust it in next sprint.This is a more organic way of developing. It delivers more involvement, control and in the end better and more usable products than other methods. Login to comment.