Continuous Discussions Podcast, Episode 89: The DevOps Toolchain [Podcast]

i just took part in a great podcast hosted by electric cloud in partnership with dzone with a round-table discussion on the importance of a healthy devops toolchain .

participants in the podcast included:

prashant mohan, product manager for smartbear’s software testing tools. @prashz91

lee atchison, senior director, strategic architecture at new relic. @leeatchison

ian buchanan, developer advocate at atlassian. @devpartisan

mark miller, devops evangelist at sonatype. @eusp | alldaydevops.com

ravi gadhia, senior solutions engineer at github.

our hosts were:

anders wallgren, cto at electric cloud. @anders_wallgren

and

sam fell, v.p. marketing at electric cloud. @samueldfell

key takeaways include:

the devops toolchain as a value stream

it's important to look at the entire value stream looking at the lead time ladder and identifying bottlenecks where automation will add the greatest value.

you need to be able to see upstream and downstream to ensure you are adding value and not duplicating effort. have a single set of integrated tools giving you vision into how the entire process is working.

think about what the code is seeing and how it's being affected.

use tools to align people and teams

given that the greatest challenge to implementing a devops methodology is culture, it's important for every member of the team to have visibility and access to metrics for every link in the toolchain.

devops is enabling cultural transformation while security overlays the entire process.

value stream mapping is the biggest hurdle companies need to get over. once you understand the whole process and the outcomes you are trying to achieve every member of the team is able to see where they are contributing and where they are hindering the process.

is there one right tool?

no; however, there's a correct set of tools for every organization and you determine this by choosing the right tool for the problem you are working to solve. every tool has a purpose and it must integrate with every other tool and provide a holistic view of the process. there is value in standardization; however, be aware that the right tool might change. as such, tools need to be able for clients to change in and out.

the tools have to work together. you cannot expect companies to "rip and replace." it's too expensive, time-consuming, and there are a lot of people to be trained on the new tool.

adapting to the changing environment

we need to be able to abstract out the details of the actual tools and focus on the outcome of the process versus the tool that's being used to achieve the outcome.

tools must integrate into a platform that's easy and intuitive for team members to use. the tools need to provide access to data and vision into the entire pipeline for audit-ability and traceability.

think holistically about the entire devops toolchain.

check out the full episode:

you can find electric cloud's write-up of the podcast here , and check out the previous episodes of continuous discussions (#c9d9) .