Community feedback needed on DevOps adoption paths
Darrel Rader 270002AASK Visits (8940)
Our current DevOps messaging defines four adoption paths: Plan/Measure, Develop/Test, Release/ Deploy, Monitor/Optimize. A few drawbacks have been surfaced with these names:
Here are suggestions for more attractive descriptors of the 4 adoption paths.
In our leadership team, there was fairly quick and strong consensus on Develop/Test, Deploy, and Operate. Steering is the one choice where there was some debate.
Why not plan and measure? Plans and planning are one of the four anti-patterns in the agile manifesto which states: We value Responding to change over following a plan. Responding to change means steering. Following a plan is the connotation of Plan/Measure. Also, measurement is an element of each adoption path, not a specific one. Finally, plan and measure has a programmatic connotation (i.e., plan and track, something managers do) and does not imply the technical leadership of scoping and architecting that should be 1st-class practices in this whole team adoption path.
We would like to test these change with our broader community of clients, partners and IBMers. If you endorse the change, like this post and add a comment if you want to explain why. If you prefer the old wording, post a comment and provide a short reason.