With the increase in the DevOps adoption and benefits declared in the industry, organizations that haven’t yet kicked off the journey are now in a rush to implement DevOps and reap its benefits. For traditional organizations the shift that DevOps brings can be disruptive. DevOps however, not only requires the adoption of a mindset working in collaboration but also a right choice of a pilot project to implement DevOps. The right selection of the pilot project will act as a catalyst to drive the DevOps movement in the organization seamlessly. Some of the attributes of the project to be examined before selecting for DevOps implementation are listed below:
- Project Size: To create an impact of DevOps benefits, the project should be sufficiently large, i.e., having a team size of at least 20-30 people. Small projects may not show the impact which is required to bring in the momentum expected by business stakeholders.
- Duration of the project: If any project is scheduled to be executed in less than a year then it may not be a good candidate to demonstrate the immediate benefits.
- Business impact/visibility of the project: Assess the risk-taking ability of starting with a business critical application which has high visibility and business impact.
- New demand from business and technology: The current market trends forcing organizations to react quickly to be competitive. If the project gets frequent new demands from business then it is a good candidate for DevOps implementation.
- Release Cycle: Back-end applications which are hardly showing any signs of change are not good candidates. Focus on applications that require regular and frequent updates / releases.
- Status of the Tools: Assess the capability of the existing tools to tackle DevOps practices with minimal efforts. In case all the tools need replacement then think twice before selecting this project.
- Efforts spent per Release: Some complex projects consume significant amount of efforts for every release to succeed. Such projects can benefit from automated release process of DevOps.
- Efforts spent on Regression Testing in each Release: Most agile projects spend a good amount of effort in refactoring from sprint to sprint. This results in an increase in regression testing of previous sprints. If the regressions testing efforts are more, then such a project can be considered for DevOps implementation.
- Existing Practices: If the culture of the organization is traditional and refuses change then first educate the project team on the importance of collaboration and communication before shortlisting such a project.
- Dependent systems: If project is integrated with many other applications, assess the impact of downtime on other dependent systems.
So, selecting the right project for DevOps implementation will definitely whet an organization’s appetite to take a calculated risk and reap the benefits of DevOps to do something innovative.
Authors: Sambasivarao Pandala : Head – Application Development & Integration Services
Harshita Darwatkar: Head – Application Support & Maintenance Services