Shape me Up before you go go! A journey transforming how we build products
summary
OBEO adopts Shape Up with a formal decision team, pitch templates and appetite-driven choices, running a 6+2 week cycle (six weeks discovery/delivery, two-week cooldown) and synchronized releases for dependent projects. Implementation uses a monorepo, GitHub Projects and code owners, CI/CD with GitHub Actions + AWS, automated tests (Cypress, gunit) and Kiwi TCMS for release testing. About ~100 ADRs document architectural decisions; large features are split into Scopes for smaller PRs and parallel integration, producing regular release candidates and predictable upstream evolution.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:57Chocolate bar game
- 7:14Stakeholders dilemma
- 10:27Transforming process with Shape Up
- 13:40Transformation challenges
- 16:30Shape Up methodology in practice
- 21:45Implementation and code review
- 25:38Monorepo and code ownership
- 27:02Deployment and testing strategies
- 28:50Release cycles and stabilization
- 31:00Handling urgent tasks
- 32:26Enablers and synchronized cycles
- 33:49Benefits for stakeholders
- 34:09Continuous improvement
- 34:53Q&A
related talks
18mAgile leadership and technical mastery, a harmonious alliance
40mPractices from trenches for embracing evolutionary architecture in wild
29mIntentional Architecture in Agile Organizations
48mDown the Ivory Tower towards Agile Architecture
01h 03mEvolutionary Software Architectures
47mMaking architecture decisions, the Agile Way
01h 00mAgile Architecture
58mBuilding Enterprise Software Today: A partnership in openness