The document describes four levels of process maturity for software development teams: Level 1 is ad hoc - processes are chaotic and undefined. Execution relies on individuals and successes are difficult to repeat. Level 2 is managed - processes are deliberate but not fully defined. Roles and responsibilities are clearer, decisions are managed, and some templates and checklists are used. Level 3 is advanced - processes are well-defined and measured. Alignment of vision and strategy is clear, knowledge is systematically shared, and UX design is integrated into the process. Level 4 is leading - measurements are used to continuously monitor and improve products. Collaboration is highly effective, skills are fully in place, and testing is rigorously automated and

2. •
•
•
•
•
•
•
•
•
•

5. •
•
•

6. Level 1 – Ad hoc Level 2 – Managed Level 3 – Advanced Level 4 – Leading
Initial, chaotic Deliberate, thinking Process defined Measure, optimize
Process No formal process
Execution tied up on individuals
Difficult to repeat successes
Process abandoned under
pressure
“We repeat what goes well –
even, if we are not entirely
certain why it worked well”
Clear and well-understood
company vision
Well established processes,
measured, monitored and
reported to track performance
Full alignment of company
vision and strategy
Measurements are continuously
used to monitor, question and
improve product
Collaboration and
organization
Roles and responsibilities are
not clearly defined
“Command” decisions
Roles and responsibilities clear
“Things get done”
Clear decision making process
Clear interfaces to other
departments
Mutual trust
Systems, templates
and check lists
Little available
Market insights and product
knowledge in individuals heads
All key activities guided by
templates, check lists and tools
Knowledge sharing system for
market, projects and products
Clear user scenarios and
personas
Systematic knowledge
gathering and sharing about
market, products
Continuous evaluation of tools
People Re-active and tactical
Firefighting “heroes”
No end-users involved in design
Tactical + strategic focus
Graphical designer in team
No UX specialists
Skills in place for all tasks,
including UX specialists
UX design starts Towards end of coding Discussion - during coding UX design before coding Part of product vision

7. Level 1 – Ad hoc Level 2 – Managed Level 3 – Advanced Level 4 – Leading
Initial, chaotic Deliberate, thinking Process defined Measure, optimize
Process No formal process
Execution is usually tied up on
individuals - “heroes”
Difficult to repeat successes
We will repeat what goes well –
even, if we are not entirely
certain why it worked well
One shared project model.
Adapted to the individual
implementation.
Regular retrospective lessons
learnt.
Performance metrics provide full
visibility
Bottlenecks identified and
corrective action taken
Visibility and predictability
Collaboration and
organization
Roles and responsibilities are
not clearly defined
“Command” decisions
Communication is managed and
facilitated
Regular meetings to sync team
members
Consensus decisions
Regular sharing of experience
and ideas also across teams.
Mutual trust.
Collaborative decisions.
Pair programming, code reviews
Knowledge sharing
Individual empowerment
Systems, templates
and check lists
Mail
Skype
Task management system
Some local automation
Slack, Hangouts
Code conventions
Continuous integration
Shared knowledge platform
Code conventions automatically
checked
Click-of-a-button full build and
testing
Testing and QA Developer may test own code Dedicated QA function
Manual testing
Test coverage analysis
Automated functional testing
Next-to complete
unit-test coverage

8. Ad hoc
Managed
Advanced
Ad hoc Managed Advanced
Product
management
& ownership
Software
development

9. •
•
•

10. Ad hoc
Managed
Advanced
Ad hoc Managed Advanced
Product
ownership
Software
development
If you are over a sinkhole,
and you know it
You are going to want
to get out of there
Always

11. •
•
•
•