Do you know how to evaluate Devops?
This is part five of the five part series where we will look at DevOps and the solutions that can be gained by its implementation.
__ Driven by a confluence of business and technological trends, the move to DevOps will continue to gain traction. To keep pace with this momentum, it’s incumbent upon the development and operations teams to work together more closely. This requires cultural, process, automation, and other changes to existing behavior.
When evaluating automation solutions and other technology, it’s wise to adopt a system that fosters integrated Dev and Ops collaboration. Each team has much to offer: Dev possesses essential experience and knowledge that can lay the foundation for a successful DevOps architecture, and Ops is critical to deploying and running the application.
To help evaluate a DevOps solution, consider these 10 questions:
Can it easily model the development and delivery workflow, including the entire build-deploy-test-release process?
Can it leverage existing scripts and add value around them?
Is it flexible, with support for any language and methodology, such as Agile, waterfall, and others?
Does it provide out-of-the-box integration to many of the common tools in the organization’s tool inventory, such as build, deploy, test, release, and so on?
Can it integrate to any infrastructure platform, including physical, virtual or cloud?
Can multiple tasks be run in parallel? Is it easy to model parallel jobs?
Can manual transition approval steps be configured?
Can it enforce role-based access control between teams?
Is the solution able to scale to the entire organization, with hundreds of users, resources and concurrent tasks/jobs?
Does it provide real-time and comprehensive visibility into the status of the workflow process and jobs?
Stay up to date
We'll never share your email address and you can opt out at any time, we promise.