Achieving Continuous Visibility Across the DevOps Lifecycle
3 likes1,457 views
The document discusses achieving continuous visibility across the DevOps lifecycle. It argues that local optimizations and lack of integration between tools has led to manual processes that slow down delivery. It promotes the use of integration patterns and infrastructure to provide end-to-end visibility by connecting tools across planning, development, testing and operations. This allows teams to see dependencies, impacts, quality status and automate deployment for less variance and faster delivery.
Achieving Continuous Visibility Across the DevOps Lifecycle
- 1. Achieving Continuous Visibility across the DevOps Lifecycle MIK KERSTEN | Founder & CEO, Tasktop @mik_kersten CARMEN DEARDO | Nationwide Technology Director @carmendeardo SESSION 3268
- 2. AGILE OPTIMIZES THE MIDDLE OF THE VALUE STREAM 2 Wait states due to starvation of prioritized work flow into backlogs Wait states due to contention for downstream environments and manual processes Agile DDT Deploy & Operate Steer Develop & Test Water-SCRUM-Fall SPEED TIME Teams waiting for work due to “discrete” planning processes Delivery slowed down by manual and high ceremony processes High Acceleration during Design, Develop and Acceptance Testing 0
- 3. FOUNDATIONAL MODEL 3 DEVOPS Business Enabling Responsiveness Reduced Lead Time for Changes Monitor Everything Continuous Delivery Automated Infrastructure Continuous Integration Automated Testing Version Control Everything PRACTICES High Trust Innovative Performance Oriented Empowered Associates Reduce Variation High Cooperation CULTURE Continuous Flow & Visibility Lean & Agile Principles Product Centric System Flow Amplify Feedback Loops Continuous Experimentation
- 4. THE HIDDEN FACTORY 4 Project Planning View Development View Release View Bus Portfolio View Project Metrics Path to Production Business Needs Production Implementations Release Metrics
- 5. CURRENT STATE 5 Release Planning Release Management (Development & Test) Deployment Automation Custom BSA RP toolsCustom BSA Rls Planning tools Custom Business Release Planning tools Project & Portfolio Management Custom Release Management Tooling Custom Release Management Tooling Code Moves Test & Production Envs Reports & notifications Other Deploy Tools Build Process Java .NET Mobile • Clarity Used for Project Management and Work Requests • Custom Release Planning Tools and spreadsheets • Tools not Integrated – no Enterprise views • Manual interactions which slow down the process • No automated deployment policies • RTC used for Agile Team Management and not integrated • Disparate views with no model of the delivery work flow or path to production RTC Project Plans & Work Requests
- 6. THE HIDDEN FACTORY 6 Project Planning View Release View Bus Portfolio View Project Metrics Path to Production Business Needs Production Implementations Release Metrics Development View
- 7. EXPOSING THE FACTORY WITH DEVOPS 7 Business Needs Production Implementations DEVOPS Provide Visibility Across the End to End Delivery Value Chain to Expose the Value Stream and Improve Delivery
- 8. DELIVERY VALUE STREAM: HIGH LEVEL 8 BUSINESS WORK REQUEST PROCESS DEMAND MANAGMENT RELEASE PLANNING DESIGN / DEVELOP QUALITY CERTIFIED DEPLOY INVENTORY INITIATIVE/ DC BUILDS
- 9. VALUE STREAM MAP 9 BUILDS DESIGN / DEVELOP QUALITY CERTIFIED DEPLOY IDENTIFY AC SCHEDULE INTO RELEASE END RELEASE PLANNING YES NOOR CREATE PLAN EXECUTE PLAN REVIEW (PDCA) DEPLOY TO TEST ENVIRONMENT EXECUTE TEST APPROVED? CERTIFIED YES ALL CERTS DONE NO DEFECTS YES NO YES NO C N/C C C BUSINESS
- 10. AGILE PROVIDES A WINDOW INTO THE FACTORY 10 Standardize “Work” input (e.g. Business Value, Defects, Operations) Provide impact analysis, Dashboard views and multi- application continuous delivery Provide direct, automated control & traceability over deployment activity. UCR (UrbanCode Release) UCD (UrbanCode Deploy) RTC (Rational Team Concert) Release Dashboard Release Scheduling Deploy
- 11. BUSINESS WORK SOURCE OPERATIONAL WORK SOURCE DEFECTS BUSINESS INITIATIVE A BUSINESS INITIATIVE B AC AC AC OPERATIONAL INITIATIVE B OC OC SYSTEM RELEASE AC AC OC AC AC OC SCM CI IT / ST /PT / UAT CODE STATION BUSINESS VALUE OPERATIONS MONITORING & FEEDBACK TEST RESULTS / PT / SECURITY READY FOR PRODUCTIONDEFECT CONTINUOUS DELIVERY WORKFLOW
- 12. WHY DOES REALITY LOOKING SO DIFFERENT? Best-‐of-‐breed DevOps & Agile tool chains are the norm
- 13. Developers Designers DIFFERENT POINTS OF VIEW ON SOFTWARE DELIVERY Developers see Designers see Managers see Managers
- 14. HETEROGENEITY ACROSS LINES OF BUINSESS
- 15. RESULT: LOCAL OPTIMIZATOINS & MANUAL PROCESSES 15
- 16. WE NEED A NEW KIND OF INFRASTRUCTURE 16 DEVOPS Business Enabling Responsiveness Reduced Lead Time for Changes Monitor Everything Continuous Delivery Automated Infrastructure Continuous Integration Automated Testing Version Control Everything PRACTICES High Trust Innovative Performance Oriented Empowered Associates Reduce Variation High Cooperation CULTURE Continuous Flow & Visibility Lean & Agile Principles Product Centric System Flow Amplify Feedback Loops Continuous Experimentation
- 17. DevOps Integration Agile ITILWaterfall / SAFe Project Requirement User Story Defect Ticket Alert Continuous Integration Continuous Delivery Executives Business Analysts Project Managers Developers IT Operations Support Desk INTEGRATION INFRASTUCTURE FOR DEVOPS
- 19. PATTERN LANGAUGE FOR DEVOPS & AGILE INTEGRATION 19 Integration Infrastructure Integration Patterns Process Frameworks Value Stream Lifecycle Tools
- 20. PROCESS FRAMEWORKS: PMBOK + SAFe + DEVOPS + ITIL 20
- 21. Pattern Applies to Example Defect Unification • Agile development • Waterfall development • Separate Dev & QA teams & tools Requirements Traceability • Agile development • Traditional Requirements Management • Traditional Quality Management • Dev and Agile PM using different tools Agile Plan Orchestration • Traditional or Agile development • Separate PMO organization • Separate Agile Dev and PPM tools Service Desk Escalation • DevOps deployment • Agile or waterfall development • Support organization separate from the development teams Supply Chain Integration • In-‐house requirements and QA mgmt • Development outsourcing • QA outsourcing Dev QA BA Agile PM QA QA .. ALM PMO Agile 2 ITSM Dev QA ITSM Defect Ticket Dev Epic QA 1 Dev .. Dev 1 Agile 1 Rqrmnt Defect INTEGRATION PATTERNS
- 22. AGILE INTEGRATION PATTERNS 22 CA Clarity Atlassian JIRA HP ALM IBM DNG Microsoft TFS SLI Pattern #1: Executive Planning to Project Definition SLI Pattern #3: Supply Chain ConnectionsSLI Pattern #2: Project Definition to Execution SLI Pattern #4: Requirements to Test Visibility SLI Pattern #5: Defect Unification SLIPattern#6:ResourceAllocation IBM RTC Service Now
- 23. Investment Theme Business Epics Program Prism Team Prism Features SLI Pattern #2: Resource Allocation Features Business Epics Work Logs Tasks User Stories Portfolio Prism Timesheets Developer, Project Manager Work Logs CC FROM PMO TO DEVOPS
- 24. INTEGRATION PATTERNS • Project Portfolio Management – Time tracking propagation – Agile plan orchestration • Requirements Management – Requirement traceability • Enterprise Agile – Backlog unification – Build traceability • Development – Build automation – Change set traceability – Code review traceability • Quality Management – Defect unification – Test traceability • Service Management – Incident escalation – Known issue propagation – Feature request traceability • Security – Vulnerability escalation • Operations – Deployment automation – Alert escalation
- 25. CONNECTING THE VALUE STREAM 25 CA PPM Requirements Traceability PMBOK SAFe DevOps Continuous Visiblity DNG RTC HP QC uDeploy Service Now Process Frameworks Integration Patterns Integration Technologies Value stream ITIL Synchronization Linking OSLC Web Hooks Defect Unification … Lifecycle Tools
- 26. VALUE STREAM FLOW 26 JIRA HP QC ALM Bluemix BMC Remedy CA CLARITY INVESTMENT THEMES BUSINESS EPIC $ BUSINESS EPIC IBM DNG/RRC Feature USER STORY USER STORY DEFECT DEFECT TEST CASE USER STORY BUSINESS EPIC Feature Feature BUSINESS EPIC Feature Feature IBM RTC Feature USER STORY USER STORY DEFECT DEFECT TEST CASE DEFECT USER STORY USER STORY DEFECT Test case link Test case link Test case link FEATURE INCIDENT PROBLEM Feature Feature Feature Feature USER STORY USER STORY USER STORY USER STORY Feature
- 28. PUTTING IT ALL TOGETHER 28
- 30. PATTERN LANGAUGE FOR DEVOPS & AGILE INTEGRATION 30 Integration Infrastructure Integration Patterns Process Frameworks Value Stream Lifecycle Tools
- 31. VISABILITY VIA REAL TIME INFORMATION 31 UrbanCode Integration Tasktop UrbanCode Plug-in Schedule for Release Monitor Release Gate Environments Orchestrate Deployment Automate Deployment PRODUCT MANAGER Work Request QA Tasktop ✔ DELIVERY OPPORTUNITIES ENTERPRISEAND SYSTEM VIEWS DEPENDENCIESAND IMPACTS QUALITY, SECURITY & TEST STATUS AUTOMATION DEPLOYMENT STATUS MORE AUTOMATION LESS VARIANCE RTC UCR UCD
- 32. 32
- 33. “YOU HAVE TO THINK HORIZONTALLY.” 32
- 34. “LOCAL OPTIMIZATION IS THE ENEMY OF LEAN DELIVERY.” 33
- 35. “AUTOMATION REQUIRES PATTERNS, PATTERNS REQUIRES ELIMINATING VARIANCE.” 34
- 36. “TECHNOLOGY IS THE FUN PART, CULTURE IS THE CHALLENGE.” 36
- 37. “HARD TO MANAGE WHAT YOU CAN'T SEE …OR MEASURE.” 35
- 38. Achieving Continuous Visibility across the DevOps Lifecycle MIK KERSTEN | CEO, Tasktop @mik_kersten CARMEN DEARDO | Nationwide Technology Director @carmendeardo SESSION 3268