| A | B | C | |
|---|---|---|---|
1 | Executive Summary - example | ||
2 | |||
3 | Effectiveness | ||
4 | |||
5 | |||
6 | |||
7 | |||
8 | |||
9 | |||
10 | |||
11 | |||
12 | |||
13 | |||
14 | |||
15 | |||
16 | |||
17 | |||
18 | |||
19 | |||
20 | |||
21 | |||
22 | 80% of committed initiatives were delivered with an average lead time of 1 and half days. 5% of unplanned work was added to the quarter committed backlog. | ||
23 | |||
24 | New Features investment was kept above 40%. Our investment to pay down Tech Debt reduced to 15%, from 19% last quarter, due to an increase in bug fixing (+8%), in which we invested 32% of our efforts. | ||
25 | |||
26 | The average time to repair High priority bugs is breaching defined SLOs. High priority bugs average 7 days from time submitted to get solved, with 57% of time spent waiting in the backlog. | ||
27 | |||
28 | Next Steps: | ||
29 | - Improve Jira health and processes to have better tracking of initiatives with clear visibility of the value delivered and time to deliver (break epics in more effective value delivery units - outcome focused). | ||
30 | - Teams will set a goal of reducing MTTR of high priority bugs from 7 to 5 days, for Q4, and will redirect team capacity to fix high priority problems faster. | ||
31 | |||
32 | |||
33 | |||
34 | |||
35 | |||
36 | |||
37 | Efficiency | ||
38 | |||
39 | |||
40 | |||
41 | |||
42 | |||
43 | |||
44 | |||
45 | |||
46 | |||
47 | |||
48 | |||
49 | |||
50 | |||
51 | |||
52 | |||
53 | |||
54 | |||
55 | |||
56 | Teams' velocity started to increase as planned. Currently it teams take 1 and half day to take code from start to production. This represents a 21% improvement when compared with the 2 days of Q2. This happened due to the reduction of the release time. | ||
57 | |||
58 | Number of bugs reported has been stable over time, however the investment the team is making to solve bugs is not enough to avoid backlog growth. With a 74% fixing ratio team is increasing the backlog of bugs. Most of the bugs are not critical, so we will not do anything at this time. | ||
59 | |||
60 | Team keeps following DORA’s best practices by deploying code twice a day, with above 90% deployment success ratio. | ||
61 | |||
62 | Next Steps: | ||
63 | - Set a goal to increase team velocity by reducing average review time by 50%, ensure review time gets back to same numbers of Q2 by having a more effective code review process. | ||
64 | |||
65 | |||
66 | |||
67 | |||
68 | |||
69 | |||
70 | |||
71 | |||
72 | |||
73 | |||
74 | |||
75 | |||
76 | |||
77 | |||
78 | |||
79 | |||
80 | |||
81 | |||
82 | |||
83 | |||
84 | |||
85 | |||
86 | |||
87 | |||
88 | |||
89 | |||
90 | |||
91 | |||
92 | |||
93 | |||
94 | |||
95 | |||
96 | |||
97 | |||
98 | |||
99 | |||
100 | |||