Welcome. Mapping the BA s Stakeholders in a DevOps Style Workflow

Transcription

1 Welcome. Mapping the BA s Stakeholders in a DevOps Style Workflow Chris Knotts, PMP ASPE Training and Techtown Training

2 I ll discuss A few examples of generic stakeholders as described in the BABOK Guide A little about DevOps Applying the DevOps context to stakeholder roles Pain points and enablers of roles associated with successful DevOps style work

3 A few assumptions for the hour Roles are associated usually with software projects, & always with overall IT workflow DevOps is not a codified set of principles Chris is not a BA BABOK Guide 2.0 vs ?

4 BABOK Guide Generic Stakeholder Business Analyst Customer Domain SME Implementation SME Operational Support Project Manager Supplier Tester Regulator Sponsor Examples and Alternate Roles Business Systems Analyst, Systems Analyst, Process Analyst, Consultant, Product Owner Segmented by market, geography, industry Broken out by organizational unit, job role Project Librarian, Change Manager, Configuration Manager, Solution Architect, Developer, DBA, Information Architect, Usability Analyst, Trainer, Organizational Change Consultant Help Desk, Network Technicians, Release Manager Scrum Master, Team Leader Providers, Consultants, etc. Quality Assurance Analyst Government, Regulatory Bodies, Auditors Managers, Executives, Product Managers, Process Owners

5 Examples of generic stakeholders Implementation SMEs Developers/Software Engineers Organizational Change Managers System Architects Usability Professionals Project Manager Testers Regulators Sponsors Suppliers

6 Generic Stakeholder Business Analyst Customer Domain SME Implementation SME Operational Support Project Manager Supplier Tester Regulator Sponsor Examples and Alternate Roles BABOK Guide Business Systems Analyst, Systems Analyst, Process Analyst, Consultant, Product Owner Segmented by market, geography, industry Broken out by organizational unit, job role Project Librarian, Change Manager, Configuration Manager, Solution Architect, Developer, DBA, Information Architect, Usability Analyst, Trainer, Organizational Change Consultant Help Desk, Network Technicians, Release Manager Scrum Master, Team Leader Providers, Consultants, etc. Quality Assurance Analyst Government, Regulatory Bodies, Auditors Managers, Executives, Product Managers, Process Owners

7 Five of the most important roles impacted by DevOps trends Software & Enterprise Architects Software Developers IT Operations & Support Software Testers Change Managers Anyone with a stake in application outcomes!

8 A simplified look at Consolidata s enterprise Change Management Application Development teams IT Operations, Production Environments, Support Business Customer s S e c u r I t y, G o v e r n a n c e S e c u r I t y, G o v e r n a n c e

9 Dev Ops

10 Opposing missions Development teams rewarded for creating value when software is deployed Operations and infrastructure admin teams penalized for downtime

11 The triumphant Agile team! Success!! Working software or feature DELIVERED Sprints Idea

12 Opposing missions The triumphant Agile team! IT Operations Deploy & Support Operation & Systems Data Security

13 The business! (different departments, needs, stakeholders etc.) The triumphant Agile team! IT Operations Deploy & Support Operation & Systems Data Security

14 The business! (different departments, needs, stakeholders etc.) The triumphant Agile team! IT Operations!! Deploy & Support Operation & Systems Data Security Customers / end users!!

15 What are organizations trying to achieve with DevOps type practices?

16 Continuous Delivery: Smaller batches of software work, more frequently, with less planning and more adaptability

17 The deployment pipeline concept Source: Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation

18 Software & System Architects A few typical challenges: Legacy Technology Mission Criticality Technical Debt DevOps-associated Enablers: Service Oriented Architecture Component-Centric Design Loose Coupling of Components Simulators and Emulators

19 Software Developers A few typical challenges: Definition of done Agile Practices that end with dev teams Long, or absent feedback loops Measurement of enterprise value DevOps-associated Enablers: Agile Practices but they must scale! Deploy it yourself with operational support Treating infrastructure as code Continuous delivery of software

20 IT Operations & Support A few typical challenges: Blame from all sides Most enterprises engineered to penalize Not responsible for most defects & failures DevOps-associated Enablers: Peer-driven change management Inclusion & collaboration early in projects Technology enablers (automation tools, etc.)

21 Software Testers A few typical challenges: Accurate testing Fast enough testing People ignoring test results DevOps-associated Enablers: Designing tests as part of the product Component oriented testing Using tests to automate deployment Making quality everyone s responsibility

22 Change Managers A few typical challenges: Imposed change management Slow delivery of value Lack of leadership support Inefficiencies arising from fearful culture DevOps-associated Enablers: Peer-driven change management Engineering change as the product Leadership-driven change

23 Application Delivery & Cost of Defects 50% of defects introduced here

24 References & recommended reading Continuous Delivery, Jez Humble and David Farley Leading the Transformation: Applying Agile and DevOps Principles at Scale, Gary Gruver and Tommy Mouser The Phoenix Project: A Novel About IT, DevOps & Helping Your Business Win, Gene Kim, George Spafford, Kevin Behr

25 Thank you!