Software Delivery - 10% time the pros and cons?
summary
Company implements Project Lounge: engineers stop sprint work one day a fortnight to experiment, learn or fix tech debt. Outcome includes a holiday countdown mobile app that reaches 700,000 downloads, regular bug fixes, accessibility work and cross‑team pairing, but measuring ROI and securing business buy‑in proves hard. Practical fixes: lower barriers with a simple spreadsheet, optional show‑and‑tells, coaching non‑technical staff, and occasional short‑term trading focus when priorities demand it.
AI-written summary · about
chapters (33)
- 0:00THE PROS AND CONS?
- 0:26THE PROS AND CONS OF 10% TIME
- 1:04what is 10% time?
- 1:15research and development.
- 3:42project lounge.
- 5:15hack day.
- 7:54individual development
- 8:43innovation
- 9:39efficiency
- 10:51self organising.
- 11:28engagement.
- 12:47attraction.
- 13:59retainment
- 14:36bug fixing
- 15:08tech debt.
- 15:48pros.
- 18:23no end product
- 18:47measuring the value.
- 19:42others not understanding.
- 20:25cancellation?!
- 21:13taking the time for granted.
- 22:13testers can't do it.
- 22:58guilt.
- 24:21getting buy in.
- 26:0410% isn't enough.
- 29:02reduce barrier to entry.
- 29:42support the 'non- technical team
- 30:22help people feel wanted.
- 31:14encourage collaboration.
- 32:42understand those who don't want to do it.
- 34:24make the value obvious.
- 35:38balance the business and individual need.
- 38:24summary.
related talks
34mBuilding a Culture For Developer Productivity
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
11mGive 10%, get 110%
32mDeveloper productivity 2.0
24mAgile working in a slow-moving world
40mHow to be a Happy Developer. Now!
17mMake Work Not Suck Improving the Developer Experience
58mDeveloper Joy – How Great Teams Get S%*t Done