Today on Continuous Discussions we had a great time discussing how horses can become unicorns too.
“Getting to DevOps” for a single product team is no easy task. So how do you “inject" DevOps and Lean principles across 20 “legacy” product teams. Spread out across 4 continents. With different technology stacks.
- How do you move from "Waterfall-ITIL" to "DevOps-Agile"?
- How do you define success?
- How do you encourage experimentation?
- What's differences do you see now in your production pipelines?
Our team of panelists had some suggestions for you.
Make sure *any change* that goes through *anything* - is considered a standard change. @davemangot talks #DOES14 lessons during #c9d9 — CloudBees (@electriccloud) April 7, 2015
You don't want to experiment with the business critical stuff - @uri1803 talks making thr #Waterfall to #Agile /#DevOps change | #c9d9 — CloudBees (@electriccloud) April 7, 2015
Don't be the guy that jumps off the building & halfway down you are thinking "So far so good." @anders_wallgren #c9d9 — CloudBees (@electriccloud) April 7, 2015
Use the language of experimentation - @yuvalyeret . | #c9d9 pic.twitter.com/B8RzNmlGij — CloudBees (@electriccloud) April 7, 2015
Minimum viable product should be called the minimum viable experiment. - @davemangot #c9d9 #DevOps — CloudBees (@electriccloud) April 7, 2015
It is always a change in culture that fosters innovation. - @DimitrisPapatho | #c9d9 — CloudBees (@electriccloud) April 7, 2015
Watch the Replay of this episode to learn more:
This episode features:
On the Next Episode of Continuous Discussions:
An end to "It Worked on My Machine!"
Join us on Tuesday, April 21, at 10am PST , when we'll be talking about Consistent Deployments Across Dev, Test and Prod .
This episode will feature:
Stay up to date
We'll never share your email address and you can opt out at any time, we promise.