Towards organisational agility at eDO, some lessons from the trenches
summary
Moves from centrally managed releases to cross-functional pods then to area groupings with a product director, development director, QA manager and agile coach create alignment and better execution. Strategic work maps strategy → themes → problem statements → concepts → hypotheses and links down to epics and stories in JIRA concept-to-epic links. Three-month value drivers form temporary cross-area teams. A visible wall board with team logos tracks weekly outcome metrics, reduces coach dependency and drives executive buy-in after 18 months of results.
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 3:18Problems with functional silos
- 7:13Moving to cross-functional teams
- 10:44Grouping teams into areas
- 13:18Three horizons of agility
- 19:46Improving visibility and alignment
- 24:45Building team capability
- 28:39Encouraging good decision-making
- 32:37Executive buy-in and results
- 35:11Refining upstream processes
related talks
43mFrom an Agile Team to an Agile Organization
22mEvolving DevOps Teams and Flexible Organizational Culture
01h 13mScrum for Executives, Leaders, and Your Boss
43mRising to the Agility Challenge
44mCan you be agile and compliant?
47mAgile experience in changing environments and the challenges faced
18mManaging Change
52mShifting into continuous delivery