Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

MIT’s Dr. Steve Spear on What Makes a High Performing Org

DZone's Guide to

MIT’s Dr. Steve Spear on What Makes a High Performing Org

MIT’s Dr. Steve Spear shares his years of research into high performing organizations with his talk: Creating High Velocity Organizations.

· DevOps Zone ·
Free Resource

Learn more about how CareerBuilder was able to resolve customer issues 5x faster by using Scalyr, the fastest log management tool on the market. 

Some organizations are just  doing  better than others. They achieve exceptional levels of performance and market leadership – from time to market, quality, safety, affordability, reliability, dependability and adaptability—that it puts their rivals to shame.

At the recent DevOps Enterprise Summit, MIT’s Dr. Steve Spear gave an excellent talk on Creating High Velocity Organizations. Spear shared his years of research into these high performing organizations across a variety of industries – including manufacturing, high tech, heavy industry, product design and production, and services, such as healthcare delivery. He studied Toyota, Alcoa, the U.S. Naval Reactor program, and others – to distill for us what it is that makes them so much better?

Watch my short 5 minutes interview with Steve Spear at DOES15 to learn what drives the success of these companies, and what software and DevOps have to do with it.

Watch the Interview With Steve Spear:


Also, check out the recording of Steve’s talk to learn about the capabilities and attributes (cultural, structural, and management methods) common to these high-performing organizations, and the impact these have on the competitive advantage and bottom line of businesses today.

Watch Steve’s Talk: Creating High Velocity Organizations


Find out more about how Scalyr built a proprietary database that does not use text indexing for their log management tool.

Topics:
devops ,culture ,workflow

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}