Child pages
  • 99 Reasons for Scrum: How customers benefit from Scrum projects
Skip to end of metadata
Go to start of metadata

October 15, 2012 by Matthias Rauer

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. We have collected 99 reasons, why customers, coworkers, and service provider equally benefit from Scrum. Let's take a look at the benefits for the customer:

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.

Why staff benefits from Scrum 

  1. Scrum means motivation through responsibility and organization within the team.
  2. The team itself  is in charge, instead of following strict rules.
  3. The Scrum process forms teams, that join forces - no loners or secrecy.
  4. Scrum allows for evenly distributed work load. There is no overtime prior to a release date.
  5. The team only attempts for each sprint what it can handle, without setting unrealistic goals.
  6. Scrum means less miscommunication. Communication is central: daily standup, review, retrospective…
  7. Scrum means less uncertainty. Current to do's are specified explicitly, otherwise they will not be realized.
  8. Scrum creates transparency for the next tasks. A customer call does not suddenly create havoc.
  9. Scrum stands for higher productivity. That means more development and less bureaucracy. And that's fun.
  10. Thanks to Scrum, developers are never forced to deliver something, that they would not be proud of.
  11. Scrum teams do not deliver unfinished results. To be proud of the quality of your own work is part of Scrum.
  12. It is cool to develop quality software, instead of half finished, unclean solutions.
  13. 72% of Scrum users say, that Scrum has led to higher team morale.
  14. Retrospectives in the Scrum process assure, that the team is on the same page and is working together effectively.
  15. Retrospectives are perceived as useful, interesting, cleansing, and relaxing by many Scrum teams.
  16. Everybody in the Scrum team can voice their opinion and all opinions are equally important.
  17. Scrum means communication at eye level with the customer.
  18. There is a direct exchange between developers and users or customers in Scrum.
  19. Scrum teams take decisions autonomously.
  20. Unrealistic estimates of effort lead to stress. In Scrum, estimates are as realistic as possible.
  21. In Scrum, estimates do not come from above, the team makes the estimates themselves.
  22. In a Scrum team, no manager will suddenly intervene and disturb.
  23. Scrum teams find solutions together and unanimously. There is no decision making by a project manager.
  24. During a Scrum sprint, the team can fully focus on developing - without changes from outside.
  25. It is no longer necessary to realize features that were planned, but have become redundant.
  26. Everyone does everything. Annoying tasks no longer get stuck with one team member.
  27. Modern concepts, such as TDD, Continuous Integration and Pair Programming are fix parts of many Scrum projects.
  28. Scrum allows for change: project times are often shorter than in classical projects.
  29. Scrum is communicative and interactive. Coordination happens in person on the board, not via anonymous electronic systems.
  30. The team continuously reflects their work and collaboration during the Scrum process, to create optimal conditions.
  31. No constant back and forth between to do's. Only few user stories are worked on simultaneously in a Scrum sprint.
  32. Scrum reviews, where results can be presented proudly are moments, which everyone anticipates.
  33. Scrum means more contentment, involvement, and appreciation for staff. 

Why service providers benefit from Scrum

  1. Do enterprises increase their efficiency and their results using Scum? 86% say "yes".
  2. Scrum means higher compatibility of IT and business goals.
  3. 100% of business that use Scrum judge this method as very powerful.
  4. Scrum leads to higher productivity in teams.
  5. Two thirds of companies who use Scrum indicate, that Scrum has simplified the development process.
  6. Scrum projects mean less risks - for the customer and the service provider.
  7. 83% of agile businesses indicate a higher customer satisfaction thanks to Scrum.
  8. 84% of agile businesses say that the use outweighs the efforts for introducing Scrum.
  9. Scrum leads to higher discipline in the development team.
  10. Scrum creates more efficient projects and thus billable times instead of bookings of "internal organization".
  11. Scrum allows for transparent team workload and reliable scheduling of capacities and resources.
  12. Scrum increases flexibility. New customer requirements can be integrated, without challenging the project or additional costs.
  13. Full functional teams: Also teams that are not directly involved with the product can be integrated in Scrum.
  14. Inspect & Adapt: The continuous adjustment in the Scrum process is powerful and increases flexibility of the service provider.
  15. Scrum relieves management in daily business.
  16. Scrum does not make the manager obsolete. It just changes his or her tasks.
  17. In Scrum projects decisions are made where there is information.
  18. Scrum leads to motivated employees. Over 90% of businesses that work with Scrum attest to that.
  19. Due to Scrum, employees have a more even workload and are thus more content.
  20. High product quality = proud Scrum team and identification with the result and the company.
  21. Thanks to Scrum, employees continuously evolve and become more valuable for the company.
  22. Scrum creates a cultural and organizational change, which allows the whole organization to benefit.
  23. Scrum techniques are adaptable: 25% of agile corporations use Scrum approaches, even in non IT projects.
  24. Waterfall projects stand for haggle and mistrust from the beginning. Scrum creates transparency.
  25. Annoying chore charts are not part of Scrum projects.
  26. In waterfall projects, in the end, the customer or the service provider end up paying more. Not in Scrum projects.
  27. Scrum means, what was realized, will be paid. No more and no less.
  28. With Scrum there are no more detailed discussions, whether a functionality is additional expense or not.
  29. Thanks to Scrum, expense estimates are realistic and don't need to be completed months before realizing the project.
  30. Scrum projects make happy clients, without arguments about cost and quality after the project.
  31. Scrum is basis for a trusting relationship with the client.
  32. Over 80% of agile enterprises confirm that Scrum is very customer oriented.
  33. Successful projects with great results are signboards for the device provider. Scrum offers the prerequisites.

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.

  • No labels