Sometimes you just need to take a step back and make sure everyone is on the same page. This very short presentation is what I use to ensure that the people I do software development with understand what I mean when I say "DevOps".
not a team of “full-stack” polyglots who each have knowledge of both development and operations • DevOps is not simply combining the Development and Operations teams • DevOps is not an interchangeable process that can be carried from one team to the next @michaelswinslow
process by which the Dev and Ops teams create, release and support software • A movement toward defining temporary intersections between Development and Operations teams • Different (always) • A Mindset or Culture What is DevOps? @michaelswinslow
Switching: It’s a major problem for developers • Developers tend to be more productive in a planned release cycle with large amounts of “heads down” time • Giving Estimates: It’s a major problem for ops engineers • Operations Engineers tend to be interrupt driven and are often the ones asked to investigate production issues • Developers often prefer Scrum / Operations often prefer Kanban @michaelswinslow
DevOps? • Minor Reason: Production Support • Temporarily fix Production issues • Major Reason: Process Improvement • Permanently fix issues that were found in Production • Find issues before they reach Production • Reduce the time it takes to identify production issues • Reduce the time it takes to reproduce production issues in other (safe) environments for testing • Reduce the time it takes to move software through the pipeline @michaelswinslow
michaelswinslow
kawaguti
yasumuusan
kaz1437
databricksjapan
hirotomotaguchi
coconala_engineer
tomorrowkey
ham0215
tomu28
trycycle
ma3tk
aeonpeople
bkeepers
geeforr
shlominoach
pauljervisheath
chrislema
cromwellryan
bermonpainter
chrisshort
afnizarnur
philhawksworth
aleyda
chriscoyier
