* Originally proposed by Jeff Sutherland in 90s, then improved by Schwaber and Beedle

* In 1993, J. Sutherland borrowed term ‘scrum’ from Takeuchi and Nonaka, “The New Product Development Game”, Havard Business Review, 1986

* Takeuchi and Nonaka compare high-performing, cross-functional teams to the scrum formation used by Rugby teams.

* In rugby scrum is the power struggle between two teams to advance on the field

* It requires complete team work, hard work, and strength. That meaning translates to software development

Scrum is the most popular agile framework.

Scrum fulfils the vision of the Agile Manifesto by helping individuals and businesses organize their work to

• maximize collaboration,
• minimize errors,
• deliver frequently, and
• create multiple opportunities to inspect and adapt.

Sprint is a short (one to four weeks long) timeframe during which the team works on some chunks of the product.

The Scrum Master helps the Scrum Team perform at their highest level. They also protect the team from both internal and external distractions. Scrum Masters hold the Scrum Team accountable to their working agreements, Scrum values, and to the Scrum framework itself.

The Product Owner defines the what–as in what the product will look like and what features it should contain. Product Owner helps build and clarify the product backlog and ensures that everyone knows the priorities.

The Development Team decides how to accomplish the work set forth by the Product Owner. Development Teams are structured and empowered to organize and manage their own work.

Sprint is a short (one to four weeks long) timeframe during which the team works on some chunks of the product.

• Each sprint begins with a plan followed by building and then testing the code, and ends with a review of the work completed and an additional review of the way in which the team worked together (retrospectives).

• During each sprint, the team completes one or more increments of the project. Each completed increment must be fully tested and fully approved by the end of the sprint (potentially deliverable).

Commitment: Scrum teams work together as a unit, members trust each other to follow through on what they say they are going to do.

Courage: Scrum teams must feel safe enough to say no, to ask for help, and to try new things.

Focus: It means that whatever Scrum teams start they finish.

Openness: Scrum teams consistently seek out new ideas and opportunities to learn.

Respect: Scrum team members respect each other’s ideas, give each other permission to have a bad day once in a while, and recognize each other’s accomplishments. They show respect to one another, to the product owner, to stakeholders, and to the ScrumMaster.

The Product Backlog is an ordered list of everything that is known to be needed in a product.

The Sprint Backlog is a list of everything that the team commits to achieve in a given Sprint. Once created, no one can add to the Sprint Backlog except the Development Team. If an item needs to be dropped from the Sprint Backlog, they must negotiate it with the Product Owner.

At the end of every Sprint, the team must complete a potentially releasable product increment meaning that it is done as agreed upon.

• Scrum Team Members stand up in circle facing everyone. Also, someone else just “observing”. Meeting is less than 15 minutes long.

• Scrum Master Scrum Master starts the meeting. Makes sure everyone talks in order from left to right.

• Each member answers to 3 questions regarding meeting the sprint goal:

   1. What did I worked on since last meeting? 

   2. What I am working on now? 

   3. Do I see any impediments?