99 Reasons for Scrum: How customers benefit from Scrum projects

We have discussed the Scrum framework in software development in various of our blogs and in our wiki. The conclusion has always been: it is not an easy task to establish agile methods, however, Scrum is always worth it. In this series of articles, we have collected 99 reasons, why customers, coworkers, and service provider equally benefit from Scrum. First, let's take a look at the benefits for the customer:

The virtual conference about agility Get your free ticket for Tools4AgileTeams on Dec 2nd & 3rd with the voucher FREEWITHSEIBERT - 70 speakers & talks, 8 tracks, over 2.000 participants for networking, and much more ...

Why customers benefit from Scrum Projects

  1. Complex projects require modern, flexible methods. Scrum allows for quick response time, waterfall projects don't.
  2. 82% of all waterfall projects have to deal with massive problems concerning quality, costs or time or may even fail.
  3. Waterfall projects = compromise of time, costs, and quality. Scrum = compromise of time, costs, and functionality.
  4. Scrum avoids exploding money or time budgets.
  5. Studies have shown: Scrum projects run with less risk, more productivity, and lower rates of failure than waterfall projects.
  6. After each Sprint in a Scrum project, the customer receives a fully functional product increment.
  7. Scrum allows for an early marketable software and thus early profits with the product.
  8. With Scrum the product continues to improve while already generating turnover.
  9. Thanks to Scrum, changed requirements can easily be integrated into the project.
  10. Scrum only realizes software functions with business value, and not ones that were anticipated but have become obsolete.
  11. In the scrum project, the budget will always be on the important to do's, and only afterwards on nice to have functions.
  12. The realization of functions strictly follows priorities of the customer.
  13. Changes in the customer's priorities are reflected in the Scrum project.
  14. Scrum allows to react to change requirements within the following sprint, and thus very short term.
  15. Clients are deeply involved into the development process and can detect wrong developments early on.
  16. Lead times with Scrum projects are often shorter than classical approaches.
  17. Scrum projects stand for highest product quality, that is non negotiable.
  18. Scrum projects can be passed to other providers in any stage: less lock-in effect.
  19. As soon as the most important functions are realized, the customer can leave the Scrum project at any time.
  20. Scrum projects can be paused, i.e. in order to get a new budget. In the meantime, the product is live and creates turnover.
  21. Scrum developed software is easier to maintain and expand than classically developed products.
  22. Studies have shown, that Scrum leads to more efficiency and transparency in projects.
  23. Scrum projects offer a constantly visible control of results for continuous improvement.
  24. QA measurements are a permanent part of realizing requirements in Scrum - no questions asked.
  25. The customer always controls the progress of the Scrum project and expected costs.
  26. Scrum projects are expense projects. Only what's done is paid for.
  27. There is no full charge for a quick and dirty product in Scrum projects.
  28. Scrum means, the work load of the customer is better distributed. He does not need to specify all functions in the beginning.
  29. Scrum forces nobody to plan exactly what will be realized in months to come.
  30. If customer requirements change, Scrum can adjust. The customer receives the product with the highest usability.
  31. The Product Owner in the Scrum process is the customer's lawyer and assures maximum customer benefits.
  32. Clearly defined acceptance criteria for features have to be met in Scrum, otherwise the Product Owner will not accept the function.
  33. In Scrum projects, customer and service provider don't work against each other, but work on a common goal.

In essence:

In Scrum projects there are only winners: the customer, the service provider, the staff and the product.

Would you add other arguments? Are you missing arguments? Let us know in a commentary or via twitter @seibertmedia. We are looking forward to your input.

Introduce Agile? We are your partner!

You have questions about Scrum? Would you like to introduce agile in your enterprise? Are you planning a software project and would like to use agile processes? //SEIBERT/MEDIA is an experienced provider for Scrum. We are happy to help you establish agile principles and processes - simply contact us with the form below.

Diesen Beitrag auf Deutsch lesen.

Additional information

Budget planning in Scrum projects and possible reactions to cost explosions
The advantages of pair programming
Reasons why you as customer should test your new software intensively and at an early stage