Product Engineering Maturity Model

Samudra KanankearachchiSoftware Architect @99X Technology

What is Product Engineering.

New Product Strategy & Planning

Product Design & Development

Testing Qualification &

Product Integration

Value Engineering

• Migration Services• Re-engineering• Product Enhancement• Cloud • Mobile Enablement

• Functional Product Testing• Compliance Certification• Technical Publications• Automation • Performance Testing • Security Testing

• Design Best Practices• Usability• Agile Product Development

• Product Consulting• Research • Feasibility Analysis• Architecture Design

Application Development : Focus on development life cycle of the

product

Product Engineering : Focus on end to end life cycle of the product

why we need a Maturity Model ?

L2

L3

L1

Maturity Levels are different

Startup

Matured Company

Achieving higher maturity in DevOps/CD is a key challenge

1. How do I deliver fast ? 2. How do I deliver often ?3. How I can be better than my competitors ?

What makes one software product is mature than other?

End User Experience ?

Features ?

Continuous Delivery Capability ?

Engineering Process Maturity ?Team Maturity?

Business Maturity ?

Development Team/Operation

Team

Engagement Maturity ?

There is no simple answer for this?

Imagine your delivery pipe looks like this

Can deliver fast and Often

Struggling to Deliver

Refactor / Redesign/ Re-Engineering

Rapid Development/ Poor Engineering

Where do I start cleanup this mess

Difficult to move forward with out a

guided model

We need to have guided model

Teams should be continuously trained to handle Product

Engineering

Software Product Engineering Continuity (SPEC)

is a Maturity Model specially crafted

for Distributed Product Engineering teams

SPEC Maturity Model

SPEC Maturity ModelEngineering Discipline

Business Focus

Team Building

Engagement Strength

Leve

l 2Le

vel

1Le

vel

3 Visible Quality

Agility in Design

Production Stability

Software Productization

Delivery Automation

Persona Awareness

Hypothesis Invalidation

Feature Delivery

Operational Analytics

User Experience

Model Bootstrap

Team Culture

Blue Oceans

Peer Feedback

Continuous Learning

Relationship Management

Product Assistance

Service Introduction

Organizational Sharing

Community Sharing

Key Areas

Levels

Sub Areas

Practices “Visible Quality (VQ)” Sub Area

Practices “Relationship Management (RM)” Sub Area

How do I use this model?

SPEC Gap Analysis

SPEC Backlog

SPEC Audit (Show Evidences)

It is all about creating a disciplined culture using SPEC

It is a journey / change won't happen overnight. Try make tomorrow better than today