Moving From Plans to Goals
summary
Argues that a Sprint Backlog is a plan but a clear, measurable Sprint Goal changes behavior: introduce a Roman Pichler template after planning, state the objective, method (prototype/spike), and a metric — e.g. goal: fly ≥4 m in the paper‑plane exercise or measure performance by X% for a welcome page. Adoption avoids forcing, uses daily checks tying work to the goal, and links sprint goals to release outcomes. Results: fewer WIP, more collaboration, higher morale, clearer sprint reviews, but initial resistance and partial failures require iteration.
AI-written summary · about
chapters (10)
- 0:00Introduction and goals
- 3:52Activity paper airplane demo
- 10:19From plans to goals shift
- 12:51Why sprint goals failed
- 15:22Roman Pichler template
- 21:57SMART goals examples
- 24:24Challenges adopting goals
- 26:51Daily scrum with purpose
- 29:01Linking to release goals
- 31:50Final activity and summary
related talks
36mContext-driven Agile Tester
14mGaining speed
05mContext-Driven Practices
51mThe Art of Test Planning – Expect the Unexpected
57mFocus. Deliver. Learn. Repeat
45mFrom plan-based to discovery-based Agile portfolio management
43mBacklogs – the good the bad and the ugly
34mFrom Waterfall To River – A Story Of Transitioning To Flow