Scrum

A Better Way Of Building Products 

Scrum is a management and control process that cuts through complexity to focus on building products that meet business needs.

Management and teams are able to get their hands around the requirements and technologies, never let go, and deliver working products, incrementally and empirically.

Scrum itself is a simple framework for effective team collaboration on complex products.

Scrum Glossary

The Scrum Glossary is meant to represent an overview of Scrum-related terms.

 Some of the mentioned terms are not mandatory in Scrum, but have been added because they are commonly used in Scrum.

The Scrum Framework

Scrum is simple.

It is the opposite of a big collection of interwoven mandatory components.

 Scrum is not a methodology. Scrum implements the scientific method of empiricism.

Scrum replaces a programmed algorithmic approach with a heuristic one, with respect for people and self-organization to deal with unpredictability and solving complex problems.

The below graphic represents Scrum in Action as described by Ken Schwaber and Jeff Sutherland in their book Software in 30 Days taking us from planning through software delivery.  

The Scrum Values

 Although always considered to be a part of Scrum and often written about, in July 2016, the Scrum Values were added to The Scrum Guide.  

These values include Courage, Focus, Commitment, Respect, and Openness.

The Roles of the Scrum Team

The Scrum Team consists of a Product Owener, the Development Team, and a Scrum Master.

Scrum Teams are self-organizing and cross-functional.

Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team.

Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team.

The team model in Scrum is designed to optimize flexibility, creativity, and productivity.

The Scrum Events

Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.

All events are time-boxed.

Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened.

The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process.

The Scrum Events are:

• Sprit
• Sprint planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective

Scrum Artifacts

Scrum’s artifacts represent work or value to provide transparency and opportunities for inspection and adaptation.

Artifacts defined by Scrum are specifically designed to maximize transparency of key information so that everybody has the same understanding of the artifact.

The Scrum Artifacts are:

• Product Backlog
• Sprint Backlog
• Increment