Fund products - start an evolution
summary
Annual budgeting and project-based funding block agility and cause team churn; the proposal is to fund teams not projects by using the annual pot to create long-lived product teams or product groups, add quarterly breakpoints with rolling wave planning, and measure progress by outcome KPIs not scope adherence. Telecom and retail examples consolidate many projects into one funding block (11 teams in one retailer case), simplify finance reporting, reduce bureaucracy and increase team stability and measurable ROI.
AI-written summary · about
chapters (11)
- 0:00Funding and agility challenges
- 10:39Project funding failures
- 18:04Agile funding evolution
- 23:45New funding aspirations
- 24:48Funding long-lived teams
- 29:41Rolling wave planning
- 33:15Outcome-based reporting
- 36:23Identifying products
- 39:10Nudges and benefits
- 44:06Call to action
- 44:47Q&A: Budget autonomy
related talks
33mPrioritizing Effectively and Forming a Product Vision
28mUser Stories and other agile failures
47mThe Only 2 Things needed to Scale Agile
01h 05mAgile transformation & the elephant in the room
48mEvolution From #Noprojects to Continuous Digital
33mAligning Goals & Processes between Engineering & Product
01h 04mMoving to a Agile Product Operating Model
31mTransitioning from Project to Product: An Experience Report