Project Release Planning: Building an Iterative Framework.
summary
Framework sets quarterly releases of three months (four per year) for a ~50 person AAA project, starts with a two-day planning workshop, then a kickoff, four two-week sprints, a two-week hardening closing period and playtest. Delivery uses Jira and Confluence with health checks after each sprint, sprint reports, a live deliverables table and a simple Kanban dependency board; later iterations add Jira automation to replace painful PowerPoint slides. Iterations reduce meetings, improve visibility, and empirically raise delivery stability.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 4:11Talk purpose and structure
- 7:19Iterative release framework
- 10:28First release workshop
- 14:18Project tools and cadence
- 18:51Release schedule and health checks
- 23:00Closing period and delivery
- 28:40Iterating framework in release two
- 33:58Refining framework in release three
- 39:38Key takeaways and advice
- 40:42Q&A
related talks
40mAgile Software Development: Practice and Analytics
52mGame Production: Helping your team succeed
23mAchieving Weekly Releases: A Technical Deep Dive into Our Development Process
49mBaking Boards: Tweak the Recipe for Agile Development
18mManaging Change
21mScaled Agile DevOps
24mThe 7 Habits of Highly Effective Release Managers
27mMechanics of releasing a large project: Leadership learnings from Kubernetes releases