Scrum

Guide Scrum

1 - Scrum Framework - Framework Scrum consist: Team Scrum + roles + events + artifacts + rules - The rules of Scrum bind together the events, roles, and artifacts, governing the relationships and interection between them.

2 - Scrum Theory - Empiricism asserts that knowledge comes from experience and making decisions based on what is known - Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation. a) Transparency requires those aspects be defined by a common standard so observers share a common understanding of what is being seen. > A common language referring to the process must be shared by all participants; and, > A common definition of “Done” must be shared by those performing the work and those accepting the work product. b) Scrum users must frequently inspect Scrum artifacts and progress toward a goal to detect undesirable variances. c) If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted. > Scrum prescribes four formal opportunities for inspection and adaptation: - Sprint Planning Meeting - Daily Scrum - Sprint Review - Sprint Retrospective

3 - Scrum

- Scrum is a framework structured to support complex product development. - Scrum 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. 4 - Team Scrum (TS) - The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. - 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