Are we there yet? Or what a release plan is for
summary
Company Totaljobs runs seven Scrum teams including one in Poland and uses a release plan like a sat nav analogy that outputs an estimated number of sprints, a projected drop date and total distance but insists on being add margin for error because breaks, legacy code fixes, holiday weeks and traffic hotspots regularly extend delivery. Keep the plan visible, update it each sprint, log risks up front, discuss detours with the product owner, and never speed up by cutting quality since extra hours rarely recover lost technical debt.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:33painting and decorating!
- 4:02Typical of all Product Owners they ...
- 4:55When we go on a journey we plan
- 5:31So how does a sat nav plan?
- 7:14Typically with a Sat Nav we apply caveats or rules of thumb...
