assessment approach - clearly agile · i. present our assessment approach 1. alignment to...

1
Because DevOps is passé Capture findings and opinions of culture, engineering practices, quality, and processes based on observations and elicitations from across the organization. Step 1: Collaborative Expectation Setting Step 3: Gather Input Step 4: Report Out Step 2: Identify Teams and Individuals Collaborative Preparation I. Present our assessment approach 1. Alignment to Agile/DevOps Principles 2. Engineering practices and tools 3. Processes / artifacts / enablers 4. Delivery / Deployment throughput 5. Infrastructure 6. Quality / Security 7. Supportive governance framework II. Solicit stakeholder input 1. Identify and prioritize desired outcomes 2. Build consensus on level of support 3. Set timeline 4. Adjust the assessment approach Interactive Interviews Observations Surveys Documents Artifacts Policies Practices Procedures Standards Approaches Agile Defect Management Delivery / Deployment Development DevOps Management Planning Tools Build Development DevOps Integration Package Testing / Quality Outcomes Measures Metrics 1. Alignment to Agile/DevOps Principles 2. Engineering practices and tools 3. Processes / artifacts / enablers 4. Delivery / Deployment throughput 5. Infrastructure 6. Quality / Security 7. Supportive governance framework A. Reports & Findings (summary, detail) B. Potential Gaps C. Perceived Risks/ Issues D. Suggestions for Improvement E. Suggestions for Next Steps Assessment Approach I. Leadership (CIO, CTO, etc.) II. Management (Directors, Branch Heads, etc.) III. Stakeholders (internal, external, indirect) IV. Delivery Teams (Waterfall, Scrum, XP, Kanban, Lean, etc.) V. Support Teams (operations, security, data, etc.) THE PLAN

Upload: others

Post on 13-May-2020

4 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Assessment Approach - Clearly Agile · I. Present our assessment approach 1. Alignment to Agile/DevOps Principles 2. Engineering practices and tools 3. Processes / artifacts / enablers

Because DevOps is passéCapture findings and opinions of culture, engineering practices, quality, and processes based on observations and elicitations from across the organization.

Step 1: Collaborative Expectation Setting

Step 3: Gather Input

Step 4: Report Out

Step 2: Identify Teams and Individuals

Collaborative PreparationI. Present our assessment approach

1. Alignment to Agile/DevOps Principles 2. Engineering practices and tools3. Processes / artifacts / enablers4. Delivery / Deployment throughput5. Infrastructure6. Quality / Security7. Supportive governance framework

II. Solicit stakeholder input1. Identify and prioritize desired outcomes2. Build consensus on level of support3. Set timeline4. Adjust the assessment approach

InteractiveInterviews

ObservationsSurveys

DocumentsArtifactsPolicies

PracticesProceduresStandards

ApproachesAgile

Defect ManagementDelivery / Deployment

DevelopmentDevOps

ManagementPlanning

ToolsBuild

DevelopmentDevOps

IntegrationPackage

Testing / Quality

OutcomesMeasures

Metrics

1. Alignment to Agile/DevOps Principles 2. Engineering practices and tools3. Processes / artifacts / enablers4. Delivery / Deployment throughput5. Infrastructure6. Quality / Security7. Supportive governance framework

A.Reports & Findings

(summary, detail)

B.Potential

Gaps

C.Perceived

Risks/ IssuesD.

Suggestions for

Improvement

E.Suggestions

for Next Steps

Assessment Approach

I. Leadership (CIO, CTO, etc.)II. Management (Directors, Branch Heads, etc.)III. Stakeholders (internal, external, indirect)

IV. Delivery Teams (Waterfall, Scrum, XP, Kanban, Lean, etc.)V. Support Teams (operations, security, data, etc.)

T H E P L A N