DOES15

if it is online I would love the link

Google's 2010 AppEngine report was very good: http://www.zdnet.com...

.@janjoostbouwman Here's @cwebber's post-mortems: https://www.chef.io/... https://www.youtube....

I want to hear the post mortem on this: http://www.detroitne...

The gmail 2009 postmortem was very impressive too. One of the early classics: http://arstechnica.c...

I also love the Transparent Uptime work done by @lennysan. Love that these post-mortems are public. @yesthattom h/t @ernestmueller

@yesthattom It's incredibly useful to see those learnings out in the open.

Sadly Apple didn't publish a PM about this outage but people reverse-engineered what happened. I wish I could read Apple's internal PM! http://blog.streamin...

OH: @yesthattom: "This is a great post-mortem that Apple customers wrote" http://blog.streamin...

Hi Carmen and all

Glad to have you all on!

hellllloooo. Awesome gathering of #does15'ers!

Hello all

.@carmendeardo hola

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

Here we go! So excited to see what is about to unfold!