COACHING CV — Gavin Dick

Location: South Africa
Email: proactive.projects@gmail.com
Phone: +27 83 509 3303

Professional Summary

With a background in complex project delivery and years of coaching training, I bring a rare combination:

Strategic clarity
Deep questioning
Real-world experience under pressure

My background:
• 20+ years in project delivery and high-risk environments
• Led complex initiatives across multiple countries
• Experienced career disruption, rejection, and financial pressure firsthand

Coaching Credentials & Education

Coach Training & Leadership Development Programme — Aimed at international standards (COMENSA & ICF)
Training in Leadership & Emotional Intelligence coaching frameworks
Certification guidance aligned with COMENSA, ICF Global competencies

Executive and Management Coach

Professional Coaching Experience

Founder & Lead Trainer — Level123 Coaching

Designed and training a 20‑week immersive professional coaching education programme covering core competencies, advanced coaching models, neuroscience of change, somatic presence, and advanced questioning.
Supervised coaches through competency progression towards COMENSA & ICF Accreditation.
Developed curriculum modules including:
- Active Listening & Powerful Questions
- Psychological Safety & Trust Building
- Emotional Intelligence & Somatic Awareness
- Ethics, Coaching Presence & Identity Work
- Goal Setting, Patterns & Systems Thinking
- Team Coaching Foundations
- Trauma‑aware practice and referral boundaries

Executive Coaching & Individual Practice

Support professionals in leadership presence, emotional regulation, and identity transformation.
Help clients develop emotional intelligence, mental fitness, and somatic awareness.
Mentor coaches on building consistent, repeatable breakthrough coaching styles.
Focus on ethical, impactful, high‑integrity coaching aligned with international frameworks.

Coaching Specialisations

Emotional Intelligence Development
Training leaders and coaches to identify, regulate, and harness emotional states for performance.

Transformational Leadership Development
Guiding clients from habitual responses to identity‑level change.

Executive & Leadership Coaching
Improving team dynamics, psychological safety, and strategic presence.

Positive Psychology & Mental Fitness
Focusing on mental saboteurs, Sage mindset, resilience, and well‑being exercises.

Coach Training & Mentor Coaching
Supporting emerging coaches through international competency standards and practical integration.

Core Coaching Competencies

Active Listening & Powerful Questioning
Reflective Practice & Emotional Awareness
Somatic Presence & Regulation
Psychological Safety & Trust Building
Ethics & Professional Standards
Systems Thinking in Coaching
Team & Group Dynamics
Advanced Framework Integration (e.g., neuroscience in change)

Approach & Philosophy

My coaching style is integrative, client‑centric, and somatically informed. I combines neuroscience principles, developmental psychology, emotional intelligence frameworks, and identity coaching to help clients move beyond surface‑level behavior change into lasting transformation.

I emphasise ethical practice and measurable outcomes, aiming to empower clients to lead with authenticity, accountability, and emotional maturity.

Professional Impact & Outcomes

Coaches equipped to achieve COMENSA & ICF credentials
Leaders able to manage stress, emotional responses, and team coherence
Increased client self‑awareness, confidence, and strategic action
Sustainable coaching practices built with ethical standards
Measurable improvement in coaching presence and client breakthroughs

Selected Topics Informing My Coaching

Emotional Intelligence & Regulation
Neuroscience of Coaching Change
Identity & Pattern Transformation
Psychological Safety in Teams
Coaching Ethics & Professional Standards
Systems & Cultural Intelligence
Group & Team Coaching Modalities

Vision

To develop a community of ethically grounded, aware coaches and leaders who are capable of creating deep transformation in individuals, teams, and organisations worldwide.

Agile & Delivery Skills

Agile coaching
Scrum framework expertise
Kanban methodology
Lean principles
Disciplined Agile Delivery (DAD)
Extreme Programming (XP)
Iteration/Sprint planning
Backlog refinement
Retrospectives facilitation
Agile ceremonies facilitation
Agile maturity assessments
Continuous improvement practices
Delivery management
Agile metrics & reporting
Risk identification and escalation
Dependency management
Workflow optimization
Value stream thinking
Team velocity tracking
Agile transformation support

Coaching & Facilitation Skills

Team coaching
One-on-one coaching
Group facilitation
Conflict resolution
Active listening
Powerful questioning
Behavioural feedback
Stakeholder facilitation
Workshop facilitation
Decision-making facilitation
Psychological safety creation
Change facilitation
Mentoring
Consensus building
Team dynamics analysis

Leadership & Interpersonal Skills

Servant leadership
Emotional intelligence
Influencing without authority
Cross-functional collaboration
Relationship building
Stakeholder management
Communication skills
Presentation skills
Negotiation skills
Empathy
Adaptability
Diplomacy
Accountability mindset
Resilience
Trust building

Training & Enablement Skills

Agile training delivery
Adult learning principles
Coaching workshop design
Knowledge sharing
Learning program facilitation
Upskilling teams
Documentation skills
Confluence knowledge management
Curriculum development
Facilitation of onboarding

Analytical & Strategic Skills

Problem-solving
Systems thinking
Strategic thinking
Process analysis
Root cause analysis
Data-driven decision making
Performance analysis
Organisational change awareness
Continuous improvement strategy
Business agility understanding

Technical / Tooling Knowledge

Jira
Confluence
Agile dashboards
Kanban boards
Scrum tools
Reporting tools
Collaboration platforms
DevOps awareness
Software development lifecycle (SDLC)
Product delivery lifecycle

Mindset & Cultural Attributes

Agile mindset
Growth mindset
Customer-centric thinking
Transparency
Collaboration orientation
Learning orientation
Innovation mindset
Adaptability to change
Ownership mentality
Continuous learning

Valuable Certifications

Certified ScrumMaster (CSM)
Professional Scrum Master (PSM)
PMI-ACP
Disciplined Agile Scrum Master (DASM)
Disciplined Agile Coach (DAC)
SAFe Agilist / SAFe Scrum Master
ICAgile Coaching certifications
Lean Six Sigma

I am able to blend the following roles:

Agile Coach
Scrum Master
Change Manager
Facilitator
Trainer
Delivery Enabler
Organisational Transformation Partner

I combine:

Agile delivery experience
Coaching/facilitation capability
Stakeholder influence
Organisational change experience
Strong communication and leadership presence

Agile Coach | Delivery Lead | Agile Transformation Specialist

Experienced Agile Coach and Delivery Leader with over 20 years of experience leading enterprise delivery, coaching cross-functional teams, and driving agile transformation initiatives across complex environments. Proven ability to embed agile principles, values, and mindset at team, leadership, and organisational levels while improving collaboration, transparency, predictability, and customer-focused delivery outcomes.

Strong background in Agile coaching, Disciplined Agile Delivery (DAD), Scrum, Kanban, Lean, and enterprise delivery leadership. Skilled in facilitating organisational change, developing agile maturity roadmaps, coaching leaders and teams, and implementing sustainable high-performance delivery systems.

Passionate about continuous improvement, leadership development, mentoring, coaching, and enabling teams to deliver value effectively and sustainably.

Core Competencies

Agile Coaching & Transformation
Disciplined Agile Delivery (DAD)
Scrum & Kanban Implementation
Agile Maturity Assessments
Lean & Continuous Improvement
Cross-Functional Team Leadership
Stakeholder Engagement & Alignment
Retrospectives & Facilitation
Delivery Metrics & Reporting
Risk & Dependency Management
Team Dynamics & Conflict Resolution
Agile Training & Upskilling
Product Delivery Optimisation
Organisational Change Enablement
Coaching & Mentoring
Confluence & Jira Administration
Leadership Coaching
Scaled Agile Coordination
Scrum of Scrums Facilitation
Flow & WIP Optimisation

Professional Experience

Agile Coach / Delivery Lead

Consulting & Contracting Roles | South Africa
2018 – Present

Key Responsibilities & Achievements

Led agile adoption and continuous improvement initiatives across multiple business units, embedding agile ways of working and improving delivery effectiveness.
Coached teams and leaders in Disciplined Agile Delivery (DAD), Scrum, Kanban, Lean, and Agile best practices.
Facilitated agile ceremonies including sprint planning, backlog refinement, stand-ups, retrospectives, showcases, and cross-functional workshops.
Developed and implemented agile maturity improvement plans in partnership with leadership and delivery stakeholders.
Built strong strategic relationships across Product, Technology, Operations, Marketing, and Executive leadership teams to improve collaboration and alignment.
Delivered Agile and DAD training workshops for new and existing team members, enabling consistent understanding and adoption of frameworks and practices.
Tracked and reported delivery metrics including velocity, cycle time, throughput, lead time, predictability, and team health indicators.
Facilitated conflict resolution, decision-making workshops, and retrospective sessions to improve team effectiveness and collaboration.
Identified and escalated delivery risks, dependencies, and organisational impediments impacting performance and delivery outcomes.
Introduced scalable coordination practices including Scrum of Scrums and Kanban flow management across multiple teams.
Promoted continuous improvement cultures through feedback loops, coaching interventions, and systemic process optimisation.
Shared agile best practices and delivery insights through Confluence documentation, internal communities, and knowledge-sharing sessions.
Participated in agile communities, Lean Coffee sessions, and industry forums to stay current with emerging agile trends and practices.

Key Outcomes

Improved delivery predictability and reduced delivery bottlenecks across multiple cross-functional teams.
Increased agile maturity and collaboration within enterprise delivery environments.
Reduced dependency-related delays through improved flow management and stakeholder alignment.
Strengthened team engagement, transparency, and accountability through coaching and facilitation practices.

Senior Project Manager / Agile Delivery Manager

South Africa
2012 – 2018

Key Responsibilities & Achievements

Managed enterprise digital and commerce delivery initiatives within high-pressure retail and eCommerce environments.
Successfully led the SAP Hybris to Commerce Cloud upgrade involving distributed teams across Romania, Italy, India, and South Africa.
Introduced agile delivery practices to improve collaboration, transparency, and release predictability.
Coordinated cross-functional delivery teams including developers, QA, product owners, architects, and business stakeholders.
Managed complex delivery dependencies, vendor relationships, timelines, risks, and stakeholder communications.
Facilitated delivery planning sessions, retrospectives, risk workshops, and executive reporting forums.
Improved collaboration between offshore and local delivery teams through structured agile ceremonies and alignment practices.
Worked closely with Marketing Product Owners to prioritise backlogs and align delivery with customer and business needs.

Key Outcomes

Reduced downtime and delivery risk during critical platform upgrades.
Improved delivery coordination across globally distributed teams.
Enhanced stakeholder confidence through transparent reporting and improved delivery governance.

Earlier Career

IT Project Manager / Delivery Consultant

Various Contracting Roles | South Africa
2000 – 2012

Delivered technology and business transformation initiatives across multiple industries.
Managed complex project lifecycles involving infrastructure, software, integration, and operational change.
Developed strong stakeholder management, governance, facilitation, and leadership capabilities.
Led teams through high-risk and high-dependency delivery environments.

Certifications & Training

Professional Scrum & Agile Practices Training
Disciplined Agile Delivery (DAD) Exposure & Coaching Experience
Agile Leadership & Facilitation Training
Coaching & Transformation Training
Project Management & Delivery Leadership Training

Tools & Technologies

Jira
Confluence
Azure DevOps
Miro
Trello
SAP Hybris / Commerce Cloud
Microsoft Teams
Slack

Leadership & Coaching Strengths

Creating psychologically safe team environments
Driving organisational alignment and collaboration
Coaching leaders through agile transformation
Facilitating constructive feedback and continuous learning
Influencing without authority across complex organisations
Building sustainable delivery cultures

Professional Development & Community Participation

Active participant in Agile communities, Lean Coffee forums, and coaching discussions.
Continuously research and apply emerging agile practices, delivery optimisation techniques, and organisational coaching approaches.
Passionate about mentoring, coaching, and enabling growth in individuals and teams.

Software Development Lifecycle (SDLC)

The Software Development Lifecycle (SDLC) is a structured process used to plan, build, test, deploy, and maintain software systems efficiently and predictably.

It helps organisations:

Reduce risk
Improve quality
Control cost and timelines
Deliver software that meets customer and business needs

Main Phases of the SDLC

1. Requirements Gathering & Analysis

Understanding:

Business needs
User requirements
Functional and non-functional requirements
Risks and constraints

Activities

Stakeholder workshops
User stories
Business analysis
Process mapping
Requirement documentation

Outputs

Product backlog
Business requirements
Acceptance criteria

2. Planning

Defining:

Scope
Timeline
Resources
Risks
Delivery approach

Activities

Estimation
Sprint planning
Release planning
Roadmap creation
Risk assessment

Outputs

Delivery plan
Sprint roadmap
Capacity plan

3. System Design

Designing:

Architecture
Databases
UI/UX
APIs
Security structures

Activities

Technical architecture
Wireframes
Solution design
Infrastructure planning

Outputs

Architecture diagrams
Technical specifications
UI designs

4. Development

Building the software.

Activities

Coding
Pair programming
Code reviews
Unit testing
Version control management

Common Practices

Scrum
Kanban
CI/CD
Test-driven development (TDD)

5. Testing

Ensuring the software works correctly.

Types of Testing

Unit Testing
Integration Testing
System Testing
User Acceptance Testing (UAT)
Regression Testing
Performance Testing
Security Testing

Goal

Find defects early and improve quality.

6. Deployment

Releasing the software into production.

Activities

Production deployment
Release management
Change management
Rollback planning

Modern Approaches

Continuous Delivery
Continuous Deployment
DevOps pipelines

7. Maintenance & Support

Ongoing improvement after release.

Activities

Bug fixes
Enhancements
Monitoring
Incident management
Performance optimisation

Traditional vs Agile SDLC

Traditional (Waterfall)

Agile

Sequential phases

Iterative delivery

Big upfront planning

Adaptive planning

Late testing

Continuous testing

Fixed scope

Flexible scope

Long release cycles

Frequent releases

Heavy documentation

Working software focus

Agile SDLC Flow

In Agile environments, SDLC happens continuously in short cycles.

Typical flow:

Backlog refinement
Sprint planning
Development
Testing
Review/demo
Retrospective
Release

Then repeat.

Role of an Agile Coach in SDLC

An Agile Coach helps:

Improve collaboration across SDLC stages
Remove bottlenecks
Improve flow efficiency
Embed Agile principles
Improve delivery predictability
Strengthen feedback loops
Increase quality and customer focus

Common SDLC Methodologies

Waterfall

Linear sequential approach.

Agile

Iterative and adaptive delivery.

Scrum

Sprint-based Agile framework.

Kanban

Flow-based work management system.

Lean

Focus on waste reduction and value flow.

DevOps

Combines development and operations for faster, reliable delivery.

Disciplined Agile Delivery (DAD)

Hybrid toolkit combining multiple Agile and Lean approaches.

Disciplined Agile Delivery

Important SDLC Concepts

CI/CD

Continuous Integration / Continuous Deployment.

Technical Debt

Future cost caused by shortcuts in development.

Definition of Done (DoD)

Agreed quality standard before work is considered complete.

WIP Limits

Restricting simultaneous work to improve flow.

Lead Time

Time from request to delivery.

Cycle Time

Time actively spent working on an item.

SDLC Metrics Commonly Tracked

Velocity
Throughput
Lead Time
Cycle Time
Defect Rate
Deployment Frequency
Escaped Defects
Team Happiness
Predictability
Customer Satisfaction

Modern SDLC Trends

DevSecOps
AI-assisted development
Platform engineering
Shift-left testing
Product operating models
Continuous discovery
Cloud-native development
Value stream management

Disciplined Agile Delivery (DAD)

Disciplined Agile Delivery (DAD) is a hybrid Agile framework designed to help organisations deliver solutions in a practical, enterprise-aware way.

Unlike frameworks that prescribe a single method, DAD takes a:

“Choose your WoW (Way of Working)” approach.

It combines practices from multiple methodologies and helps teams decide:

Which practices work best
In which context
At what level of organisational maturity

Core Idea of DAD

DAD recognises that:

One Agile framework does not fit every situation
Enterprises are complex
Teams need flexibility
Delivery extends beyond just software development

DAD therefore provides:

Guidance
Decision frameworks
Process goals
Toolkits of practices

Rather than rigid rules.

Methodologies Combined in DAD

DAD pulls techniques from:

Framework

What DAD Uses

Scrum

Iterations, ceremonies, roles

Kanban

Flow, WIP limits, visualisation

Lean

Waste reduction, value optimisation

Extreme Programming (XP)

Engineering practices, TDD, CI

Agile Modeling

Lightweight modelling

DevOps

Deployment & operational integration

SAFe

Enterprise coordination concepts

Unified Process

Governance and lifecycle thinking

Why DAD Exists

Traditional Agile frameworks often focus mainly on:

Development teams
Sprint execution
Team-level agility

DAD expands beyond that to include:

Architecture
Governance
Security
Compliance
Enterprise realities
Operations
Stakeholder coordination
End-to-end delivery

DAD Lifecycle

DAD extends Agile beyond simple sprint cycles.

1. Inception

Lightweight planning and setup.

Activities:

Vision alignment
Team formation
Architecture planning
Initial backlog
Risk identification

2. Construction

Iterative solution development.

Activities:

Development
Testing
Refinement
Reviews
Continuous integration

3. Transition

Preparing for production release.

Activities:

Deployment
User readiness
Final testing
Operational handover
Production support readiness

4. Ongoing Improvement

Continuous optimisation after release.

Activities:

Metrics analysis
Retrospectives
Process refinement
Feedback incorporation

Key Principles of DAD

1. People First

Teams and collaboration matter more than process rigidity.

2. Pragmatism

Use what works in your context.

3. Enterprise Awareness

Consider organisational realities:

Governance
Compliance
Dependencies
Funding
Security

4. Continuous Improvement

Always refine delivery systems and practices.

5. Context Counts

Different teams need different approaches.

6. Choice is Good

Multiple valid ways exist to solve problems.

Roles in DAD

DAD roles extend beyond Scrum roles.

Primary Roles

Team Lead (similar to Scrum Master)
Product Owner
Architecture Owner
Team Members
Stakeholders

Supporting Roles

Specialists
Domain experts
Independent testers
Integrators
Portfolio managers

DAD vs Scrum

Scrum

DAD

Team-focused

Enterprise-aware

Prescriptive

Hybrid/adaptive

Simple framework

Process decision toolkit

Mainly development

Full delivery lifecycle

Limited governance guidance

Governance integrated

Fixed roles

Flexible roles

DAD vs SAFe

DAD

SAFe

Flexible toolkit

Structured scaling framework

Lightweight governance

Heavier governance

Team chooses WoW

Standardised structure

Adaptive

More prescriptive

What an Agile Coach Does in DAD

An Agile Coach using DAD:

Helps teams choose appropriate practices
Coaches leaders on organisational agility
Improves flow and collaboration
Facilitates retrospectives and learning
Aligns governance with agility
Removes delivery bottlenecks
Improves end-to-end value delivery

Typical DAD Practices

Scrum Practices

Sprint planning
Daily stand-ups
Reviews
Retrospectives

Kanban Practices

WIP limits
Flow visualisation
Throughput optimisation

Lean Practices

Waste reduction
Continuous learning
Value stream focus

XP Practices

Pair programming
Test-driven development
Continuous integration

Benefits of DAD

Flexible and adaptable
Better enterprise fit
Strong governance support
Improves delivery maturity
Encourages continuous learning
Supports scaling across teams

Challenges of DAD

More complex than Scrum
Requires experienced coaching
Can overwhelm immature teams
Needs strong leadership support
Harder to standardise

Where DAD Works Best

DAD is especially effective in:

Large enterprises
Regulated environments
Complex delivery ecosystems
Organisations with mixed delivery styles
Teams needing governance plus agility

Common DAD Metrics

Cycle time
Lead time
Delivery predictability
Escaped defects
Throughput
Team health
Customer satisfaction
Deployment frequency

Important DAD Concept

“Choose Your WoW”

(Way of Working)

This is the central philosophy of DAD:

Teams intentionally choose practices based on context, maturity, and goals instead of blindly following a framework.

CI/CD

CI/CD stands for:

CI = Continuous Integration
CD = Continuous Delivery or Continuous Deployment

It is a modern software engineering and DevOps practice that helps teams deliver software:

Faster
More reliably
With fewer defects
In smaller, safer increments

1. Continuous Integration (CI)

Continuous Integration means developers:

Frequently merge code into a shared repository
Automatically build and test code changes

The goal is to:

Detect issues early
Reduce integration problems
Keep software in a deployable state

Typical CI Flow

Developer:

Writes code
Commits code to repository (e.g., Git)
Automated pipeline runs:
- Build
- Unit tests
- Static code analysis
- Security checks

If something fails:

Team fixes it immediately

CI Principles

Small frequent commits
Automated testing
Fast feedback
Shared codebase
Build automation

2. Continuous Delivery (CD)

Continuous Delivery means:

Software is always ready for release
Deployments are automated
Release decisions can happen anytime

The system automatically:

Builds
Tests
Packages
Prepares software for production

But:

A human usually approves the final release.

3. Continuous Deployment

Continuous Deployment goes one step further.

If all automated tests pass:

Software deploys automatically to production
No manual approval required

CI vs Continuous Delivery vs Continuous Deployment

Practice

Meaning

Continuous Integration

Automatically build & test code

Continuous Delivery

Software always releasable

Continuous Deployment

Automatic production releases

CI/CD Pipeline

A pipeline is the automated workflow that moves code from development to production.

Typical pipeline:

Code Commit

↓

Build

↓

Unit Tests

↓

Integration Tests

↓

Security Scans

↓

Artifact Packaging

↓

Deploy to Test

↓

User Acceptance Testing

↓

Deploy to Production

Common CI/CD Tools

Source Control

Git
GitHub
GitLab
Bitbucket

Build & Pipeline Tools

Jenkins
GitHub Actions
GitLab CI/CD
Azure DevOps

Container & Deployment

Docker
Kubernetes

Testing Tools

Selenium
JUnit
Cypress

Benefits of CI/CD

Faster Delivery

Smaller releases happen more often.

Reduced Risk

Smaller changes are easier to test and rollback.

Better Quality

Automated testing catches defects earlier.

Faster Feedback

Developers know quickly if something breaks.

Improved Collaboration

Teams integrate continuously instead of working in silos.

Agile + CI/CD

CI/CD strongly supports Agile principles because it enables:

Fast feedback loops
Incremental delivery
Continuous improvement
Frequent customer value delivery

Without CI/CD:

Agile teams often struggle with slow releases
Testing bottlenecks
Manual deployment risk

DevOps Relationship

CI/CD is a core DevOps capability.

DevOps

DevOps aims to:

Break silos between Development and Operations
Automate delivery
Improve reliability and speed

CI/CD provides the automation foundation.

Agile Coach Perspective on CI/CD

An Agile Coach does not usually build pipelines directly but helps:

Remove delivery bottlenecks
Encourage automation culture
Improve collaboration between Dev and Ops
Reduce manual approval delays
Improve release predictability

Common CI/CD Metrics

Deployment Frequency

How often software is released.

Lead Time for Changes

Time from code commit to production.

Change Failure Rate

Percentage of releases causing incidents.

Mean Time to Recovery (MTTR)

How quickly issues are resolved.

Common CI/CD Challenges

Legacy systems
Manual testing dependencies
Slow approval processes
Lack of automated tests
Environment inconsistencies
Cultural resistance

Modern CI/CD Practices

Shift Left Testing

Testing earlier in development.

Infrastructure as Code (IaC)

Infrastructure managed through code.

Blue-Green Deployments

Two production environments for safer releases.

Canary Releases

Gradually releasing to small user groups first.

Feature Toggles

Turning features on/off without redeployment.

Simple Real-World Example

A developer fixes a bug:

Pushes code to GitHub
Jenkins pipeline starts automatically
Tests run
Build passes
Application deploys to staging
Product Owner approves
Production deployment occurs automatically

Entire process may take:

Minutes instead of days/weeks

CI/CD in Interview Language

“CI/CD enables teams to continuously integrate, test, and deploy software through automated pipelines, improving delivery speed, quality, predictability, and feedback loops while reducing operational risk.”

Product Delivery Lifecycle

The Product Delivery Lifecycle is the end-to-end process of:

Discovering customer needs
Designing solutions
Building products
Delivering value
Continuously improving based on feedback

Unlike a traditional project lifecycle (which focuses on completing scope), the product delivery lifecycle focuses on:

continuous customer value delivery

High-Level Product Delivery Lifecycle

Discovery

↓

Prioritisation

↓

Planning

↓

Design

↓

Development

↓

Testing

↓

Release

↓

Measurement

↓

Feedback & Improvement

↓

Repeat

1. Product Discovery

Understanding:

Customer problems
Market opportunities
User behaviours
Business goals

Goal:

Build the right thing.

Activities

Customer interviews
Market research
User research
Journey mapping
Problem validation
Competitor analysis

Key Roles

Product Manager
UX Researchers
Stakeholders
Customers

2. Prioritisation

Deciding:

What delivers the most value
What should be built first
What should wait

Common Techniques

MoSCoW
WSJF
Value vs effort
RICE scoring

3. Planning

Preparing delivery execution.

Activities

Roadmap planning
Backlog refinement
Estimation
Dependency identification
Sprint/release planning

4. Design

Creating the user and technical experience.

Activities

UX/UI design
Wireframes
Architecture design
API design
Prototype testing

5. Development

Building the product incrementally.

Activities

Coding
Code reviews
Pair programming
CI/CD
Feature development

6. Testing & Quality Assurance

Ensuring the solution works properly.

Testing Types

Functional testing
Regression testing
Security testing
Performance testing
User acceptance testing

7. Release & Deployment

Making the product available to users.

Activities

Production deployment
Feature rollout
Change communication
Monitoring
Rollback readiness

8. Measurement & Monitoring

Evaluating:

Product performance
Customer outcomes
Business value

Common Metrics

Customer satisfaction
Usage analytics
Conversion rates
Retention
Revenue impact
Cycle time
Defect rates

9. Feedback & Continuous Improvement

Using insights to improve the product continuously.

Goal:

Learn fast and adapt quickly.

Feedback Sources

Customers
Analytics
Support tickets
Retrospectives
Stakeholder reviews

Agile Product Delivery Lifecycle

In Agile environments, delivery happens continuously in short feedback loops.

Typical Agile cycle:

Backlog refinement
Sprint planning
Build
Test
Demo/review
Retrospective
Release

Then repeat.

Product vs Project Thinking

Project Mindset

Product Mindset

Deliver scope

Deliver value

Temporary initiative

Continuous evolution

Success = on time

Success = customer outcomes

Fixed requirements

Adaptive learning

Output-focused

Outcome-focused

Product Delivery Roles

Product Manager

Owns product vision and prioritisation.

Product Owner

Manages backlog and team priorities.

Agile Coach / Scrum Master

Improves team effectiveness and delivery flow.

Engineering Team

Designs and builds the solution.

UX/UI Designers

Improve user experience and usability.

QA/Testers

Ensure quality and reliability.

Agile Coach Role in Product Delivery

An Agile Coach helps:

Improve flow efficiency
Remove bottlenecks
Facilitate collaboration
Improve Agile maturity
Strengthen feedback loops
Enable continuous improvement
Align delivery with customer value

Product Delivery Metrics

Flow Metrics

Lead time
Cycle time
Throughput

Quality Metrics

Escaped defects
Reliability
MTTR

Product Metrics

Adoption
Retention
NPS
Engagement

Delivery Metrics

Predictability
Velocity
Deployment frequency

Modern Product Delivery Concepts

DevOps

Development + operations collaboration.

DevOps

CI/CD

Automated build, test, and deployment pipelines.

Product Operating Model

Cross-functional teams aligned around customer value streams.

Value Stream Management

Optimising end-to-end value flow.

Continuous Discovery

Constant customer learning alongside delivery.

Common Product Delivery Challenges

Siloed teams
Too many dependencies
Poor prioritisation
Weak customer feedback
Slow release cycles
Technical debt
Leadership misalignment

Enterprise Product Delivery Example

A banking app team may:

Research customer pain points
Prioritise a new payment feature
Design the experience
Build incrementally in sprints
Test continuously
Release via CI/CD pipeline
Monitor usage metrics
Improve based on customer feedback

This cycle repeats continuously.

Interview-Style Summary

“The product delivery lifecycle is the continuous end-to-end process of discovering, designing, building, delivering, measuring, and improving products to maximise customer and business value through iterative feedback-driven delivery.”

Project Management Institute Agile Certified Practitioner (PMI-ACP)

The PMI-ACP is a globally recognised Agile certification offered by the Project Management Institute.

It validates knowledge and practical experience across:

Agile principles
Agile delivery
Agile leadership
Multiple Agile frameworks and techniques

Unlike certifications focused only on Scrum, PMI-ACP covers:

broad Agile thinking across multiple methodologies

What PMI-ACP Covers

PMI-ACP is framework-agnostic and includes:

Framework / Approach

Included

Scrum

Yes

Kanban

Yes

Lean

Yes

XP (Extreme Programming)

Yes

TDD

Yes

Agile leadership

Yes

Value-driven delivery

Yes

Continuous improvement

Yes

Why PMI-ACP is Valuable

It demonstrates:

Real Agile delivery knowledge
Practical Agile experience
Understanding of multiple Agile approaches
Ability to work in complex Agile environments

It is highly respected in:

Enterprise organisations
Banking
Consulting
Technology
Scaled Agile environments

PMI-ACP vs Scrum Certifications

PMI-ACP

PSM / CSM

Broad Agile coverage

Scrum-focused

Multiple methodologies

Primarily Scrum

Enterprise-oriented

Team-oriented

Requires experience

Some Scrum certs do not

Strong governance recognition

Strong Scrum depth

Eligibility Requirements

PMI changes requirements occasionally, but typically you need:

1. Agile Experience

Practical experience working on Agile teams/projects.

2. Agile Training

Formal Agile education/training hours.

3. General Project Experience

Project delivery experience.

Exam Areas

The PMI-ACP exam usually tests:

1. Agile Principles & Mindset

Agile Manifesto
Lean thinking
Servant leadership

2. Value-Driven Delivery

Prioritisation
Incremental delivery
Customer value

3. Stakeholder Engagement

Collaboration
Communication
Feedback loops

4. Team Performance

Team dynamics
Coaching
Conflict resolution

5. Adaptive Planning

Rolling wave planning
Iterative forecasting
Backlog management

6. Problem Detection & Resolution

Root cause analysis
Continuous improvement
Retrospectives

7. Continuous Improvement

Metrics
Feedback
Process optimisation

Key Agile Concepts in PMI-ACP

Servant Leadership

Leaders support and enable teams rather than command-and-control.

Empiricism

Decisions based on observation, evidence, and learning.

Incremental Delivery

Delivering value in small usable increments.

Adaptive Planning

Plans evolve as learning increases.

Continuous Feedback

Frequent inspection and adaptation.

Common Topics Studied

User stories
Estimation techniques
Velocity
Burn-down charts
Kanban flow
WIP limits
Agile metrics
Retrospectives
Technical debt
Risk management
Value stream thinking

Typical Agile Tools Referenced

Jira
Confluence
Azure DevOps
Kanban boards
Story mapping tools

PMI-ACP vs PMP

PMP

PMI-ACP

Traditional + hybrid PM

Agile-focused

Broad project governance

Agile delivery depth

Predictive methodologies

Adaptive methodologies

Scope/schedule control

Flow/value optimisation

Who Should Take PMI-ACP?

Ideal for:

Agile Coaches
Scrum Masters
Delivery Managers
Product Managers
Project Managers
Team Leads
Transformation Leads

Benefits of PMI-ACP

Strong global recognition
Enterprise credibility
Broad Agile understanding
Improves Agile career opportunities
Demonstrates practical Agile capability

Common PMI-ACP Interview Language

“I use Agile principles and adaptive delivery approaches to improve collaboration, flow, predictability, and customer value delivery across teams and organisations.”

Example Real-World PMI-ACP Skills

A PMI-ACP practitioner may:

Facilitate retrospectives
Coach Agile teams
Manage delivery risks
Improve Kanban flow
Support Scrum teams
Use Agile metrics
Enable continuous improvement
Align stakeholders around customer value

Recommended Complementary Certifications

Scrum.org PSM
Scaled Agile, Inc. SAFe
ICAgile ICAgile
Project Management Institute Disciplined Agile
DevOps certifications
Coaching certifications (ICF, leadership coaching, facilitation)

Azure DevOps

Azure DevOps is a cloud-based DevOps and Agile delivery platform from Microsoft used to manage:

Software development
Agile project delivery
CI/CD pipelines
Testing
Source control
Release management

It supports the full:

Software Development Lifecycle (SDLC)

and is widely used in enterprise Agile and DevOps environments.

Main Components of Azure DevOps

1. Azure Boards

Agile work management tool.

Used for:

Backlogs
User stories
Sprint planning
Kanban boards
Task tracking
Epics & features

Common Agile Features

Scrum boards
Kanban flow boards
Sprint tracking
Burndown charts
Velocity tracking
Work item management

2. Azure Repos

Source code management.

Supports:

Git repositories
Branching strategies
Pull requests
Code reviews

3. Azure Pipelines

CI/CD automation engine.

Supports:

Automated builds
Automated testing
Deployment pipelines
Multi-environment releases

4. Azure Test Plans

Testing management solution.

Supports:

Manual testing
Exploratory testing
Test case management
UAT tracking

5. Azure Artifacts

Package management repository.

Used for:

NuGet
npm
Maven packages
Dependency management

Azure DevOps in Agile Delivery

Azure DevOps helps Agile teams:

Visualise work
Manage backlogs
Improve transparency
Track flow
Automate delivery
Improve collaboration

Typical Agile Workflow in Azure DevOps

Product Backlog

↓

Sprint Planning

↓

Task Assignment

↓

Development

↓

Code Commit

↓

CI/CD Pipeline

↓

Testing

↓

Deployment

↓

Retrospective

Common Agile Practices Supported

Scrum

Sprint boards
Story points
Sprint planning
Velocity tracking

Kanban

WIP limits
Flow management
Cycle time analysis

DevOps

CI/CD pipelines
Infrastructure automation
Release orchestration

Agile Coach Perspective

An Agile Coach uses Azure DevOps to:

Improve visibility of work
Monitor delivery metrics
Reduce bottlenecks
Improve flow efficiency
Coach teams on backlog management
Improve predictability
Enable transparency

Common Azure DevOps Metrics

Flow Metrics

Lead time
Cycle time
Throughput

Sprint Metrics

Velocity
Burndown
Sprint completion rate

DevOps Metrics

Deployment frequency
Build success rate
MTTR
Change failure rate

Common Azure DevOps Boards Structure

Epic

Large strategic initiative.

↓

Feature

Business capability.

↓

User Story

Customer requirement.

↓

Task

Technical work item.

Common Work Item States

New

↓

Active

↓

Resolved

↓

Closed

Or in Kanban:

To Do

↓

In Progress

↓

Testing

↓

Done

CI/CD in Azure DevOps

Azure Pipelines automate:

Builds
Testing
Security scans
Releases

This enables:

Faster deployments
Lower risk
Continuous delivery

Common Azure DevOps Integrations

GitHub
Jira
Slack
Teams
SonarQube
Kubernetes
Docker

Advantages of Azure DevOps

Strong Microsoft ecosystem integration
Enterprise-ready
End-to-end delivery visibility
Excellent CI/CD support
Good Agile planning capabilities
Scalable across teams

Common Challenges

Can become overly process-heavy
Poor board configuration creates confusion
Over-customisation
Teams focusing on tools instead of Agile mindset

Azure DevOps vs Jira

Azure DevOps

Jira

Strong CI/CD integration

Strong Agile workflow flexibility

Microsoft ecosystem

Atlassian ecosystem

Integrated DevOps platform

Best-of-breed Agile management

Strong enterprise governance

Strong configurability

Example Interview Answer

“I’ve used Azure DevOps to support Agile delivery by managing backlogs, facilitating sprint planning, tracking delivery metrics, visualising flow through Kanban boards, and integrating CI/CD pipelines to improve delivery speed, transparency, and predictability.”