Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Without Self-Service Operations, the Cloud is Just Expensive Hosting 2.0 - (a DevOps story)

4,340 views

Published on

Damon Edwards (DTO Solutions) presentation at Cloud Expo 2014 Santa Clara.

We are all here because we are sold on the transformative promise of The Cloud. But what good is all of this ephemeral, on-demand infrastructure if your usage doesn't actually improve the agility and speed of your business? How must Operations adapt in order to avoid stifling your Cloud initiative?

Published in: Technology
  • Good stuff. I'm seeing more and more governance as a service come up in conversations. Might be a nice add to slide 58.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Without Self-Service Operations, the Cloud is Just Expensive Hosting 2.0 - (a DevOps story)

  1. 1. Without Self-Service Operations the Cloud Becomes Expensive Hosting 2.0 Damon Edwards @damonedwards
  2. 2. @damonedwards
  3. 3. devopscafe.org
  4. 4. Operations Tools DevOps Consulting Automation Design
  5. 5. Conventional Cloud Wisdom
  6. 6. Conventional Cloud Wisdom  Saves you time …provision infrastructure really really fast
  7. 7. Conventional Cloud Wisdom  Saves you time …provision infrastructure really really fast  Saves you money …use only what you need, when needed, then shut off
  8. 8. Conventional Cloud Wisdom  Saves you time …provision infrastructure really really fast  Saves you money …use only what you need, when needed, then shut off  Saves your job …or gets you a new one (#linkedin)
  9. 9. We need to move quicker than our competitors
  10. 10. We need to move quicker than our competitors Cloud
  11. 11. Cloud
  12. 12. Why aren’t we moving quicker than our competitors? Cloud But… Server images from x days to z minutes y% improved utilization t% cheaper storage … more ops numbers … more ops numbers
  13. 13. Ops Cloud
  14. 14. Ops Legacy Process and Tooling Cloud
  15. 15. No difference No difference No difference PMO Dev QA Ops Legacy Process and Tooling Cloud
  16. 16. No difference No difference No difference PMO Dev QA Ops Legacy Process and Tooling Cloud No difference
  17. 17. Planning Dev Sprints Integration Infrastructure Procurement and Setup Performance Testing Security Review Prod Release Dev Env Setup Team 1 Team 2 Team 3
  18. 18. Planning Dev Sprints Integration Infrastructure Procurement and Setup Performance Testing Security Review Prod Release Dev Env Setup Team 1 Team 2 Team 3
  19. 19. Planning Dev Sprints Integration Infrastructure Procurement and Setup Performance Testing Security Review Prod Release Dev Env Setup Team 1 Team 2 Team 3 Have we improved our ability to give the customer... • What they want • When they want it • At the lowest cost possible
  20. 20. People Process Tools
  21. 21. Keep focused on the metrics
  22. 22. Keep focused on the metrics Lead Times (and more predictable)
  23. 23. Keep focused on the metrics Lead Times (and more predictable) MTTD (Mean Time To Detect)
  24. 24. Keep focused on the metrics Lead Times (and more predictable) MTTD (Mean Time To Detect) MTTR (Mean Time to Repair)
  25. 25. Keep focused on the metrics Lead Times (and more predictable) MTTD (Mean Time To Detect) MTTR (Mean Time to Repair) Quality at the Source (Less scrap, caught faster)
  26. 26. Slios are the #1 enemy of throughput and quality Dev & Test Activity Release Activity Ops Activity Business Activity
  27. 27. Slios are the #1 enemy of throughput and quality Dev & Test Activity Release Activity Ops Activity Business Activity
  28. 28. Slios are the #1 enemy of throughput and quality Dev & Test Activity Release Activity Ops Activity Business Activity ! Handoff ! Handoff ! Handoff
  29. 29. Slios are the #1 enemy of throughput and quality Handoff Dev & Test Activity Release Activity Ops Activity Business Activity ! Application Knowledge ! Handoff ! Handoff
  30. 30. Slios are the #1 enemy of throughput and quality Dev & Test Activity Release Activity Ops Activity Business Activity ! Application Knowledge ! Operational Knowledge ! Handoff Handoff Handoff
  31. 31. Slios are the #1 enemy of throughput and quality Handoff Dev & Test Activity Release Activity Ops Activity Business Activity ! Application Knowledge ! Operational Knowledge Business Intent ! Handoff Handoff
  32. 32. Slios are the #1 enemy of throughput and quality Handoff Dev & Test Activity Release Activity Ops Activity Business Activity ! Application Knowledge ! Operational Knowledge Business Intent ! Handoff Handoff Ownership but limited Accountability
  33. 33. Slios are the #1 enemy of throughput and quality Handoff Dev & Test Activity Release Activity Ops Activity Business Activity ! Application Knowledge ! Operational Knowledge Business Intent ! Handoff Handoff Ownership but limited Accountability Accountability but no Ownership
  34. 34. Redraw the organization to eliminate silos Dev & Test Activity Release Activity Ops Activity Business Activity
  35. 35. Redraw the organization to eliminate silos Cross Functional Delivery Team Dev & Test Activity Release Activity Ops Activity Business Activity Cross Functional Delivery Team Cross Functional Delivery Team Aligned by value streams or customer identifiable services
  36. 36. Redraw the organization to eliminate silos Cross Functional Delivery Team Dev & Test Activity Release Activity Ops Activity Business Activity Cross Functional Delivery Team Cross Functional Delivery Team Aligned by value streams or customer identifiable services Freedom & Responsibility Culture is key to enabling
  37. 37. Redraw the organization to eliminate silos Cross Functional Delivery Team Dev & Test Activity Release Activity Ops Activity Business Activity Cross Functional Delivery Team Cross Functional Delivery Team Aligned by value streams or customer identifiable services Freedom & Responsibility Culture is key to enabling Do this if nothing else!
  38. 38. Redraw the organization to eliminate silos Cross Functional Delivery Team Dev & Test Activity Release Activity Ops Activity Business Activity Cross Functional Delivery Team Cross Functional Delivery Team Aligned by value streams or customer identifiable services Freedom & Responsibility Culture is key to enabling Google: “Cloud Operations at Netflix” “Actionable Metrics Netflix” Roy Rapoport “DOES14 Netflix youtube" Different Talk
  39. 39. What do you need to do? DevOps
  40. 40. What do you need to do? (Hint: Just doing a re-org won’t work) DevOps
  41. 41. Turn information flow into artifact flow Customer Shared Drive Test Shared Drive Prod Commits Rollout Schedule README MOP Release Schedule PRD PRD Release Memos Tasks QA Forum Ticket Remedy Ticket Estimates Technical Support Patch Calendar QA forum MOP EP(2) README ERR ERR MOP, SOP PRD Design Specs crit bugs email Lockdown control checklist M New Targets Remedy Ticket Single Image Server XML BRD ERR BTS QA Environment Documentum Production Packages Customer communication L/T = 28d P/T = 7d H/C = 1 S/R = Stephen / Xi Product Program Planning L/T = 105d P/T = 46d H/C = 15 S/R = 100% John Robert Release Program Management L/T = P/T = H/C = S/R = Erica Smith Engineering Planning Process L/T = 45d P/T = 18d H/C = 23 S/R = Preliminary Bob Smith Development L/T = 45d P/T = 21d H/C = 140 S/R = Bob Smith Full Development L/T = 75d P/T = 43d H/C = 130 S/R = Bob Smith Build L/T = 1d P/T = 0.3d H/C = 2 S/R = 33% John Doe D Selective Promotion L/T = 90d P/T = 15d H/C = 5 S/R = Steve Young QA Test L/T = 105d P/T = 11d H/C = 42 S/R = Sam Young Engineering Release L/T = 60d P/T = 1d H/C = 1 S/R = >5% Victoria Doe Release Promotion L/T = 60d P/T = 0.2d H/C = 1 S/R = >5% Victoria Doe Cloud Services Release L/T = 60d P/T = 16d H/C = 3 S/R = 3% Reggie / Carlos Change Control L/T = 42d P/T = H/C = S/R = Peter Lee Deploy Release L/T = 90d P/T = 8d H/C = 8 S/R = 2% Lewis S./Peter Y. Server Provisioning L/T = 24d P/T = 4d H/C = 3 S/R = 50% Jen Garza BRD Server Acceptance L/T = 14d P/T = 1d H/C = 4.5 S/R = 15% Lynn A. etc derived reqs. PRD QA Forum Ticket Service pack review L/T = 56d P/T = 7d H/C = 6 S/R = 100% Suresh Wu M PD(3) PD(3) M EP PD M(3) M W(2) TS M(3) M(2) W(2) M(2) EP EP EP(3) W W EP W PD TS(2) M M M(2) M W(2) EP D M(3) EP W EP PD D(3) Current state value stream map L/T Lead time P/T Process time H/C Head count S/R Scrap rate D Defects EP Extra processes M Motion PD Partially done TS Task switching W Waiting Product Management Engineering Cloud Services
  42. 42. Turn information flow into artifact flow Customer Shared Drive Test Shared Drive Prod Commits Rollout Schedule README MOP Release Schedule PRD PRD Release Memos Tasks QA Forum Ticket Remedy Ticket Estimates Technical Support Patch Calendar QA forum MOP EP(2) README ERR ERR MOP, SOP PRD Design Specs crit bugs email Lockdown control checklist M New Targets Remedy Ticket Single Image Server XML BRD ERR BTS QA Environment Documentum Production Packages Customer communication L/T = 28d P/T = 7d H/C = 1 S/R = Stephen / Xi Product Program Planning L/T = 105d P/T = 46d H/C = 15 S/R = 100% John Robert Release Program Management L/T = P/T = H/C = S/R = Erica Smith Engineering Planning Process L/T = 45d P/T = 18d H/C = 23 S/R = Preliminary Bob Smith Development L/T = 45d P/T = 21d H/C = 140 S/R = Bob Smith Full Development L/T = 75d P/T = 43d H/C = 130 S/R = Bob Smith Build L/T = 1d P/T = 0.3d H/C = 2 S/R = 33% John Doe D Selective Promotion L/T = 90d P/T = 15d H/C = 5 S/R = Steve Young QA Test L/T = 105d P/T = 11d H/C = 42 S/R = Sam Young Engineering Release L/T = 60d P/T = 1d H/C = 1 S/R = >5% Victoria Doe Release Promotion L/T = 60d P/T = 0.2d H/C = 1 S/R = >5% Victoria Doe Cloud Services Release L/T = 60d P/T = 16d H/C = 3 S/R = 3% Reggie / Carlos Change Control L/T = 42d P/T = H/C = S/R = Peter Lee Deploy Release L/T = 90d P/T = 8d H/C = 8 S/R = 2% Lewis S./Peter Y. Server Provisioning L/T = 24d P/T = 4d H/C = 3 S/R = 50% Jen Garza BRD Server Acceptance L/T = 14d P/T = 1d H/C = 4.5 S/R = 15% Lynn A. etc derived reqs. PRD QA Forum Ticket Service pack review L/T = 56d P/T = 7d H/C = 6 S/R = 100% Suresh Wu M PD(3) PD(3) M EP PD M(3) M W(2) TS M(3) M(2) W(2) M(2) EP EP EP(3) W W EP W PD TS(2) M M M(2) M W(2) EP D M(3) EP W EP PD D(3) Current state value stream map L/T Lead time P/T Process time H/C Head count S/R Scrap rate D Defects EP Extra processes M Motion PD Partially done TS Task switching W Waiting Product Management Engineering Cloud Services
  43. 43. Insert verification points to drive feedback loops Business Need: Customer Capactiy AZ Redundancy Site Build Value Demand Product Manager -Partnerships -Biz Modeling -Hardware Acquisition 6 months "Acme Partner" Capacity -Pick Site (Colo, Acme Partner) -Physical security with InfoSec, Contractors Procure Hardware -Ship to Uranus -Cabling and power plugs 1.5 - 2 months BOM NetArch ComputeArch StorageArch Security email different parties Customizations Ad-hoc Redesign -5 chassis to 4 chassis to save $$ -No firewall Ops Admin Rack Elevations Patch Diagrams Physical Layouts 1 week correct cables? "must be "latest & greatest" gear!" FooCorp (Contractor) Box.net + Ops Admin Rack and Stack Elevations .vs Patch Plan .xls -Rack/Cable -Network / ? -Labeling Build spec? Build Lead Net Ops Admin -Net connections -VLANs -Subnets -IP Addressing <<Scriptable>> 3w 2d Generic Low Level Design .xls Ops Admin Interprets Compute and Storage Build Team -Hardware Manager Config/Profile -Prepare OS Install -Power failover testing <<Scriptable>> 2-3d Ops Admin Compute and Storage Build 2w -Setup OpenStack, CEPH -Prepare Build Server with software repository (ubuntu) -Cobbler node, PXE booting -Puppet Master -Reprovisioning 2d via cell net Files and Packages Ubuntu OS Openstack .ISV .IMG rsync scp Puppet Server Build Code COI Accumulation Delay Manifests Heira Cobbler yaml Retrofit Jenkins SSD? Customer? Git Dev, Ops Adding Changes Acme Partner Seeding Env. + Services -Reqs -Deliver Schedule -Network -Zoning -Mail Server -Prime Service Catalog -6 VN -Access -Flavors -Tennants -Authorization -Repo Mirror -ID Management System (5d) -LDAP server -2 Factor Auth / Radint -Licenses (SQL Server) -Images -Load Balancer Setup -Monitoring PM (Skipper) Ops Devs A&E -Install HA for each product -Web portal -Databases -A.D. -Prime Catalog 3 weeks Platform Validation Ops Admin -Functionality testing -Boot VMs -Check network -Capacity testing -Synthetic testing Tempest test cases Register Support Contracts for CEPH, Canonical, TAC Punchlist .xls Box.net PM (Lewis) Site specific services and ACLs Weekly Status Meeting Acme Partner PM -Handoff Meeting to Acme Partner -Retrospective Ad-hoc fix push Scrum Fixed in sprint Rally Openstack Bug Dev, Ops QA (SDU) Systems Dev Unit -Testing (destructive, non-destructive) -Restore DB 3-4 weeks Heira Environment Data Defects InfoSec -IDS Infra -Install scanner -Vulnerability scan -3rd party PenTest Account Manager (Bob) 4 months Normalize Standardize
  44. 44. Insert verification points to drive feedback loops Business Need: Customer Capactiy AZ Redundancy Site Build Value Demand Product Manager -Partnerships -Biz Modeling -Hardware Acquisition 6 months "Acme Partner" Capacity -Pick Site (Colo, Acme Partner) -Physical security with InfoSec, Contractors Procure Hardware -Ship to Uranus -Cabling and power plugs 1.5 - 2 months BOM NetArch ComputeArch StorageArch Security email different parties Customizations Ad-hoc Redesign -5 chassis to 4 chassis to save $$ -No firewall Ops Admin Rack Elevations Patch Diagrams Physical Layouts 1 week correct cables? "must be "latest & greatest" gear!" FooCorp (Contractor) Box.net + Ops Admin Rack and Stack Elevations .vs Patch Plan .xls -Rack/Cable -Network / ? -Labeling Build spec? Build Lead Net Ops Admin -Net connections -VLANs -Subnets -IP Addressing <<Scriptable>> 3w 2d Generic Low Level Design .xls Ops Admin Interprets Compute and Storage Build Team -Hardware Manager Config/Profile -Prepare OS Install -Power failover testing <<Scriptable>> 2-3d Ops Admin Compute and Storage Build 2w -Setup OpenStack, CEPH -Prepare Build Server with software repository (ubuntu) -Cobbler node, PXE booting -Puppet Master -Reprovisioning 2d via cell net Files and Packages Ubuntu OS Openstack .ISV .IMG rsync scp Puppet Software Environment Server Build Code COI Accumulation Delay Manifests Heira Cobbler yaml Retrofit Jenkins SSD? Customer? Git Dev, Ops Adding Changes Acme Partner Seeding Env. + Services -Reqs -Deliver Schedule -Network -Zoning -Mail Server -Prime Service Catalog -6 VN -Access -Flavors -Tennants -Authorization -Repo Mirror -ID Management System (5d) -LDAP server -2 Factor Auth / Radint -Licenses (SQL Server) -Images -Load Balancer Setup -Monitoring PM (Skipper) Ops Devs A&E -Install HA for each product -Web portal -Databases -A.D. -Prime Catalog 3 weeks Platform Validation Ops Admin -Functionality testing -Boot VMs -Check network -Capacity testing -Synthetic testing Tempest test cases Register Support Contracts for CEPH, Canonical, TAC Punchlist .xls Box.net PM (Lewis) Site specific services and ACLs Weekly Status Meeting Acme Partner PM -Handoff Meeting to Acme Partner -Retrospective Ad-hoc fix push Scrum Fixed in sprint Rally Openstack Bug Dev, Ops QA (SDU) Systems Dev Unit -Testing (destructive, non-destructive) -Restore DB 3-4 weeks Heira Environment Data Defects InfoSec -IDS Infra -Install scanner -Vulnerability scan -3rd party PenTest Account Manager (Bob) 4 months Physical Environment Server Environment Verification Cloud Environment Normalize Standardize
  45. 45. Insert verification points to drive feedback loops Business Need: Customer Capactiy AZ Redundancy Site Build Value Demand Product Manager -Partnerships -Biz Modeling -Hardware Acquisition 6 months "Acme Partner" Capacity -Pick Site (Colo, Acme Partner) -Physical security with InfoSec, Contractors Procure Hardware -Ship to Uranus -Cabling and power plugs 1.5 - 2 months BOM NetArch ComputeArch StorageArch Security email different parties Customizations Ad-hoc Redesign -5 chassis to 4 chassis to save $$ -No firewall Ops Admin Rack Elevations Patch Diagrams Physical Layouts 1 week correct cables? "must be "latest & greatest" gear!" FooCorp (Contractor) Box.net + Ops Admin Rack and Stack Elevations .vs Patch Plan .xls -Rack/Cable -Network / ? -Labeling Build spec? Build Lead Net Ops Admin -Net connections -VLANs -Subnets -IP Addressing <<Scriptable>> 3w 2d Generic Low Level Design .xls Ops Admin Interprets Compute and Storage Build Team -Hardware Manager Config/Profile -Prepare OS Install -Power failover testing <<Scriptable>> 2-3d Ops Admin Compute and Storage Build 2w -Setup OpenStack, CEPH -Prepare Build Server with software repository (ubuntu) -Cobbler node, PXE booting -Puppet Master -Reprovisioning 2d via cell net Files and Packages Ubuntu OS Openstack .ISV .IMG rsync scp Puppet Software Environment Server Build Code COI Accumulation Delay Manifests Heira Cobbler yaml Retrofit Jenkins SSD? Customer? Git Dev, Ops Adding Changes Acme Partner Seeding Env. + Services -Reqs -Deliver Schedule -Network -Zoning -Mail Server -Prime Service Catalog -6 VN -Access -Flavors -Tennants -Authorization -Repo Mirror -ID Management System (5d) -LDAP server -2 Factor Auth / Radint -Licenses (SQL Server) -Images -Load Balancer Setup -Monitoring PM (Skipper) Ops Devs A&E -Install HA for each product -Web portal -Databases -A.D. -Prime Catalog 3 weeks Platform Validation Ops Admin -Functionality testing -Boot VMs -Check network -Capacity testing -Synthetic testing Tempest test cases Register Support Contracts for CEPH, Canonical, TAC Punchlist .xls Box.net PM (Lewis) Site specific services and ACLs Weekly Status Meeting Acme Partner PM -Handoff Meeting to Acme Partner -Retrospective Ad-hoc fix push Scrum Fixed in sprint Rally Openstack Bug Dev, Ops QA (SDU) Systems Dev Unit -Testing (destructive, non-destructive) -Restore DB 3-4 weeks Heira Environment Data Defects InfoSec -IDS Infra -Install scanner -Vulnerability scan -3rd party PenTest Account Manager (Bob) 4 months Physical Environment Server Environment Verification Cloud Environment Normalize Standardize Verification Point Verification Point
  46. 46. Insert verification points to drive feedback loops Business Need: Customer Capactiy AZ Redundancy Site Build Value Demand Product Manager -Partnerships -Biz Modeling -Hardware Acquisition 6 months "Acme Partner" Capacity -Pick Site (Colo, Acme Partner) -Physical security with InfoSec, Contractors Procure Hardware -Ship to Uranus -Cabling and power plugs 1.5 - 2 months BOM NetArch ComputeArch StorageArch Security email different parties Customizations Ad-hoc Redesign -5 chassis to 4 chassis to save $$ -No firewall Ops Admin Rack Elevations Patch Diagrams Physical Layouts 1 week correct cables? "must be "latest & greatest" gear!" FooCorp (Contractor) Box.net + Ops Admin Rack and Stack Elevations .vs Patch Plan .xls -Rack/Cable -Network / ? -Labeling Build spec? Build Lead Net Ops Admin -Net connections -VLANs -Subnets -IP Addressing <<Scriptable>> 3w 2d Generic Low Level Design .xls Ops Admin Interprets Compute and Storage Build Team -Hardware Manager Config/Profile -Prepare OS Install -Power failover testing <<Scriptable>> 2-3d Ops Admin Compute and Storage Build 2w -Setup OpenStack, CEPH -Prepare Build Server with software repository (ubuntu) -Cobbler node, PXE booting -Puppet Master -Reprovisioning 2d via cell net Files and Packages Ubuntu OS Openstack .ISV .IMG rsync scp Puppet Software Environment Server Build Code COI Accumulation Delay Manifests Heira Cobbler yaml Retrofit Jenkins SSD? Customer? Git Dev, Ops Adding Changes Acme Partner Seeding Env. + Services -Reqs -Deliver Schedule -Network -Zoning -Mail Server -Prime Service Catalog -6 VN -Access -Flavors -Tennants -Authorization -Repo Mirror -ID Management System (5d) -LDAP server -2 Factor Auth / Radint -Licenses (SQL Server) -Images -Load Balancer Setup -Monitoring PM (Skipper) Ops Devs A&E -Install HA for each product -Web portal -Databases -A.D. -Prime Catalog 3 weeks Platform Validation Ops Admin -Functionality testing -Boot VMs -Check network -Capacity testing -Synthetic testing Tempest test cases Register Support Contracts for CEPH, Canonical, TAC Punchlist .xls Box.net PM (Lewis) Site specific services and ACLs Weekly Status Meeting Acme Partner PM -Handoff Meeting to Acme Partner -Retrospective Ad-hoc fix push Scrum Fixed in sprint Rally Openstack Bug Dev, Ops QA (SDU) Systems Dev Unit -Testing (destructive, non-destructive) -Restore DB 3-4 weeks Heira Environment Data Defects InfoSec -IDS Infra -Install scanner -Vulnerability scan -3rd party PenTest Account Manager (Bob) 4 months Physical Environment Server Environment Verification Cloud Environment Normalize Standardize Verification Point Verification Point Verification Point Verification Point Verification Point Verification Point Verification Point Embed in the rest of the process!!
  47. 47. Insert verification points to drive feedback loops Business Need: Customer Capactiy AZ Redundancy Site Build Value Demand Product Manager -Partnerships -Biz Modeling -Hardware Acquisition 6 months "Acme Partner" Capacity -Pick Site (Colo, Acme Partner) -Physical security with InfoSec, Contractors Procure Hardware -Ship to Uranus -Cabling and power plugs 1.5 - 2 months BOM NetArch ComputeArch StorageArch Security email different parties Customizations Ad-hoc Redesign -5 chassis to 4 chassis to save $$ -No firewall Ops Admin Rack Elevations Patch Diagrams Physical Layouts 1 week correct cables? "must be "latest & greatest" gear!" FooCorp (Contractor) Box.net + Ops Admin Rack and Stack Elevations .vs Patch Plan .xls -Rack/Cable -Network / ? -Labeling Build spec? Build Lead Net Ops Admin -Net connections -VLANs -Subnets -IP Addressing <<Scriptable>> 3w 2d Generic Low Level Design .xls Ops Admin Interprets Compute and Storage Build Team -Hardware Manager Config/Profile -Prepare OS Install -Power failover testing <<Scriptable>> 2-3d Ops Admin Compute and Storage Build 2w -Setup OpenStack, CEPH -Prepare Build Server with software repository (ubuntu) -Cobbler node, PXE booting -Puppet Master -Reprovisioning 2d via cell net Files and Packages Ubuntu OS Openstack .ISV .IMG rsync scp Puppet Software Environment Server Build Code COI Accumulation Delay Manifests Heira Cobbler yaml Retrofit Jenkins SSD? Customer? Git Dev, Ops Adding Changes Acme Partner Seeding Env. + Services -Reqs -Deliver Schedule -Network -Zoning -Mail Server -Prime Service Catalog -6 VN -Access -Flavors -Tennants -Authorization -Repo Mirror -ID Management System (5d) -LDAP server -2 Factor Auth / Radint -Licenses (SQL Server) -Images -Load Balancer Setup -Monitoring PM (Skipper) Ops Devs A&E -Install HA for each product -Web portal -Databases -A.D. -Prime Catalog 3 weeks Platform Validation Ops Admin -Functionality testing -Boot VMs -Check network -Capacity testing -Synthetic testing Tempest test cases Register Support Contracts for CEPH, Canonical, TAC Punchlist .xls Box.net PM (Lewis) Site specific services and ACLs Weekly Status Meeting Acme Partner PM -Handoff Meeting to Acme Partner -Retrospective Ad-hoc fix push Scrum Fixed in sprint Rally Openstack Bug Dev, Ops QA (SDU) Systems Dev Unit -Testing (destructive, non-destructive) -Restore DB 3-4 weeks Heira Environment Data Defects InfoSec -IDS Infra -Install scanner -Vulnerability scan -3rd party PenTest Account Manager (Bob) 4 months Physical Environment Server Environment Verification Cloud Environment Normalize Standardize Verification Point Verification Point Verification Point Verification Point Verification Point Verification Point Verification Point Embed in the rest of the process!!
  48. 48. Insert verification points to drive feedback loops Business Need: Customer Capactiy AZ Redundancy Site Build Value Demand Product Manager -Partnerships -Biz Modeling -Hardware Acquisition 6 months "Acme Partner" Capacity -Pick Site (Colo, Acme Partner) -Physical security with InfoSec, Contractors Procure Hardware -Ship to Uranus -Cabling and power plugs 1.5 - 2 months BOM NetArch ComputeArch StorageArch Security email different parties Customizations Ad-hoc Redesign -5 chassis to 4 chassis to save $$ -No firewall Ops Admin Rack Elevations Patch Diagrams Physical Layouts 1 week correct cables? "must be "latest & greatest" gear!" FooCorp (Contractor) Box.net + Ops Admin Rack and Stack Elevations .vs Patch Plan .xls -Rack/Cable -Network / ? -Labeling Build spec? Build Lead Net Ops Admin -Net connections -VLANs -Subnets -IP Addressing <<Scriptable>> 3w 2d Generic Low Level Design .xls Ops Admin Interprets Compute and Storage Build Team -Hardware Manager Config/Profile -Prepare OS Install -Power failover testing <<Scriptable>> 2-3d Ops Admin Compute and Storage Build 2w -Setup OpenStack, CEPH -Prepare Build Server with software repository (ubuntu) -Cobbler node, PXE booting -Puppet Master -Reprovisioning 2d via cell net Files and Packages Ubuntu OS Openstack .ISV .IMG rsync scp Puppet Software Environment Server Build Code COI Accumulation Delay Manifests Heira Cobbler yaml Retrofit Jenkins SSD? Customer? Git Dev, Ops Adding Changes Acme Partner Seeding Env. + Services -Reqs -Deliver Schedule -Network -Zoning -Mail Server -Prime Service Catalog -6 VN -Access -Flavors -Tennants -Authorization -Repo Mirror -ID Management System (5d) -LDAP server -2 Factor Auth / Radint -Licenses (SQL Server) -Images -Load Balancer Setup -Monitoring PM (Skipper) Ops Devs A&E -Install HA for each product -Web portal -Databases -A.D. -Prime Catalog 3 weeks Platform Validation Ops Admin -Functionality testing -Boot VMs -Check network -Capacity testing -Synthetic testing Tempest test cases Register Support Contracts for CEPH, Canonical, TAC Punchlist .xls Box.net PM (Lewis) Site specific services and ACLs Weekly Status Meeting Acme Partner PM -Handoff Meeting to Acme Partner -Retrospective Ad-hoc fix push Scrum Fixed in sprint Rally Openstack Bug Dev, Ops QA (SDU) Systems Dev Unit -Testing (destructive, non-destructive) -Restore DB 3-4 weeks Heira Environment Data Defects InfoSec -IDS Infra -Install scanner -Vulnerability scan -3rd party PenTest Account Manager (Bob) 4 months Physical Environment Server Environment Verification Cloud Environment Normalize Standardize Verification Point Verification Point Verification Point Verification Point Verification Point Verification Point Verification Point Embed in the rest of the process!! •Outside-in perspective on testing (“is this thing working?”)
  49. 49. Insert verification points to drive feedback loops Business Need: Customer Capactiy AZ Redundancy Site Build Value Demand Product Manager -Partnerships -Biz Modeling -Hardware Acquisition 6 months "Acme Partner" Capacity -Pick Site (Colo, Acme Partner) -Physical security with InfoSec, Contractors Procure Hardware -Ship to Uranus -Cabling and power plugs 1.5 - 2 months BOM NetArch ComputeArch StorageArch Security email different parties Customizations Ad-hoc Redesign -5 chassis to 4 chassis to save $$ -No firewall Ops Admin Rack Elevations Patch Diagrams Physical Layouts 1 week correct cables? "must be "latest & greatest" gear!" FooCorp (Contractor) Box.net + Ops Admin Rack and Stack Elevations .vs Patch Plan .xls -Rack/Cable -Network / ? -Labeling Build spec? Build Lead Net Ops Admin -Net connections -VLANs -Subnets -IP Addressing <<Scriptable>> 3w 2d Generic Low Level Design .xls Ops Admin Interprets Compute and Storage Build Team -Hardware Manager Config/Profile -Prepare OS Install -Power failover testing <<Scriptable>> 2-3d Ops Admin Compute and Storage Build 2w -Setup OpenStack, CEPH -Prepare Build Server with software repository (ubuntu) -Cobbler node, PXE booting -Puppet Master -Reprovisioning 2d via cell net Files and Packages Ubuntu OS Openstack .ISV .IMG rsync scp Puppet Software Environment Server Build Code COI Accumulation Delay Manifests Heira Cobbler yaml Retrofit Jenkins SSD? Customer? Git Dev, Ops Adding Changes Acme Partner Seeding Env. + Services -Reqs -Deliver Schedule -Network -Zoning -Mail Server -Prime Service Catalog -6 VN -Access -Flavors -Tennants -Authorization -Repo Mirror -ID Management System (5d) -LDAP server -2 Factor Auth / Radint -Licenses (SQL Server) -Images -Load Balancer Setup -Monitoring PM (Skipper) Ops Devs A&E -Install HA for each product -Web portal -Databases -A.D. -Prime Catalog 3 weeks Platform Validation Ops Admin -Functionality testing -Boot VMs -Check network -Capacity testing -Synthetic testing Tempest test cases Register Support Contracts for CEPH, Canonical, TAC Punchlist .xls Box.net PM (Lewis) Site specific services and ACLs Weekly Status Meeting Acme Partner PM -Handoff Meeting to Acme Partner -Retrospective Ad-hoc fix push Scrum Fixed in sprint Rally Openstack Bug Dev, Ops QA (SDU) Systems Dev Unit -Testing (destructive, non-destructive) -Restore DB 3-4 weeks Heira Environment Data Defects InfoSec -IDS Infra -Install scanner -Vulnerability scan -3rd party PenTest Account Manager (Bob) 4 months Physical Environment Server Environment Verification Cloud Environment Normalize Standardize Verification Point Verification Point Verification Point Verification Point Verification Point Verification Point Verification Point Embed in the rest of the process!! •Outside-in perspective on testing (“is this thing working?”) •No work output complete without a verification test (code not docs!)
  50. 50. Insert verification points to drive feedback loops Business Need: Customer Capactiy AZ Redundancy Site Build Value Demand Product Manager -Partnerships -Biz Modeling -Hardware Acquisition 6 months "Acme Partner" Capacity -Pick Site (Colo, Acme Partner) -Physical security with InfoSec, Contractors Procure Hardware -Ship to Uranus -Cabling and power plugs 1.5 - 2 months BOM NetArch ComputeArch StorageArch Security email different parties Customizations Ad-hoc Redesign -5 chassis to 4 chassis to save $$ -No firewall Ops Admin Rack Elevations Patch Diagrams Physical Layouts 1 week correct cables? "must be "latest & greatest" gear!" FooCorp (Contractor) Box.net + Ops Admin Rack and Stack Elevations .vs Patch Plan .xls -Rack/Cable -Network / ? -Labeling Build spec? Build Lead Net Ops Admin -Net connections -VLANs -Subnets -IP Addressing <<Scriptable>> 3w 2d Generic Low Level Design .xls Ops Admin Interprets Compute and Storage Build Team -Hardware Manager Config/Profile -Prepare OS Install -Power failover testing <<Scriptable>> 2-3d Ops Admin Compute and Storage Build 2w -Setup OpenStack, CEPH -Prepare Build Server with software repository (ubuntu) -Cobbler node, PXE booting -Puppet Master -Reprovisioning 2d via cell net Files and Packages Ubuntu OS Openstack .ISV .IMG rsync scp Puppet Software Environment Server Build Code COI Accumulation Delay Manifests Heira Cobbler yaml Retrofit Jenkins SSD? Customer? Git Dev, Ops Adding Changes Acme Partner Seeding Env. + Services -Reqs -Deliver Schedule -Network -Zoning -Mail Server -Prime Service Catalog -6 VN -Access -Flavors -Tennants -Authorization -Repo Mirror -ID Management System (5d) -LDAP server -2 Factor Auth / Radint -Licenses (SQL Server) -Images -Load Balancer Setup -Monitoring PM (Skipper) Ops Devs A&E -Install HA for each product -Web portal -Databases -A.D. -Prime Catalog 3 weeks Platform Validation Ops Admin -Functionality testing -Boot VMs -Check network -Capacity testing -Synthetic testing Tempest test cases Register Support Contracts for CEPH, Canonical, TAC Punchlist .xls Box.net PM (Lewis) Site specific services and ACLs Weekly Status Meeting Acme Partner PM -Handoff Meeting to Acme Partner -Retrospective Ad-hoc fix push Scrum Fixed in sprint Rally Openstack Bug Dev, Ops QA (SDU) Systems Dev Unit -Testing (destructive, non-destructive) -Restore DB 3-4 weeks Heira Environment Data Defects InfoSec -IDS Infra -Install scanner -Vulnerability scan -3rd party PenTest Account Manager (Bob) 4 months Physical Environment Server Environment Verification Cloud Environment Normalize Standardize Verification Point Verification Point Verification Point Verification Point Verification Point Verification Point Verification Point Embed in the rest of the process!! •Outside-in perspective on testing (“is this thing working?”) •No work output complete without a verification test (code not docs!) •Start with simple shell scripts (“lingua franca” of ops)
  51. 51. Drive all changes through a SDLC Tests Code Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE
  52. 52. Drive all changes through a SDLC Code Dev Ops * Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE Collaboration Tests
  53. 53. Drive all changes through a SDLC Versioned Release Code Tests Dev Ops * Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE Collaboration
  54. 54. Versioned Release Code Tests Dev Ops * Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE Collaboration Dev Ops * Execute Operations Procedures Drive all changes through a SDLC
  55. 55. Versioned Release Code Tests Dev Ops * Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE Collaboration Dev Ops * Execute Operations Procedures Drive all changes through a SDLC Same People!!
  56. 56. Versioned Release Code Tests Dev Ops * Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo SERVICE Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE Collaboration Dev Ops * Execute Operations Procedures Drive all changes through a SDLC Same People!!
  57. 57. What about cross-cutting concerns? Cross Functional Delivery Team (PO • Dev • Test • SRE) Tests Code Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Packages Environments SOURCE Monitoring QA Security Environments --- Metrics
  58. 58. What about cross-cutting concerns? Cross Functional Delivery Team (PO • Dev • Test • SRE) Tests Code Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Packages Environments SOURCE Monitoring QA Security Environments --- Metrics QA as a Service Security as a Service Metrics as a Service Env. as a Service
  59. 59. What about cross-cutting concerns? Cross Functional Delivery Team (PO • Dev • Test • SRE) Tests Code Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Packages Environments SOURCE pull pull pull pull Monitoring QA Security Environments --- Metrics QA as a Service Security as a Service Metrics as a Service Env. as a Service
  60. 60. Be an internal service provider pull Cross-Cutting Concern X ✓ Standardized offerings ✓ Pulled by users (not pushed) ✓ On-demand and self-service ✓ Implementation knowledge not necessary for normal use ✓ Provider spends their time building service and coaching users X as a Service
  61. 61. Start working like an internal service provider pull X as a Service Cross-Cutting Concern X
  62. 62. Start working like an internal service provider pull X as a Service Cross-Cutting Concern X 1 Define your offerings
  63. 63. Start working like an internal service provider pull X as a Service Cross-Cutting Concern X 1 Define your offerings
  64. 64. Start working like an internal service provider pull X as a Service Cross-Cutting Concern X 1 Define your offerings 2 Tame the tool sprawl
  65. 65. Start working like an internal service provider pull X as a Service Cross-Cutting Concern X 1 Define your offerings 2 Tame the tool sprawl
  66. 66. Start working like an internal service provider pull X as a Service Cross-Cutting Concern X 1 Define your offerings 2 Tame the tool sprawl 3 Setup self-service interfaces
  67. 67. Start working like an internal service provider pull X as a Service Cross-Cutting Concern X 1 Define your offerings 2 Tame the tool sprawl 3 Setup self-service interfaces
  68. 68. Start working like an internal service provider pull X as a Service Cross-Cutting Concern X 1 Define your offerings 2 Tame the tool sprawl 3 Setup self-service interfaces 4 Setup secure access
  69. 69. Start working like an internal service provider pull X as a Service Cross-Cutting Concern X 1 Define your offerings 2 Tame the tool sprawl 3 Setup self-service interfaces 4 Setup secure access
  70. 70. pull X as a Service Cross-Cutting Concern X Start working like an internal service provider Plug: Give Rundeck a try --> rundeck.org 1 Define your offerings 2 Tame the tool sprawl 3 Setup self-service interfaces 4 Setup secure access
  71. 71. What about things that can’t be automated? DevOps
  72. 72. Good rule of thumb: Tickets are for exceptions, not the daily work X X Ticket System ?? X
  73. 73. Good rule of thumb: Tickets are for exceptions, not the daily work Manual request queues lead to... • Bottlenecks • Increased lead times • Reinforces organizational silos • Misinterpretation or omissions X X Ticket System ?? X
  74. 74. How do we mitigate the negative impact of manual request queues? DevOps
  75. 75. Use a work management system like Kanban Up Next Service B Service C Service D Service E Doing Plan it Do it Review it Post Mortem Backlog prioritized by stakeholders Ta s k Task Service A Task Task Task Task Task Emergency - Type 1 Emergency - Type 2 Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task
  76. 76. Use a work management system like Kanban Up Next Service B Service C Service D Service E Doing Plan it Do it Review it Post Mortem Backlog prioritized by stakeholders Ta s k Task Service A Task Task Task Task Task Emergency - Type 1 Emergency - Type 2 Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Only works if you set and enforce: • Service catalog and backlog rules • WIP and SLA per service type • WIP per person
  77. 77. Use a work management system like Kanban Your standardized offerings Up Next Service B Service C Service D Service E Doing Plan it Do it Review it Post Mortem Backlog prioritized by stakeholders Ta s k Task Service A Task Task Task Task Task Emergency - Type 1 Emergency - Type 2 Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Only works if you set and enforce: • Service catalog and backlog rules • WIP and SLA per service type • WIP per person
  78. 78. Use a work management system like Kanban Your standardized offerings Up Next Service B Service C Service D Service E Doing Plan it Do it Review it Post Mortem Backlog prioritized by stakeholders Ta s k Task Service A Task Task Task Task Task Emergency - Type 1 Emergency - Type 2 Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Only works if you set and enforce: • Service catalog and backlog rules • WIP and SLA per service type • WIP per person SLA per service type
  79. 79. Use a work management system like Kanban Your standardized offerings Up Next Service B Service C Service D Service E Doing Plan it Do it Review it Post Mortem Backlog prioritized by stakeholders Ta s k Task Service A Task Task Task Task Task Emergency - Type 1 Emergency - Type 2 Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Only works if you set and enforce: • Service catalog and backlog rules • WIP and SLA per service type • WIP per person SLA per service type Enforce WIP to protect capacity and hit commitments!
  80. 80. Unlimited Environments* (* OK, yes… nothing is ever unlimited)
  81. 81. Unlimited Environments* • Hardware is cheap… people and opportunity costs are expensive (* OK, yes… nothing is ever unlimited)
  82. 82. Unlimited Environments* • Hardware is cheap… people and opportunity costs are expensive • Shared integration environments become choke points (* OK, yes… nothing is ever unlimited)
  83. 83. Unlimited Environments* • Hardware is cheap… people and opportunity costs are expensive • Shared integration environments become choke points • The more environments people have, the more experiments they run (* OK, yes… nothing is ever unlimited)
  84. 84. Unlimited Environments* • Hardware is cheap… people and opportunity costs are expensive • Shared integration environments become choke points • The more environments people have, the more experiments they run • The more production-similar environments people have, the higher the quality of organization (* OK, yes… nothing is ever unlimited)
  85. 85. ..But Security! ...But Compliance! DevOps
  86. 86. Security and Compliance Opportunity Tests Code Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE
  87. 87. Security and Compliance Opportunity Tests Code Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE Design and Code Reviews
  88. 88. Security and Compliance Opportunity Tests Code Source Repo Config Env Spec Run-book Auto-mation Design and Code Reviews CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE Code and Binary Scanning
  89. 89. Security and Compliance Opportunity Tests Code Source Repo Config Env Spec Run-book Auto-mation Design and Code Reviews CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE Code and Binary Scanning “Bake” security tests into your “immune system”
  90. 90. Security and Compliance Opportunity Tests Code Source Repo Config Env Spec Run-book Auto-mation Design and Code Reviews CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE Code and Binary Scanning “Bake” security tests into your “immune system” Component vulnerability and governance
  91. 91. Security and Compliance Opportunity Tests Code Source Repo Config Env Spec Run-book Auto-mation Design and Code Reviews CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE Code and Binary Scanning “Bake” security tests into your “immune system” Component vulnerability and governance Access policy and operational security checks
  92. 92. Security and Compliance Opportunity Tests Code Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE
  93. 93. Security and Compliance Opportunity Tests Code Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE What’s the change?
  94. 94. Security and Compliance Opportunity Tests Code Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE What’s the change? How did you validate the change?
  95. 95. Security and Compliance Opportunity How did you validate the change? Tests Code Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE What’s the change? Where did the change go?
  96. 96. Security and Compliance Opportunity How did you validate the change? Tests Code Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE What’s the change? Where did the change go? Who has access to what environment? Who did what when and where?
  97. 97. Security and Compliance Opportunity How did you validate the change? Tests Code Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console What was executed on the box to make the change? Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE What’s the change? Where did the change go? Who has access to what environment? Who did what when and where?
  98. 98. Security and Compliance Opportunity How did you validate the change? Tests Code Source Repo Config Env Spec Run-book Auto-mation CI Server Package Repo Operations Console What was executed on the box to make the change? Shell Powershell Pre-Production Environments Shell Powershell Production Environment Packages Operations Development SOURCE What’s the change? Where did the change go? Who has access to what environment? Who did what when and where? Change things here Run / control things here
  99. 99. Recap
  100. 100. Recap • Redraw the org to eliminate silos!
  101. 101. Recap • Redraw the org to eliminate silos! • Turn information flow into artifact flow
  102. 102. Recap • Redraw the org to eliminate silos! • Turn information flow into artifact flow • Insert verification points to tighten feedback loops
  103. 103. Recap • Redraw the org to eliminate silos! • Turn information flow into artifact flow • Insert verification points to tighten feedback loops • Drive all changes through a SDLC
  104. 104. Recap • Redraw the org to eliminate silos! • Turn information flow into artifact flow • Insert verification points to tighten feedback loops • Drive all changes through a SDLC • Turn cross-cutting concerns into internal service providers
  105. 105. Recap • Redraw the org to eliminate silos! • Turn information flow into artifact flow • Insert verification points to tighten feedback loops • Drive all changes through a SDLC • Turn cross-cutting concerns into internal service providers • Strive for unlimited environments
  106. 106. Bonus: DevOps Litmus Test
  107. 107. Bonus: DevOps Litmus Test Reduce cycle time AND improve quality?
  108. 108. Bonus: DevOps Litmus Test Reduce cycle time AND improve quality? Eliminate handoffs or reduce the friction of those handoffs that can't be eliminated?
  109. 109. Bonus: DevOps Litmus Test Reduce cycle time AND improve quality? Eliminate handoffs or reduce the friction of those handoffs that can't be eliminated? Eliminate manual information flow and replace with tool-to-tool artifact flow?
  110. 110. Bonus: DevOps Litmus Test Reduce cycle time AND improve quality? Eliminate handoffs or reduce the friction of those handoffs that can't be eliminated? Eliminate manual information flow and replace with tool-to-tool artifact flow? Eliminate manually-fulfilled request queues and other sources of waiting and context switching?
  111. 111. Bonus: DevOps Litmus Test Reduce cycle time AND improve quality? Eliminate handoffs or reduce the friction of those handoffs that can't be eliminated? Eliminate manual information flow and replace with tool-to-tool artifact flow? Eliminate manually-fulfilled request queues and other sources of waiting and context switching? Improve awareness and understanding of how work is flowing of the end-to-end lifecycle?
  112. 112. Bonus: DevOps Litmus Test 1 or more marked “NO”? Then back to the drawing board!
  113. 113. Bonus: DevOps Litmus Test Reduce cycle time AND improve quality? 1 or more marked “NO”? Then back to the drawing board!
  114. 114. Bonus: DevOps Litmus Test Reduce cycle time AND improve quality? Eliminate handoffs or reduce the friction of those handoffs that can't be eliminated? 1 or more marked “NO”? Then back to the drawing board!
  115. 115. Bonus: DevOps Litmus Test Reduce cycle time AND improve quality? Eliminate handoffs or reduce the friction of those handoffs that can't be eliminated? Eliminate manual information flow and replace with tool-to-tool artifact flow? 1 or more marked “NO”? Then back to the drawing board!
  116. 116. Bonus: DevOps Litmus Test Reduce cycle time AND improve quality? Eliminate handoffs or reduce the friction of those handoffs that can't be eliminated? Eliminate manual information flow and replace with tool-to-tool artifact flow? Eliminate manually-fulfilled request queues and other sources of waiting and context switching? 1 or more marked “NO”? Then back to the drawing board!
  117. 117. Bonus: DevOps Litmus Test Reduce cycle time AND improve quality? Eliminate handoffs or reduce the friction of those handoffs that can't be eliminated? Eliminate manual information flow and replace with tool-to-tool artifact flow? Eliminate manually-fulfilled request queues and other sources of waiting and context switching? Improve awareness and understanding of how work is flowing of the end-to-end lifecycle? 1 or more marked “NO”? Then back to the drawing board!
  118. 118. @damonedwards damon@dtosolutions.com

×