Results & Deep Dive of Past Experiences¶
Two team's journey through the Dojo¶
Team 1¶
An in person engineering team for a large bank that wanted to create new lending capabilities for customers. The business wanted to go faster to market and react quickly to customer feedback. Tech leads and engineers wanted to build using modern, scalable, and resilient architecture and platforms.
Team 2¶
A remote product team wanted to containerize their application and adopt cloud native practices and methodologies. The team needed some help to decouple their correct app architecture and make them deploy independently, faster and safer. Containers and container orchestration tools are new for the team.
Dojo Experience¶
Team 1 Dojo Experience¶
During Team 1's time in the Dojo, Liatrio assisted in mapping the product backlog and breaking down the work into delivery increments (in this case hypersprints). Liatrio was able to expand on their current engineering principles while also bringing in/supporting Behavior Driven Development and Test Driven Development. The Dojo was so successful that the company brought 50+ more teams through the Dojo.
Through their Dojo they accelerated product launch by 3 months, customer facing product features were released every 2 weeks, and team metrics were improved by 250%.
Team 2 Dojo Experience¶
Team 2 wanted to use their time in the Dojo doing less on product and new feature development and more on re-architecting their service apps to cloud native solutions and onboarding to Azure Cloud Platform. The team's success led to two more engagements being requested, one for infrastructure automation and another for application monitoring/observability.
This team's Dojo led to a 100% cloud hosted infrastructure, and also set the benchmark for the rest of the enterprise. Service and resilience increased by 20%, and team metrics increased by 160%.
Timelines of Each Teams' Dojo¶
Team 1 Timeline¶
Team 2 Timeline¶
Another Journey Through a 6-week Product Dojo¶
A website and customer data team for a retail company eagerly entered the Dojo looking to improve their software delivery capabilities. The team's main focus was to establish modern ways of working and utilize the new engineering delivery platform. Trusting the Dojo coaches, the team embarked on their continuous improvement journey.
Discovery¶
The charter was created in collaboration with the team to help uncover their current delivery process and define objectives & key results to accomplish during the Dojo.
Dojo Experience¶
As the 6-week immersive learning experience began, the team was on their way to remove silos and become more cross-functional.
- Work was done in their existing app components/repo
- Each day had specific goals and topics covered
- We leveraged huddle rooms for breakdown and working in groups
- MS Teams chat was the primary chat system for team communication
- Active participation by all members of the team
- Facilitated 50+ pair and mob sessions
End of the Dojo Accomplishments¶
Platform¶
- Everyone’s local machine setup with Docker and Minikube
- Documented local setup and added to README
- Built strategy to iterate on CircleCI pipeline locally
- Recorded multiple pairing sessions on setting up and running Docker locally
- Added branch CircleCI workflow
- Introduced the concept of Multi-stage Docker builds
Dev Practices¶
- Conducted Svelte learning session
- Covered NPM lifecycle and how to manage project dependencies
- Setup Zalenium locally and in the pipeline
- Stabilized dev workflow pipeline
- Created solution for Svelte environment variables
- Defined branch patterns for feature development
Ways of Working¶
- Documented new member onboarding process
- Paired with Ethan on Scrum recommendations
- Defined ways of working
- Solved dependency mapping for Jira tickets
- Defined team norms around protected code changes and pull requests
- Add branch permissions in Bitbucket to align with team norms
- Showcased progress to other teams and leadership
Skills Matrix¶
Skills matrix shows the impact Dojos make to individuals skill sets.
