DOES15

Businesses may be compelled to pursue DevOps if they need to improve SW Delivery outcomes

hey folks... I'd say when they're finally tired of feeling the pain of NOT engaging in DevOps

Needs for faster cycle times, improved quality, better cost efficiency

.@DOESsummit heh... ALL orgs (*) are ready to (at least) get started... building empathy muscles and making "a thing" more efficient

@stbrodie Agree with Steve. It's hard to think of an organization that shouldn't be interested in DevOps but then again, I am biased :-)

That said, there needs to be a willingness to address the organizational and cultural pre-requisites

@stbrodie a need for automation!

If you are getting sick of 8 hour conference calls with forty people on them holding their breath hoping things will work...

.@DOESsummit perhaps start with something very manually and error prone, automate it, iterate to next thing.

An interest in improvement

@joshcorman automate all the things in all the organizations!

If you have a lot of wait states and waste and don't have visibility across the value stream

When they are ready to break down the wall

For our team, while we've had to cut the size of the staff, I've made the case that, more than ever, we need to automate, engage in CI/CD to ensure we can continue to enjoy quality and feature delivery with a smaller team.

That's it. That, and an organizational will to do something about it.

many teams start out with agile development but then realize that you have to go broader than that. To drive more improvement across the entire value chain.

Yes Carmen. That's the next logical step after they've embraced agile methods

.@DOESsummit 1 of my favs is intro Deming's Supply Chain Principles... [cont]

.@DOESsummit [cont] 1) Fewer Suppliers 2) Best Supplies from 'em 3) Track which parts went where ==> Less Unplanned work, Break-Fix, Faster MTTR

Other indicators include: your Ops team is unable to take vacations, outages are more likely during code pushes, and new feature are written but don't appear in production for months.

@michaelvalentin Automation truly is a force-multiplier!

@carmendeardo that's also how we got started. You can't get the full potential of Agile without including Ops in your team

Well said Michael

@anders_wallgren agreed. the hardest part is to breakdown the QA silo thinking and get them to enhance their skills so that they can engage in the automation engineering

.@DOESsummit Teams often learn DevOps the first time as they transition from building OnPrem SW to Cloud

@joshcorman Agree with Josh's suggestion to start small with a painful manual task and then iterate

if you want to get better at something, you do it more often and measure when it fails so you can improve

(1) Downtime from failed deployment, (2) Cost of failed deployment (3) If no rolling deploys, can deploy be completed within maintenance window

.@DOESsummit #sarcasm ... by the trail of terminated employees??

why is is important? Continuously measure and improve

.@DOESsummit more seriously though. ALL SYSTEMS FAIL. The trick is do we learn from them. FailSmall, FailFast, Iterate.

.@DOESsummit I love Dan Geer's Principle... "No Silent Failures". I.e. did we see it, were there leading indicators

You do need to get your deployment process under control and then work to make it faster via automation and integration

let's not forget that this ALL starts with Culture. Unless the culture changes, unless the people who can make changes "care" about changing vs. protecting their silo/department, it becomes a grass roots effort at best.

@joshcorman Success is boring. Spend more time planning for failure than you do for success. Hopefully you'll be more bored that way.

@carmendeardo exactly: measure, improve, automate

Agree that culture change is a huge factor and moving away from high ceremony procedures and moving away from time based releases to readiness based

@joshcorman Iteration FTW!

By sharing learnings, best practices, challenges to be solved

more community involvement in things such as CrowdChat!

sharing is caring. Give talks, post blogs with your findings, teach workshops

Attending DevOps Enterprise Summit 2015 is a great forum for sharing with the community

@stbrodie this will be a major focus at the conference this year!

@stbrodie def. get together at conferences

@JanJoostBouwman "sharing is caring" - heard that in a childs song once. Some things will never change.

One thing I really admire about the #DevOps community is that everyone is very open to sharing their experiences, warts and all. #does15

As a vendor, we love to hear what the community would like to see in the tooling and automation front

at the devopsdays amsterdam I did an ignite about the importance of giving back to the community

Sharing experiences and the experiments that we are all trying out to see what is working and what to watch out for. It's a continuous learning experience.

@anders_wallgren exactly!

@carmendeardo continuous all the things!

i think that sharing is even more important for enterprises and other large organizations begining their Devops transformation journey. there are some unique large org challenges

Sharing postmortems... https://www.crowdcha...

@carmendeardo Really looking forrward to your session at DOES15 Carmen

right, Continuous *

@JanJoostBouwman We would love to see that! Do you have a link?

@stbrodie @carmendeardo yes! Last year's talk was awesome.

@stbrodie Thanks Steve, I hope I don't disappoint :-) I don't have any more bathroom jokes (at least not yet :-)

@stbrodie I'm really pleased that we are really getting on to this. We even start contributing to open source, which is a HUGE thing for a bank

the link to the slides should be on my linked in profile. Not sure the ignites were recorded

Awesome. OH: @carmendeardo "Every time I give talk, I learn more than anyone else in the room"

OH: @janjoostbouwman: "I want to impress upon my peers that it's important to share our #devops journey and story"