Why Use Scrum?

Why Use Scrum
Why Use Scrum?

Why Use Scrum?

Why use scrum in software development? Here are some of the key benefits of Scrum in any project are:

  • Adaptability: Empirical process control and iterative delivery make projects adaptable and open to incorporating change.
  • Transparency: All information radiators like a Scrumboard and Sprint Burndown Chart are shared, leading to an open work environment.
  • Continuous Feedback: Continuous feedback is provided through the Conduct Daily Standup and Demonstrate and Validate Sprint processes.
  • Continuous Improvement: The deliverables are improved progressively Sprint by Sprint, through the Groom Prioritized Product Backlog process.
  • Continuous Delivery of Value: Iterative processes enable the continuous delivery of value through the Ship Deliverables process as frequently as the customer requires.
  • Sustainable Pace: Scrum processes are designed such that the people involved can work at a sustainable pace that they can, in theory, continue indefinitely.
  • Early Delivery of High Value: The Create Prioritized Product Backlog process ensures that the highest value requirements of the customer are satisfied first.
  • Efficient Development Process: Time-boxing and minimizing non-essential work leads to higher efficiency levels.
  • Motivation: The Conduct Daily Standup and Retrospect Sprint processes lead to greater levels of motivation among employees.
  • Faster Problem Resolution: Collaboration and colocation of cross-functional teams lead to faster problem solving.
  • Effective Deliverables: The Create Prioritized Product Backlog process and regular reviews after creating deliverables ensures effective deliverables to the customer.
  • Customer Centric: Emphasis on business value and having a collaborative approach to stakeholders ensures a customer-oriented framework.
  • High Trust Environment: Conduct Daily Standup and Retrospect Sprint processes promote transparency and collaboration, leading to a high trust work environment ensuring low friction among employees.
  • Collective Ownership: The Approve, Estimate, and Commit User Stories process allows team members to take ownership of the project and their work leading to better quality.
  • High Velocity: A collaborative framework enables highly skilled cross-functional teams to achieve their full potential and high velocity.
  • Innovative Environment: The Retrospect Sprint and Retrospect Project processes create an environment of introspection, learning, and adaptability leading to an innovative and creative work environment.

Source: A Guide to the SCRUM BODY OF KNOWLEDGE (SBOK™ Guide), 2013 Edition [1]

For more Scrum articles, please visit our internal page, found here

Why Use Scrum?

Agile Manifesto

Agile Manifesto for Software Development

What is the Agile Manifesto?

The Agile Manifesto is a brief document built on 4 values and 12 principles for agile software development. The Agile Manifesto was published in February 2001 and is the work of 17 software development practitioners who observed the increasing need for an alternative to documentation-driven and heavyweight software development processes.

What Does The Agile Manifesto Say?

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Twelve Principles of Agile Software

We follow these principles:

  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  7. Working software is the primary measure of progress.
  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  9. Continuous attention to technical excellence and good design enhances agility.
  10. Simplicity–the art of maximizing the amount of work not done–is essential.
  11. The best architectures, requirements, and designs emerge from self-organizing teams.
  12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Who Created the Agile Manifesto?

Here are the individuals who signed the original Agile Manifesto back in 2001:

For more information, please visit the Agile Manifesto page or our article page


Last updated by at .

Secured By miniOrange