[Music] thank you [Music] I'm Stuart I'm a visual Storyteller trainer and member of the scrum Alliance community and I want to talk you through the essentials of scrum scrum is a lightweight framework that helps people teams and organizations generate value through adaptive solutions for complex problems these people create products as a vehicle to deliver value these products have a clear boundary known stakeholders and well-defined users or customers a product could be a service a physical product or something more abstract the foundation of scrum is lean thinking and empiricism lean thinking focuses on reducing waste and
empiricism asserts that knowledge comes from experience and making decisions based on what is observed scrum defines three pillars that support empiricism transparency inspection and adaptation transparency means making work and process visible to all transparency then enables inspection inspection enables us to detect potentially undesirable variances or problems but inspection with our adaptation is considered pointless grum is designed to provoke adaptation of the product created and processes used to deliver value a scrum team is expected to adapt the moment it learns anything new through inspection now the fundamental unit of scrum is a small self-managing cross-functional team
of people called the scrum team who are responsible for all product related activities the scrum team consists of one scrum Master one product owner and Developers developers are the people in the scrum team that are committed to creating any aspect of a usable increment each Sprint who hold each other accountable as professionals the product owner is accountable for maximizing the value of the product resulting from the work of the scrum team and product backlog management the scrum Master is a true leader who is accountable for the scrum team's Effectiveness by establishing scrum as defined in
the scrum guide they do this by helping everyone understand scrum theory and practice the scrum Team Works within a Sprint where ideas turn to Value this is a containing event for four formal inspect and adapt events Sprint planning the daily scrum the Sprint review and the Sprint retrospective the Sprint is a fixed length event of one month or less to create consistency the scrum team makes use of three key artifacts that represent work or value the product backlog the Sprint backlog and the increment the product backlog is an emergent ordered list of what is needed
to improve the product it is the single source of work undertaken by the scrum team the Sprint backlog is a highly visible real-time picture of the work the developers plan to accomplish during the Sprint which is created and adapted by the developers throughout the Sprint the increment is an additive to all prior increments and fully verified ensuring all increments work together in order to drive value it must be usable the artifacts are designed to maximize transparency of key information to achieve this each artifact contains a commitment to enhance transparency for the product backlog it is
the product goal developed by the product owner this is a future state of the product which can serve as a target for the scrum team to plan against for the Sprint backlog it is the Sprint goal this is the single objective for the Sprint which provides coherence and focus and for the increment it is the definition of done this is a formal description of the state of the increment when it meets the quality measures required for the product the Sprint commences with Sprint planning where the product owner ensures that attendees are prepared to discuss the
most important items to work on within that Sprint from the product backlog and how they map to the product goal spring planning addresses the following topics topic one why is this Sprint valuable the product owner proposes how the product could increase its value and utility in the Sprint topic two what can be done this spring the product owner and developers then select product backlog items that are ready to work on from the product backlog to include in the current Sprint topic three how will the chosen work get done for each selected product backlog item the
developers plan the work necessary to create an increment that meets the definition of done the Sprint goal the product backlog items selected for the Sprint plus the plan for delivering the work are added to the Sprint backlog Sprint planning is time boxed to a maximum of eight hours for a one month Sprint the purpose of the daily scrum is to inspect progress towards the Sprint goal and adapt the Sprint backlog is necessary adjusting the upcoming planned work the daily scrum is a 15-minute event for the developers of the scrum team it is held every day
at the same place and same time to reduce complexity throughout the spring the intention is to create a valuable increment or multiple increments which act as a concrete stepping stone toward the product goal the definition of done provides a formal description of the state of the increment when it meets the quality measures required for the product the moment a product backlog item meets the definition of done an increment is born the purpose of a Sprint review is to inspect the outcome of the Sprint and determine future adaptations the scrum team presents the results of the
work to key stakeholders and progress toward the product goal is discussed during the event the scrum team and stakeholders review what was accomplished in the Sprint and what has changed in their environment and collaborate on what to do next the Sprint review is the second to last event of the Sprint and is time boxed to a maximum of four hours for a one month Sprint the purpose of a Sprint retrospective is to plan ways to increase quality and effectiveness for scrunting inspects how the last Sprint went with regards to individuals interactions processes tools and their
definition of done the scrum team identifies the most helpful changes to improve its effectiveness the most impactful improvements are addressed as soon as possible they may even be added to the Sprint backlog for the next Sprint the Sprint retrospective concludes the Sprint it is time boxed to a maximum of three hours for a one month Sprint the ongoing activity of product backlog refinement takes place throughout the Sprint this is the act of breaking down and further defining product backlog items into smaller more precise items the developers who will be doing the work are responsible for
sizing and the product owner May influence the developers by helping them understand and select trade-offs successful use of scrum depends on people becoming more proficient in living five values commitment Focus openness respect and courage when these values are embodied by the scrum team and the people they work with the empirical scrum pillars of transparency inspection and adaptation come to life building Trust it's simple and purposefully incomplete you can try as is and determine if its philosophy Theory and structure help you to achieve the goals you need to create value here at the scrum Alliance our
community can help connect you to the people learning and resources you need to succeed [Music]
