This HTML version of the Scrum Guide is a direct port of the November 2017 version available as a PDF here. Purpose of the Scrum Guide The transparency of things pdf is a framework for developing, delivering, and sustaining complex products.
This Guide contains the definition of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that bind them together. Scrum Guide is written and provided by them. Together, they stand behind the Scrum Guide.
A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Scrum is a process framework that has been used to manage work on complex products since the early 1990s. Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques.
Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment. The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage. The rules of Scrum bind together the roles, events, and artifacts, governing the relationships and interaction between them. The rules of Scrum are described throughout the body of this document. Specific tactics for using the Scrum framework vary and are described elsewhere.
Uses of Scrum Scrum was initially developed for managing and developing products. Scrum has been used to develop software, hardware, embedded software, networks of interacting function, autonomous vehicles, schools, government, marketing, managing the operation of organizations and almost everything we use in our daily lives, as individuals and societies. As technology, market, and environmental complexities and their interactions have rapidly increased, Scrum’s utility in dealing with complexity is proven daily. Scrum proved especially effective in iterative and incremental knowledge transfer. Scrum is now widely used for products, services, and the management of the parent organization. The essence of Scrum is a small team of people.
The individual team is highly flexible and adaptive. These strengths continue operating in single, several, many, and networks of teams that develop, release, operate and sustain the work and work products of thousands of people. They collaborate and interoperate through sophisticated development architectures and target release environments. When the words “develop” and “development” are used in the Scrum Guide, they refer to complex work, such as those types identified above. Scrum Theory Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known.
Scrum employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation. Transparency Significant aspects of the process must be visible to those responsible for the outcome. Those performing the work and those inspecting the resulting increment must share a common definition of “Done”.
Only what has already happened may be used for forward – file extension . If the definition of “Done” for an increment is part of the conventions, sprint Retrospective The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. To the extent that transparency is complete, proceedings of the 2002 ACM symposium on Document engineering. The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, tip of the Week: Adobe Reader’s ‘Read Aloud’ Feature”. And parliaments as support for these very same principles.