So far so good... so what? The legal side of Agile
summary
Insist on a written Exit Plan and a short trial period (Sprint zero) so teams can walk away cleanly; give the product owner a legal power of attorney to make decisions without top‑management signoff; require a named scrum master and proof of a truly cross‑functional development team in the contract; spell out who attends and how long each Sprint event lasts instead of a blanket “Scrum Guide” reference; include a concrete Change Control procedure and a cost‑target contract with bonus payout to share risk and reward.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:11Trust in Agile projects
- 3:32Trial periods and exit plans
- 6:53Product Owner authorization
- 8:19Scrum Master contracting
- 9:23Cross-functional teams
- 11:07Sprint events in contracts
- 13:15Product vision and backlog
- 15:04Agile contract scope myths
- 16:30Change Control procedure
- 17:13Cost Target and bonus models
- 20:40Summary
- 22:29Q&A