


Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
A comprehensive overview of the scrum methodology, a popular agile framework for software development. It delves into the core principles, values, and practices of scrum, including its key components like sprints, sprint planning, daily scrums, sprint reviews, and sprint retrospectives. The document also explores the roles of the scrum master, product owner, and development team, highlighting their responsibilities and interactions within the scrum framework. It further examines the importance of transparency, inspection, and adaptation in scrum, emphasizing the iterative and incremental nature of the process. This document serves as a valuable resource for individuals seeking to understand and implement scrum in their software development projects.
Typology: Exams
1 / 4
This page cannot be seen from the preview
Don't miss anything!



Difference between SCRUM and Agile - Agile is using sprintgs. SCRUM is agile for Software dev Scrum employs an xx, yy approach to optimize zz and zz. - Iterative Incremental predictablity control risk Three pillars uphold every implementation of empirical process control - transparency, inspection, and adaptation Pillar of empirical process control : Transparency. What and how? - Important elements of process must be visible to relevant people. Must also be defined with a common standard Pillar of empirical process control: Inspection. What and how - Inspect artifacts to identify variances by skilled inspectors at point of work without clogging work itself Pillar of empirical process control: Adaptation. What and how - If inspector finds variance is beyond accepted limits, the process or artifact must be adjusted 4 formal meetings of SCRUM? - Sprint planning Daily SCRUM Sprint review Sprint retrospective SCRUM Values? - CCFOR - Commitment Courage Focus Openness Respect Scrum teams are (2) - Self Organizing - No leader. They pick how to do Cross Functional - Not depend on other out of the team Main goal of Product Owner? How? - Maximizing the value of the project developed by the development team. How? By managing the product backlog! What does Product Backlog management includes?(5) - 1. Clearly expressing PBIs
Function of Scrum Master? Leader? Major task? - Promoting and supporting SCRUM. Servant Leader. Ensure meetings between outsiders and scrum team are useful. SM service to PO - DT understands PO and PBI Product planning in an empirical environment Facilitating SCRUM events SM service to DT - Coaching in SO and CF (Self Organization and Cross Functionality) Remove impediment of DT Facilitating SCRUM events (Think of PM to DT duties but with SCRUM flavour) SM services to the Organization - Helping Organization with SCRUM adoption Characteristics of SCRUM events? - Time boxed. Cannot be shortened/lengthened after they start Ends when matter is closed in the given time. What is the underlying purposes of SCRUM events? - Every event is an Opportunity for inspection and adaptation. Events are designed to allow critical transparency and inspection What is a Sprint? - One month or less run where "Done" useable and potentially releasable product is released. Components of a sprint - Sprint Planning Daily Scrum Development Work Sprint Review Sprint Retrospective What should be ensured during a Sprint?CaC - No changes are done to affect the Sprint Goal Quality goals don't decrease Scope may be discussed with PO as new things are found Why are sprints time boxed to one month? What do sprints enable? - If longer, definition of whats being built may change. More complexities and risk. Cost is limited to one calendar month Sprints enable predictability through inspection and adaptation of progress towards sprint goal Can a sprint be Cancelled? If so, why? If not, why not? - Yes. PO can cancel. If the Sprint goal is obsolete. Can cancel with influence from Stakeholders, SM or DT.
Discusses issues faced and resolutions Sprint Retrospective: 1. Purpose 2. TIming 3. Time - 1. ST (Scrum Team) to review itself
Sprint Review: Scrum Master and specialty - Participates as a peer from the accountability of the Scrum process. 3 goals of a Sprint Review - 1. Review the people, relationships, process, tools