As organizations make the shift to DevOps, best practices are constantly being questioned, updated and qualified. In an homage to “The Joel Test: 12 Steps to Better Code“, Michael Elder adopted the list as it applies to DevOps. So without further ado:
For those that follow
- Do your developers and operators communicate the production realities and the application’s requirements?
- Do you version deployment configuration and scripts along with your source code?
- Do you have patterns for platforms and applications, designed jointly by development and operations?
- Can your developers launch and destroy production-like environments from those patterns?
- Are your patterns based on reusable deployment configuration scripts?
- Can you deploy an environment (platform and application) in one step?
- Do you deploy your applications daily into production-like environments and verify them?
- Do you link bugs and work items to changes in the application and configuration?
- Do you associate tickets for production issues with relevant bugs opened for development to fix?
- Do you have automated tests to validate your application and platform function and characteristics?
- Do you monitor software against expectations after deploying your application?
- Do you have a delivery pipeline exposed through a summary dashboard to assess delivery velocity?
What do you think? Will these 12 steps help your organization achieve DevOps?
Click here for the full article and complete descriptions of each of the 12 steps to better DevOps