Moving from Project to Product
summary
Organizations fail by front‑loading decisions, funding year‑ahead projects and rewarding handoffs; only 8% of companies expect to survive that way. Shift to product/platform/service teams that use CI/CD pipelines as a service, infrastructure as code and automated tests, fund teams not projects, and keep batches small. Cross‑functional squads push changes in two to four weeks into customers, measure outcomes not output, and avoid the release frenzy; the result is faster validated learning and fewer wasted months and dollars.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:55Its broken
- 1:24This isnt the business
- 1:43The fault I dont believe lies in it
- 2:30Example
- 5:28The reality
- 5:47Where did it all go wrong
- 6:44Taylorism
- 8:52Projects
- 12:00Customers Users
- 12:18Dont worry about whether it works
- 12:52Where do we go
- 13:02Criticisms
- 14:46Product vs Service
- 20:07Five Guiding Principles
- 20:32Moving from large batches to small
- 21:37Key starting point
- 21:52Scope
- 22:16Funding
- 22:42Speed to market
- 23:23The 5 guarding principles
- 23:37How we measure things
- 24:07Summary
- 24:17Questions
related talks
38mBuilding a high quality product
24mBringing Product Thinking into DevOps
33mCulture of Continue Delivery
30mTransforming to a Culture of Continuous Improvement
28mBringing DevOps to Product
05mHelp! My DevOps team is stuck!
28mProject to Product: Practical Realities at a Large Scale Enterprise
25mBringing Product thinking to DevOps