The checklist is provided in four sections, each representing a different step in a phased adoption plan.
Phase One - Envision
Build a clear picture of your future operating model, socialise your vision, and start to make tooling decisions.
- Identify your target DevOps team structure
- Identify any transitional DevOps team structure (if required)
- Acquire access to cloud services
- Ensure your procurement teams are ready for consumption-based billing
- Agree budgets and budget holders
- Decide your environment segregation strategy and set up the requisite accounts/subscriptions
- Create a shortlist of required information systems
- Create a shortlist of work management tools
- Create a shortlist of CI/CD tools and platforms
- Create a shortlist of knowledge sharing tools
Phase Two - Build
Start making changes! Ideally, begin with a few people and make them responsible for completing setup tasks, owning relevant ceremony diary meetings, and configuring their own tooling.
- Recruit or second people into your target teams
- Select a work management tool for your DevOps Team
- Select and configure a Knowlegebase for knowledge sharing between your Engineering Team and Service Desk
- Set up your CI/CD tooling
- Deploy Cloudmarque’s Core Building Block
- Connect your cloud monitoring capability/alerts to your Service Desk
- Populate a backlog
- Using an iterative planning methodology?
- Decide on an iteration length (typically 1, 2, or 3 weeks)
Phase Three - Launch
Initiate an iterative delivery cycle and work through all the processes, validating and finalising any setup activities.
- Ensure both your Service Desk and DevOps Team have access to the Knowlegebase
- Complete your first iteration including all ceremonies
- Use CI/CD to automate cloud deployments
Phase Four - Nurture
Like all Agile teams, your new DevOps capability should be self-organising and self-improving. However, there is much that leadership can do to encourage improvement and ensure the team does not stagnate.
- Reiterate the ownership that a team has to change and improve their working practises, ensuring they realise that they are empowered to change
- Communicate wider business plans to ensure team members are correctly prioritising and investing in automation where applicable
- Celebrate wins!
- Ensure that the team is pacing themselves: iterative delivery is a continuous practise and members may experience “burnout” if subjected to continual high-pressure deadlines. View progress as a marathon, rather than a sprint.
- Identify new tools, delivery platforms, and system features which may accelerate delivery
- Ensure that learning is documented and that retrospective feedback is acted upon
Edit this page on GitHub
The content on this page is published under Open Source licenses via GitHub. To submit issues or provide feedback please visit the repository.Visit