4. Why we needed yet another maturity model
3
• Maturity Models are usually really high level – we wanted to enable
teams to go on the journey themselves
• Maturity models usually don’t really tell you about dependencies, which
we wanted to address to avoid “we do CI, but don’t have automated
tests”
• Maturity models usually don’t tell when you need to coordinate
something centrally and what applications can do on their own
• We didn’t like that the models had reportable levels, we wanted to see
progress not gaining levels
6. Telstra CD Technical Capabilities – Dependency Tree
Feature Toggling
Configuration
Management
Unit Testing
Build Practices
Deployment
Practices
Functional Testing
Virtualisation
Software Quality
Package Promotion
Reporting &
Visibility
•CD team have defined a
set of technical
dependencies
(capabilities) required on
the path to achieving
Continuous Delivery
•Foundation capabilities
are at the left. These are
the minimum required.
•The most mature
capabilities are at the
right.
•Yellow are enterprise
dependencies
• Each box comes with
definition and metrics
7. Continuous Delivery is
at the very far right!
CD Technical Capabilities – Highlights of the vision
Feature Toggling
Configuration
Management
Unit Testing
Build Practices
Deployment
Practices
Functional Testing
Virtualisation
Software Quality
Package Promotion
Reporting &
Visibility
8. Continuous Delivery is at
the very far right!
It is a multi-year journey to
achieve this across the
organisation with many
enabling technical
capability pre-requisites.
Feature Toggling
Configuration
Management
Unit Testing
Build Practices
Deployment
Practices
Functional
Testing
Virtualisation
Software Quality
Package
Promotion
Reporting &
Visibility
Telstra CD Technical Capabilities – Current Focus
Focus is on getting
applications to establish
foundation capabilities in:
- Automated Unit
Testing
- Auto Packaging
- Auto Deployments
and collecting baseline
metrics
9. Feature Toggles
Key Challenge: How do
you toggle across the
enterprise?
Dependant on everything
being in SourceControl
Similar annotations
will be done for the
following slides
11. Unit Testing
10
*Depending on each application’s needs,
the team involved willchosefrom the
following coverage criteria: function,
statement, branch or condition coverage.
Details of what eachof thesemean can
befound intheDefinitions andMetrics
document.
20. Environment BuildReporting
Delivery
Environments
Requirements Management
Data Warehouse
Status of Project
Health of Build
Defect Rate
Duration of Deployment
Workflow
Management
Source Control
Build Server
Build Scheduler
Build Store
Initiate Initiate Initiate
Extract Store
Test
Management
Automated
Manual
Defect
Retrofit
Requirement
Design Tooling
Integrated
Development
Environment
Environment
Configuration
Environment Design
Environment Build
Scheduler
Environment
Monitoring
Functional
Technical
Build
Deploy
Deploy
Deploy
Requirement
Implementation
Design
Development
Test
Production
Virtual Server
Provisioning
Build Governance
Source Code
Build Version
Technology
Documentation
PromotionPath
Automated
Regression
Cycle
Automated
Regression
Cycle
Automated
Regression
Cycle
Deploy Scheduler
Portfolio, Program and Project Management
Agile Lifecycle
Management
Portfolio
Management
Service
Management /
Kanban
Application Lifecycle
Management
Project Management
(Risk, Issue, etc.)
Enterprise Planning
Idea Generation
Demand
Management
Idea Prioritisation
21. Thank You!
Your Feedback is Important!
Access the Innovate agenda tool to complete your
session surveys from your smartphone, laptop or
conference kiosk.