Excellence Driven Retrospective Framework
This article includes two parts. The first part is the concept. The second part is the implementation.
Part 1: The concept of Excellence Driven
Purpose:
Define what the team value most and use it to drive continuous excellence.
Instruction:
- Define a series of excellence.
- Regularly review and improve.
- The base philosophy is long term team and long term investment.
The example of series of excellence:
1. Cross functional team
Definition: not let skill imbalance an impediment.
Sub items:
- define people and skills matrix, and the ideal skills distribution.
- arrange pair programming in sprint work with allowed capacity.
- consider personal interest.
(current map + interest map -> ideal map)
(ideally on each skill, there are 2 persons who master and 1 person who knows about.)
2. Value stream optimization
Definition: remove obstacle and let every effort toward customer value.
Sub items:
- DoR
- DoD
- committed plus optional stories, the optional stories can be identified on either planning or grooming
- identify impediments
- meeting structure and rhythm improvement.
3. Team work
Definition: team collaborate to maximize team effort.
Sub items:
- knowledge sharing
- regular celebration, pursuit award
- collective code ownership
- cross person demo, Tom demo Jerry's work
Part 2: implement Excellence Driven in Retrospective
As illustrated in the picture below, the steps are:
People get familar with the concept of Excellence Driven above.
Print each category of the Excellence in an A4 or A3 paper, and post on the white board.
People use silent brainstorm (i.e. write on Post-It without talking with each other) to generate idea, either Did Good or Need Improvement against each Excellence category.
Go through all the Post-Its and generate action items to form Improvement Backlog.
Refine (CRUD) the Excellence categories.
参考：
阅读原文，补充修订扩展备用页。