The Pivotal Engineering Dojo
summary
Six- to eight-week residency by invitation embeds engineers on Cloud Foundry teams where code is pair programmed + test‑first (TDD), contributions land immediately, and decisions happen in minutes. Work focuses on runtime internals or BOSH provisioning, with remote pairing via Screenhero or terminal tools and commits credited using git‑duet. Pairing yields high quality with roughly two–three story points a day for many pairs, but documentation shrinks, slack is limited, and scaling the dojo model remains a challenge.
AI-written summary · about
chapters (8)
- 0:00Introduction and welcome
- 2:27Agile and extreme programming
- 8:09Dojo program overview
- 15:30Lessons and culture at Pivotal
- 22:10Recommendations and closing
- 23:12Q&A on pairing practices
- 26:50Remote pairing challenges
- 29:57Productivity of pair programming
related talks
31mThe Cloud Foundry Dojo Experience — How to Become a Contributor
30mFrom 0 to core contributor
18mWhy we pair?
01h 54mPair Programming & Test Driven Development done right
27mInstilling DevOps Ways of Working in Large Enterprise...
01h 01mPairing, Sharing, Caring - One team's journey to Pair Programming
19mKeynote: Confessions of a Cloud Foundry PaaS Product Owner: How to Create a Successful Devops Team
32mMaximizing the Fun Pair Programming Benefits