Scrum

Scrum is an empirical process, where decisions are based on observation, experience and experimentation. Scrum has three pillars: transparency, inspection.

Scrum is a management framework that teams use to self-organize and work towards a common goal. It describes a set of meetings, tools, and roles for efficient project delivery. Much like a sports team practicing for a big match, Scrum practices allow teams to self-manage, learn from experience, and adapt to change. Software teams use Scrum to solve complex problems cost effectively and sustainably.

Scrum is a framework that is easy to learn but difficult to become an expert in. The co-creators of scrum, Jeff Sutherland and Ken Schwaber, have explained the underlying concepts in The Scrum Guide. The guide gives a detailed overview of scrum processes and how to implement them effectively.The essence of Scrum is a self-organizing team delivering customer value in a time-boxed period called a Sprint. Scrum defines artifacts, roles, and events associated with each Sprint.

Scrum Teams use tools called Scrum artifacts to solve problems and manage projects. Scrum artifacts provide critical planning and task information to team members and stakeholders. There are three primary artifacts:

Product Backlog

The Product Backlog is a dynamic list of features, requirements, enhancements, and fixes that must be completed for project success. It is essentially the team’s to-do list, which is constantly revisited and reprioritized to adapt to market changes. The product owner maintains and updates the list, removing irrelevant items or adding new requests from customers.

Sprint Backlog

The Sprint Backlog is the list of items to be completed by the development team in the current Sprint cycle. Before each Sprint, the team chooses which items it will work on from the Product Backlog. A Sprint Backlog is flexible and can evolve during a Sprint.