Last updated 22/07/2021
Numerous associations see a transition to light-footed programming advancement and afterward to DevOps as key strides in their computerized change ventures.
Yet, much of the time, these advances are handled by littler groups, subsequently constraining the general effect they can have. Revealing these practices all the more comprehensively all through the association can deliver noteworthy profits by redoing forms on a more terrific scope. However, making that jump is testing.
Agile, an advancement philosophy that includes joint effort among self-sorting out and cross-practical groups, just as the end-clients of the product, is planned for improving the quality and speed of software and service development.
DevOps, then, mixes software development and IT operations to abbreviate the advancement lifecycle and furnish continuous delivery of applications with high caliber.
Together these methodologies can quicken digital transformation and majorly affect how work completes — especially in the event that they are scaled up to include more clients and activities. Here are a few hints for prevailing with Agile and DevOps at scale.
Organizations looking to scale Agile and DevOps as a feature of their advanced change must set up a culture that grasps the sharing of obligation and responsibility for ways to deal with software development.
“DevOps skills and DNA must be widely spread across the organization,” states Herve Coureil, a chief digital officer at Schneider Electric, a provider of energy and automation products. “It has to become part of the company culture.”
To arrive at that objective, organizations can't restrain duty regarding Agile and DevOps to a subset of specialists. “Providing releases compliant with DevOps best practices becomes the responsibility of the whole team and not one single individual who could become a single point of failure,” Coureil says.
At Schneider, “the agile and DevOps vision is to transform the overall operating model” of the company, Coureil continues. “We are applying agile practices to have continuous and transparent communication flow across all functions of the organization, including portfolio management, finance management, product management, product engineering, architecture, professional services, and end consumers.”
Right off the bat in 2019, Schneider made an Agile Transformation Office assist groups to deliver digital products quicker, with better quality and with minimal measure of waste.“We are adopting the ‘Wave and Spike’ approach to scale the transformation” across the company, Coureil says. “Any product or set of products that are chosen in a wave applies all aspects of [the] new operating model leveraging agile Scrum and Kanban, DevOps CI/CD [continuous integration and continuous delivery], and continuous feedback and Lean practices of portfolio management.”
The organization offered workshops for groups to pick up Scrum practice understanding and gave mentors to enable the groups to enhance their utilization of Agile. The entirety of Schneider's improvement extends now to influence agile structure approaches.
It's insufficient to simply grow the sending of Agile and DevOps over the association. Organizations need to gauge the worth these activities are conveying at each phase of the extension.
“Define key performance measurements with a current state baseline and iteratively measure and progress,” Coureil says. “Start with an understanding of existing team roles and work practices to understand how they are working and where improvements are needed.”
Schneider had a few groups utilizing the waterfall model of advancement — which separates venture exercises into straight successive stages in which each stage relies upon the expectations of the past one — progress to the Scrum Agile process framework.
“We had other teams practicing parts of Scrum, but not consistently,” Coureil says. “We created a team self-assessment template that helped teams understand agile best practices, their own practices, and what they needed to do to improve.”
“IT service provider Insight Enterprises uses measurements such as technical progress, product pipeline trends, resource consumption, product quality, performance, and business outcomes”, says Jonathan Parnell, senior digital transformation architect. Explicit variables to inspect incorporate procedure time, time to relieve issues, expenses to fix item deformities, and others.
On the individuals/social side, the board likewise sees drifts in group elements, process overhead, reliability, assurance, and inspiration.
There's no lack of items to assist ventures with misusing DevOps, and a considerable lot of these can be helpful. However, it's imperative to make preparations for apparatuses swelling. “Having too many referenced tools would result in different behaviors between teams and limit the shared culture,” Coureil says. “It would make the adoption of best practices and standards harder, increase our potential [cyber security attack] surface, and prevent scale savings.”
Schneider's key DevOps designers are responsible for keeping up the instrument stack, consistently improving it to cover new utilize cases or innovation settings, and making changes when required. “It requires a permanent technology watch,” Coureil says.
To empower profitability and assurance security, Schneider keeps up a mutualized DevOps apparatus stack that covers a scope of advances and situations, including cloud-based applications and sensors utilized for the Internet of things (IoT) applications.
It’s important to consider security measures at the outset of agile and DevOps initiatives, so as not to cause issues that can plague the development lifecycle.
Prior to joining Insight, Parnell worked as a director of engineering at a media services and production company, and discovered that “no matter how fast our releases and deployments were, security was not only a bottleneck but an inhibitor to speed and scalability,” Parnell says. “The level of trust and motivations were drastically misaligned. Not everyone across the value-stream felt the responsibility of security.”
At the media company, development had been focused on business end-users, without the appropriate security contexts. “We had missed a crucial perspective technically of considering security as part of quality, and security violations as bugs and defects,” Parnell says. “We had to go all the way back to address this within continuous integration.”
The company put in place a number of security-based elements, including policy-driven development that took into account threat modeling and other security measures, a “security-by-design” approach, and recommended security practices.
“This took over a year to implement due to the amount of technical debt we had incurred not starting with security, and the amount of cognitive load it took to evangelize a ‘security culture,’” Parnell says.
The governance of agile and DevOps is also important. “Avoid the pitfall of agile being translated into ‘everybody gets to do what they want to do,’” says Steve Bagby, CTO at Mastercard, a payments technology company. “This will only result in chaos and kill your ability to operate and secure your systems, impeding your ability to ultimately delight your customer.”
Mastercard has been organizing its engineering teams around agile principles for several years. “Since nearly all of what we do is delivered as a service, building for operability [has] always been an integral part of that, out of necessity,” Bagby says.
There’s a clear benefit of integrating responsibilities for building, deploying, and running applications because everyone has something at stake and feels accountable to the team,” Bagby says.
To deploy agile and DevOps broadly in an organization means having a lot of staffers who are well versed in these methods and prepared to make the necessary changes in development processes.
“Train early and often, including face-to-face classroom training with practice scenarios,” Coureil says. “We did dozens of hands-on classroom training sessions globally to establish a foundation. We then had our coaches do small training sessions to reinforce best practices.”
All the content for training was made available in an interactive learning portal for re-use across teams, Coureil says. “Everyone can add their own comment and content to enhance the learning,” he says.
For its agile and DevOps initiative, the media company Parnell previously worked at created a cross-functional team of 12 to 15 people, including developers, database administrators, and representatives from IT operations, networking, security, and lines of business.
“This team went through a series of initial workshops to get alignment and upskilling/enablement on the concepts, fundamentals, best practices, and nomenclature of agile and DevOps” and other related disciplines, Parnell says. “This is critical. Without basic alignment on these things flow is nearly impossible.”
The media company discovered with a cross-functional team representing various dimensions of the business that motivations varied and in some cases were diametrically opposed. “Especially developers who wanted speed and elasticity versus operations and security who required stability and safety,” Parnell says. “It became a balance of offense — exploiting opportunities — and defense — managing risks and uncertainty — by incorporating objective evidence from metrics.”
A number of the steps covered earlier involve the sharing of practices. But it’s worth mentioning separately how vital this is to scale agile and DevOps successfully throughout an organization, and that there needs to be a mechanism for doing this.
Insurance firm Liberty Mutual Insurance has created an Agile Enablement Office, which helps various development teams gain maturity in agile and DevOps over time.
“We also hired experienced talent, like Scrum masters, from outside of Liberty to bring best practices in and be embedded within teams,” says Mark Cressey, senior vice president, and general manager of hosting services at the firm.
“In some cases, they took on the work, and in most instances, they coached the internal Scrum masters we were bringing on as part of our transformation,” Cressey says. “It was really important to not let every team go in their own direction. Supporting them through outside knowledge about agile, agile transformation, and DevOps was key to our success.”
Sharing experiences also means hearing back from teams about their progress or any issues that arise. “It hasn’t been a linear path from zero to 100 percent agile,” Cressey says. “But we’ve listened to the teams throughout the process, and when we needed to take a different direction based on that feedback we did. We paused or reset any given area of practice to get critical feedback about what’s working and what’s not working.”
Scaling agile and DevOps might come naturally to those organizations that are “native” to these methodologies. But for the many that are relatively new to the concepts, support from senior executives is a key to success.
“Everyone says they want to be or already are agile. But in order to truly live up to that claim, top-level executives must fully buy into the concept,” says Mark Mathewson, CTO, small business and international, at financial services firm Capital One.
“In my work, I’ve found that executives must support all aspects of budgeting, capacity planning, among other concerns,” Mathewson says.
Capital One is seven years into a massive technology transformation, through which it has comprehensively reinvented its talent and culture, how people work, and the technology infrastructure. “We moved to a 100 percent agile model for delivering software and built a scaled engineering organization,” Mathewson says.
The company spent three years moving to the cloud, scaling DevOps, adopting open source, and is beginning to take advantage of the flexibility created. Capital One is now turning its attention to standard and continuous delivery.
“It used to be that developers' involvement with products mostly ended after delivery to operations,” Mathewson says. “Now that we're practicing a DevOps approach, our developers feel even more ownership of these products, and are empowered to get proactive about uptime, supportability, and monitoring.”
NovelVista Learning Solutions is a professionally managed training organization with specialization in certification courses. The core management team consists of highly qualified professionals with vast industry experience. NovelVista is an Accredited Training Organization (ATO) to conduct all levels of ITIL Courses. We also conduct training on DevOps, AWS Solution Architect associate, Prince2, MSP, CSM, Cloud Computing, Apache Hadoop, Six Sigma, ISO 20000/27000 & Agile Methodologies.
* Your personal details are for internal use only and will remain confidential.
|AWS Solution Architect Associates|
|SIAM Professional Training & Certification|
|ITIL® 4 Foundation Certification|
|DevOps Foundation By DOI|
|Certified DevOps Developer|
|PRINCE2® Foundation & Practitioner|
|ITIL® 4 Managing Professional Bridge Course|
|Certified DevOps Engineer|
|DevOps Practitioner + Agile Scrum Master|
|ISO Lead Auditor Combo Certification|
|Microsoft Azure Administrator AZ-104|
|Digital Transformation Officer|
|Certified Full Stack Data Scientist|
|Microsoft Azure DevOps Engineer|
|Professional Scrum Product Owner II (PSPO II) Certification|
|Certified Associate in Project Management (CAPM)|
|Practitioner Certified In Business Analysis|
|Certified Blockchain Professional Program|
|Certified Cyber Security Foundation|
|Post Graduate Program in Project Management|
|Certified Data Science Professional|
|Certified PMO Professional|
|AWS Certified Cloud Practitioner (CLF-C01)|
|Certified Scrum Product Owners|
|Professional Scrum Product Owner-II|
|Professional Scrum Product Owner (PSPO) Training-I|
|GSDC Agile Scrum Master|
|ITIL® 4 Certification Scheme|