You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Our product engineering dojo is an immersive learning space where teams build a product mindset and best-in-class engineering skills. We do this by putting learning ahead of process by working on their actual product backlog, pairing teams with dedicated product and engineering coaches, and iterating rapidly twice a week.
In 2016 I was hired as one of the head coaches of a massive DevOps transformation. The goal was to, in a 7000+ person IT organization, get teams fluent in topics such as CI/CD, automated testing, and product management. Our dojo team created a successful, impactful program at scale.
I’ll share experiences and learnings from my 6-month journey. Starting with the concept of a DevOps Dojo, we’ll then explore it from four, detailed perspectives: product, place, process, and people.
Product: Elaborating on the classic “coder’s dojo” - focused on building technical skills - to a “DevOps Dojo” where we perfect technical skills while delivering on product learning goals.
Place: A virtual tour through the engineering spaces that promote collaborative, rapid feedback, and high energy work.
Process: How we scaled to 12 concurrent dojo teams of 4-16 people with a custom pull system (kanban) featuring unusual-but-realistic WIP limits.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters