A DevOps Dojo is a place where DevOps team members go for hands-on training. In Japan, a dojo is a safe environment where someone can practice new skills. In software development and operations management, DevOps Dojos provide learners with an immersive environment where team members can gain practical work experience without having to worry about introducing errors into the production environment.
A DevOps Dojo team is usually made up of the learning product team, product managers, Agile coaches
The benefits of creating and using a DevOps Dojo for training include:
- Identifying and closing skills gaps.
- Creating a culture of collaboration.
- Giving DevOps team members the time it takes to learn something new.
- Providing development and operations teams with a collaborative, risk-free learning environment.
- Creating turnkey trainers who can facilitate future DevOps Dojos.
How DevOps Dojos work
DevOps Dojos typically last for six weeks, with around two sprints a week. Dojo coaches will act as teachers until the team can begin to perform and meet expectations on their own. For example, coaches will help members with the DevOps tools they will be using. Implementation of a DevOps Dojo should start with small teams and a few coaches. Typically, developers in a DevOps Dojo will gather and run through multiple lightweight exercises to gain experience in a new skill. Each exercise is called a “kata.”
A common implementation of a DevOps Dojo is called a Dojo challenge. In this challenge, a team will work toward a common goal for six weeks. The main idea of the challenge is to help the team identify and improve areas they need practice with. Completing the goal is secondary, meaning the stress of reaching the goal is lessened while emphasizing the practice, making for a less stressful learning environment.
The Target Dojo
The retailer Target is credited with the creation of DevOps Dojos. Prior to the founding of Dojos, they were facing a few
Target is also credited with creating the dojo challenge, a specific implementation of a DevOps Dojo. At first, they utilized training from external sources, but later shifting to hosting