- Maximising value
- Product backlog management
- Definition of done
- 4-scrum events (non-negotiable)
- Roles & Responsibilities (non-negotiable)
- 4 values of scrum
- Value individuals & interactions over process and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiations
- Responding to change over following a plan
- 12 clarifying principles
- Simplicity maximises the amount of work NOT done
- Generate value through adaptive solutions to complex problems
- High performing cross functional teams
- Everyone knows a bit but we do have specialisations
- 3 pillars of empiricism : Transparency | Inspection | Adaptation
- Scrum values: Courage | Focus | respect | Commitment | Openness
- No scrum team member is in charge
- A squad: 10 or fewer
- Scrumbut: We say we are agile but our actions do not support that
- The scrum team should have all of the skills and competencies needed to deliver the product increment
- Product vision>Product roadmap>release planning>iteration planning>Daily planning
- User story: As a [Role], I want [functionality] so that [business benefit]
- User stories are INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable
- Sprint backlog is owned by the developers: self organise
- At the end of sprint, demo and potentially release increment
- Acceptance criteria have to be set to check against definition of done (only show completed work)
- Retro at the end of each sprint for the team only
- Product owner maximises the value
- Evidence based management (EBM) -> 4 Key Value Areas
- Current value (CV)
- Time to Market (T2M)
- Ability to innovate (A2I)
- Unrealised Value (UV)
- Sprint planning ~2 hrs per week of sprint
- Level of effort
- Complexity
- Uncertainty
- Sprint goal : Why
- Sprint backlog can evolve: What
- Action plan: How
- Self service model
- Fail wall -> Show the failures!
- Predictability kills innovation
- Visual waste, what is blocking
- Definition of awesome
- Nobody should be adding work to the sprint backlog except the devs.
- You need product backlog refinement
- Refinement is important so that value is understood and achievable
- Discuss the “how” during sprint planning : Sprint goal | Product backlog | action plan to deliver
5 challenges creating done increments
- Lack of team ownership: A lot of WIP is a warning sign, backlog carried over
- Lack of collaboration
- No clear sprint goal
- Sprint goal objective is should have a set of measures to provide the team focus and flexibility
- Is the sprint goal clear? Is it too long?
- Sprint goal is not just completing the product backlog
- Too much change during the sprint
- Impediments are not being removed