Tying Agile with DevOps to Function as One Team
23 October 2015
Opinions represent those of the author and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.
Agile and DevOps go hand in hand, but are there any specific considerations to ensure a successful collaboration between development and Agile operations?
Agile primarily focuses on the collaboration between self-managed and cross-functional teams to deliver products or services to the business and transition the business to operations that support production. To build a tighter integration between Agile and DevOps, self-managed and cross-functional teams are needed in addition to team members who understand the nuances of the business and production. This integration completes the value chain from business to production and beyond. Wherever possible, a definite role rotation can be planned within the value chain to evade any critical dependency and to improve collective ownership.
In addition to having the right mix in a team, it is important to have the right mix of tools that can automate the review and approvals of regulatory requirements such as documentation and approvals. Also, your standard operating procedures must be clearly defined to make the regulatory requirements mistake-proof and to reduce the development life cycle from inception until go-live.
The preproduction environment should mirror the live production environment to prevent postproduction verifications and to optimize the availability of the production environment.
Groom the teams in a way so that Agile and DevOps are one team -- no Ops or production support teams -- and everything (new development and support) is owned by this team.
Test and refine all the resources, such as human and technical resources, until you attain the desired results. Before embarking on this journey, it is important that all key stakeholders for the transformation understand what problem is being solved with this change, and they should build an appetite for challenges until the change is stabilized and the desired results are attained.
In a service industry in which multiple vendor teams are working on different pieces of the product, do the appropriate value stream mapping across the functional boundaries and define the right mix of value streams. Work as one team irrespective of organizational demarcation.
Current rating: 3 (2 ratings)
The community welcomes feedback that is constructive and supportive, in the spirit of better understanding and implementation of Scrum.