This is the QDR template all of our Development Managers use to report on progress of teams every 3 months. Check out the below post for more details: - https://medium.com/ingeniouslysimple/how-we-report-on-teams-at-redgate-5d66c5fdf4c4

1. XXX Programme– 2019 Q3
Quarterly Product Development Review
A.Person

2. Team(s) Overview
The XXX Teams
Changes in last period: -
• Developer A moved to programme X
• Developer B has joined team u.p, expect a month to get up to speed
• Designer C is on sabbatical for next 6 weeks
Team U.P
The Autobots
Team Orca

3. Teams Purpose
Our Purpose
To build Ingeniously Simple products our customers love and recommend
to their colleagues

4. Team– OKR1 (Q3 review)
Objectives We aim to increase the number of people using XXX product in a production environment
# Key Results Confidence Progress Actual Minimum
OKR1 KR1 KR1: The number of users using the product as part of a production
pipeline increases by: -
• Baseline – 0
• Minimum – 1
• Gold standard – 3
100% 100% 10 1
OKR1 KR2 KR2: The number of users who have successfully created a deployment
increases: -
• Baseline – 2
• Minimum – 15
• Gold standard – 40
100% 100% 81 15

5. Team– OKR2 (Q3 review)
Objectives Example here
# Key Results Confidence Progress Actual Minimum
OKR2 KR1 70% 70% X X
OKR2 KR2 100% 100% 1 1
OKR2 KR3 100% 100% 1 1

6. Accelerate Metrics – Product 1
Measure RAG
Dep Freq
L/T

7. Accelerate Metrics – Product 2
Measure RAG
Dep Freq
L/T

8. Successes
• Team launched new product to market
• Release went on 12th September and take up was XX
• Retrospective identified following areas for improvement in release process
• Xxxx
• Xxxx
• Working practices continue to evolve
• Mob programming by default
• XP practices being embedded
• Experiment on trunk based development started

9. Challenges
• Change failure rate above 5% for one week
• Due to outage on widget 2
• Team recovered service by Thursday
• Experiment on pairing groups stopped
• Feedback from latest retro was that experiment was slowing team
• xxxxxxxxxxx

10. PDP/ Succession/
Stars
PDP Successions Plans Stars
Team X All team members 1 senior engineer, 1 tech lead Person A
Team Y All team members 1 product manager Person B
Legend
Green: Team strength; area of
excellence.
Amber: Some good practice in
this area, but room for
improvement
Red: Team weakness; team
have problems/lack of
awareness/ deprioritized area
* = improvement focus
Overall Health
Team Health Agile/ Lean Values
Where the score is identified as amber or red,
improvement activity is taking place this quarter to
improve the rating
Adaptable
Qualityisbuiltin
Transparent
FocusonBusiness
Value
Focusonuser
WorkingSoftware
Continuousdelivered
Collaborate
Wasteiseliminated
Retainlearning
PLG
Team U.P - Q1 2019
Team U.P - Q2 2019
Team U.P - Q3 2019
The Autobots - Q1 2019
The Autobots - Q2 2019
The Autobots - Q3 2019
Team X Q2 2019
Team X Q3 2019
Team X Q4 2019
Team Y Q2 2019
Team Y Q3 2019
Team Y Q4 2019

11. Improvement Actions• Demonstrate how teams are improving accelerate metrics
• Get metrics up and working for team A – DONE
• Demonstrate reduction in MTTR and CFR for both teams – NOT DONE
• Demonstrate continuous improvement activity across all 3 teams
• Mob programming as default - DONE
• New mob programming spaces created - DONE

12. Next Quarter

13. 2019 Q4: OKRsObjectives We aim to increase the number of people using XXX product in a production environment
# Key Results Confidence Progress Actual Minimum
OKR1 KR1 KR1: The number of users using the product as part of a production
pipeline increases by: -
• Baseline – 0
• Minimum – 1
• Gold standard – 3
0% 0% X X
OKR1 KR2 KR2: The number of users who have successfully created a deployment
increases: -
• Baseline – 2
• Minimum – 15
• Gold standard – 40
0% 0% X x

14. Improvement Actions
• Demonstrate how teams are improving accelerate metrics
• Address CFR and MTTR across two teams and their products
• Ensure all teams are regularly reviewing metrics and understand why they are where they are
• Launch V1 solution in mid October

15. Questions?