DevOps - Applying Lean & Agile Principles to Operations & More

Post on 12-Apr-2017

164 views 1 download

Transcript of DevOps - Applying Lean & Agile Principles to Operations & More

F R I D A Y - M A Y 2 7 , 2 0 1 6

Chris Edwards

OpsDevApplying Lean & Agile Principles to Operations & More

Chief Architect, Kasasa

Slides and video will be posted on architester.com after the conference.

OpsDevWhat is ?

Clarity from a example.

Two goals of software organizations

ValueSpeed

to ServiceQuality

ofConflict

Optimize Preserve

ValueSpeed

to ServiceQuality

ofConflict

Optimize Preserve

OpsDev

OpsDev

OpsDev

QADev

This is a solved problem!

How?

Test Automation

Increased Collaboration

Moved QA to the front of the process

Embedded QA in the Team

Shared Responsibility & Shared Pain

Acceptance Criteria required for stories

Quality added to the definition of “done”

Feedback within minutes of commit!

QA is now “baked in” to our process!

OpsNow apply the same lean/agile principles for…

A DevOps Definition: Extending Lean & Agile principles to include the entire value chain

across all parts of a software organization

What would this look like?

Consider what Ops do…

How can we Automate?

IaaS, PaaS or Virtualization

Configuration Management Tools

Infrastructure as Code

Consistent Environment Creation

Fast Feedback on Production Readiness

Increased Collaboration

Embed Ops in the Team

Devs help support code in prod

Move Ops to the front of the process

Push to Production Early & Often

Definition of Done = Works in Production

Ops is now “baked in” to our process!

What about other parts of the org?

Pause for Review & Questions❖ Automation

❖ PaaS / IaaS / Virtualization ❖ Configuration Management ❖ Infrastructure as Code ❖ Consistent Environments

❖ Collaboration ❖ Embedding Ops on Team ❖ Devs carry the pager

❖ Moving Ops to the Front ❖ Push to prod early & often ❖ Done = Works In Prod

Slides and video will be posted on architester.com after the conference.

Theory of Constraints“Eliyahu M. Goldratt, who created the Theory of Constraints, showed us how any improvements made anywhere besides the bottleneck are an illusion.”

-Erik, The Phoenix Project

Optimize for the Whole“An orchestra is judged by listeners, not so much by illustrious players, but by the way they work together.”

-W. Edwards Deming

Continuous Improvement“Improving daily work is even more important than doing daily work.”

-Erik, The Phoenix Project

The Four Types of Work❖ Business Projects ❖ Internal IT Projects

❖ Changes & Maintenance ❖ Unplanned Work

How can I control unplanned work?

Make the Work Visible

Elevate Preventative Work

Automate Away Human Error

Shore Up Fragile Systems

What do I do about bottlenecks?

Identify the Bottleneck

Protect & Exploit the Bottleneck

Standardize Work

ResourcesDevOpsWhere do I go from here?

Slides and video will be posted on architester.com after the conference.

Slides and video will be posted on architester.com after the conference.

Attend a DevOps Days Event!

❖ Agile Austin DevOps Sig ❖ Austin DevOps Meetup

Attend Monthly Meetups

Slides and video will be posted on architester.com after the conference.

Questions?AnySlides and video will be posted on architester.com after the conference.

Email: ChrisEdwards357@gmail.com

Blog: http://architester.com

Twitter: @ChrisEdwards357

Github: http://github.com/chrisedwards

Who am I?

Chris EdwardsChief Architect, Kasasa

Slides and video will be posted on architester.com after the conference.