7 roles DevOps need to succeed Almost all IT organizations want to adopt the DevOps application, and the promise of faster software development and greater business agility stems from simplifying and accelerating interactions between development and operations. The problem is that there is no easy or quick way to get there. "Many organizations have gone this way, considering it to be a purely technological game: to get the DevOps tool and life will be much better," says Rohit Anto, partner and head of business solutions at DevOps with PwC Global IT Advisory. These efforts often fail. The successful journey begins with the right people in the right DevOps roles with the right skills and willingness to cooperate. IT leaders must employ, empower, seven new or sophisticated professional roles. In addition to the Basic Change Control Agent for DevOps, these roles include launch managers, automation engineers, test developers, experience assurance experts, security engineers and public service technology operators who understand evolution. Operations. New skills and new roles.
There is nothing like the DevOps team, says Antao and other experts. It is an approach. What's more, there is less clarity regarding the roles of DevOps. Not surprisingly, DevOps is described as "one thing everyone wants but nobody wants to do," says Mark Warren, product marketing manager for source code management and the Perforce Collaboration Platform Factory. The seven important roles. While the adoption of new or redefined roles is not enough in and of itself to successfully transform DevOps, it is an essential first step. "In the unsuccessful DevOps initiatives, the organization does not realize that people are the most important component of the equation," says Gary Lishwito, vice president of Managed Services Delivery and Business Advisory Platforms Capgemini North America. "These organizations often appoint members of their new DevOps teams before understanding and documenting the technical and soft skills needed for the high performance DevOps team." And do not realize that not all employees have the insight or desire. Are essential for success in a very smooth and mutually supportive environment. " 1. DevOps Evangelist "There are IT organizations that have evolved to exploit the practices and capabilities of DevOps, and there are IT
organizations that are in the process of doing so," says Crocker. "This development will not happen on its own, and the vital role here is limited to the person responsible for that change." Evangelist DevOps is your leader.
This person must promote the benefits of DevOps by identifying and measuring the business benefits that derive from the agility provided by DevOps. As a change agent, DevOps Evangelical ensures acceptance by development and operating teams, identifies key roles to support DevOps delivery methods, and ensures that IT professionals are trained and qualified to perform those tasks. Changes, says Nagisetty. In addition, the DevOps leader needs to eliminate fear of organizational failure, says Anto. "You have to build a culture of learning where it is safe to fail, fail quickly, learn from it and improve it." Crocker agrees. "In an organization led by DevOps, there are some new roles ... but it is much more important that cultural change be made to meet the challenges of delivering IT and IT operations in silos," he says. 2. Version Manager. If you call this role the launch manager, the launch engineer, or the product stability manager, the approach is the same: "Release managers work to manage product coordination from
development to production," says Nagisti. "They usually work on more technical details and obstacles that will not involve the traditional project manager." Version managers oversee coordination, integration, flow development, testing and deployment to support continuous delivery. Anto says they focus not only on creativity, but also on maintaining a series of end-to-end delivery tools. 3. Automation Engineer. Because DevOps rely heavily on automated systems, this functionality is key. Sometimes called integration specialists, automation engineers analyze, design and implement strategies for continuous implementation and ensure high availability in production and pre-production systems, says Nagisetty. "Automation engineers have an integrated automation role in DevOps tools and cloud platforms," says Leitao. "This role can also include flexible thinking in major DevOps operations." The role of an automation engineer becomes crucial in the world of DevOps. "DevOps should provide a highly reliable, fully automated and barrier-free environment," says Mizrahi. "With the waterfall, everyone had to ride four-wheel drive vehicles on the off-road." DevOps automates the construction of the highway so that the rest of us can use fast cars.
This position is particularly important for geographically distributed organizations, he adds. 4. Test the developer / software. The software developer is at the heart of the organization DevOps. Under DevOps, the developer's title may remain the same, but the role of the new developer / lab increases the scope of responsibilities. Developers are not only responsible for converting new requirements into code, but also for testing unity, implementation and continuous monitoring. "They're not just setting a standard code, they're throwing it at the quality control team," says Antoine of PricewaterhouseCoopers. While DevOps has more extensive collaboration among development and operations groups, it is sometimes called DevTestOps, a name that reinforces the idea that testing is part of the process, says Nagisetty. This change often requires moving to more automatic tests so that quality is not affected. "The problem is that the teams still think they can do manual tests, that they are flexible, and you can not," says Mizrahi. "If you need to experiment with new constructions every day and you're doing two-week manual tests, you're in an impossible situation." Product quality is usually deteriorated until the organization and processes change accordingly.
DevOps Online Training 5. Professional Experience Guarantee (XA). Although QA is often part of software development, a new type of control is needed when DevOps are adopted. The need for quality control testing is replaced by the need for XA experts to ensure the deployment of all new functions and features taking into account the end-user experience. "The current expectation of quality control roles is to test the function, but the role must evolve to include a user experience guide" 6. Security Engineer. In the development of the traditional waterfall, system security is often a late event. It is a "non-functional requirement", such as quality assurance, often addressed at the end of system development, DevOps-minded workshops include security engineers working side by side with developers, integrating their recommendations early in the process. "They build security in the product.
AnyOne Interested to Learn DevOps Course Reach Out Us:
We Offer DevOps Project Training For More Visit: Visualpath.in Contact: 9704455959