‘DevOps’ (note: no gap between Dev and Ops) is as exciting as a T20 cricket format compared to a Test match. In the immensely competitive and innovative software industry, DevOps is certainly a buzz word to understand. Before an IT organization invests in DevOps practice, below are the key questions for self assessment, in order to mark a successful entry into the continuous IT delivery.
- Are there really walls between Dev, QA and Ops teams in the organization and Why? People do not collaborate among themselves? Processes does not communicate to each other? Tools does not integrate between them?
- Does your business has enough appetite to consume the agility you intend to produce? What does your customer want? Do they want 10 deployments/day? Will they be confused on the pace of change?
- Are the current IT, QA and Operational processes repeatable and optimised to the maximum in their respective engineering functions? Are they ready for synergy between them?
- High quality and Faster time to market are trade offs and requires maturity over a period of time to balance the value. Do you really want to deliver software faster by taking a risk on quality? What does poor quality means in your business?
- How complex is your IT delivery team structure? If they are geo dispersed and multi vendor based then there are enough challenges to optimize and warrants current state maturity first, for engineering process optimisation.
- How mature is the organization's automation maturity? Is it scalable and robust? What is the organization’s tool strategy? Decision making and tool selection to implementation quick enough?
- What is the current feedback cycle from Ops back to Dev? DevOps will not define one, but can accelerate.
- What is the current level of Dev quality evidenced in the organization? Poorer the quality, more time needs to be spent in improving the core IT engineering processes before joining the DevOps movement.
No comments:
Post a Comment