Scrum is for complex work - release often - support product Scrum is a process - its not a 'methodology' Empiric (Scrum Pillars) Transparency Inspection Adaptation Values -> GOAL Roles Artifacts Events Backlog Management (from Mistral) Sprint Planning 8h/30d Sprint 30 d or less Daily Scrum 15 mins Sprint Review 4h/30d Sprint Retrospective 3h/30d Scrum in complex environment Sourced from video What is scrum Questions? What is the guideline timebox for Sprint Planning? - 8 hours for 30 day sprint. What amount work should developers complete in a Sprint? - increment that fulfills the Definition of Done. Which party of the Scrum Team defines the DoD? Unless its an organizational standard, the Scrum Team creates suitable Definition of Done that relates to the product. Who manages the work during a Sprint? - The Developers. What should the Scrum Team do in the first Sprint? - a valuable and useful increment. Who is responsible for adding or dropping Product Backlog items from Sprint Backlog? - everyone on the Scrum Team, but basically its dialogue between PO and devs. Is it true that Scrum Team members should never be replaced? Not true, members can change, whilst also observing the short-term reduction in productivity. When does next sprint begin? - immediately after the end of the previous Sprint. During Sprint Retro, should the team select process items to add into Backlogs? - false, this was recommended before 2020 update to Scrum Guide. When would Scrum Master cancel the sprint? - never, Only the Product Owner has the authority to cancel the Sprint, when Sprint Goal becomes obsolete.