ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Instructions
2
The most important skill for a manager is to select the ONE idea to implement this week. Not trying to do 10 at once. Only ONE forces the manager to pick the BIGGEST IMPACT item that is doable in a week. Elite managers are comfortable being forced to make decisions about cost and priority and timing, not JUST produce a list of things for someone else to choose from. What happens with bad managers is they generate all the ideas and pick the wrong things to do at the wrong times.
3
4
Deliverable #1: What is the biggest impact item for this team that you would do next week?
5
6
Deliverable #2: Provide a summarized stack rank (1 = action you would take next week.......5 = least important decision to make)of all the actions you recommend for this team based on your insights with WS data.
7
8
ActionAffect quality?Easy/Hard?Quick/Long?
9
1. Manager has to establish the Eng.Maintenance.QE team and start enforcing the Quality Bar, and require ICs to attach video evidence (PIQB.8) to their tickets.
Currently the team has 4.98% EQB failure rate. By the proposed IQB the team also has 2.29% formatting issue failures and 1.24% related to unit tests. These can slip through the system at the moment, because the ICs do the IQB for their own tickets, it’s not enforced.		This has the potential to remove all current IQB failures: 8.52%HardLong
10
2. During my QB enforcement I noticed a returning pattern of code formatting issues, which appeared in 2.29% of all reviewed tickets. To handle this returning issue I will add the following IQB items: "PIQB.6 Code is free from formatting issues", "PIQB.7 Code is free from unused import statements"2.29% increase in the proposed IQB FTAREasyQuick
11
3. While doing my QB enforcements I found tickets where the developer didn’t run unit tests locally before opening the PR and had to fix them while the PCA was reviewing the code. These rounds waste time for everyone, to treat this issue I’m adding QB item "PIQB.2 Ran all unit tests and they all succeed"1.24% increase in the proposed IQB FTAREasyQuick
12
4. Start measuring functional errors and hold the ICs accountable for these mistakes. Currently the team thinks that leaving functional errors in the code and getting rejected in verification step is part of the process and is accepted. The only form of (EQB) FTAR calculation they have does not regard for these issues and noone is held responsible for them, but in fact, it hurts the team’s image and wastes time for the maintenance team and every team downstream. I will create a sheet with every IC’s proposed IQB FTAR and announce to the team that the Rank and Reviews will be done based on this report. This change will also force the ICs to test their changes and help increase the EQB FTAR by 4.98%.Not directly, but
reveals the tickets failed on testing (4.98%)		EasyQuick
13
14
Deliverable #3 Instructions: Identify at least 10 specific units that failed the quality bar. For each unit, provide the reason for failure and the solution that would prevent this failure. Then stack rank the solutions in deliverable #4.
15
Jira ticket linkReason for QB failureSolution
16
WMP-49Unit tests weren't addedManager has to establish the Eng.Maintenance.QE team and start enforcing the Quality Bar
17
NVPCID-8727Was not tested properlyManager has to establish the Eng.Maintenance.QE team and start enforcing the Quality Bar
18
NVPCID-7958Was not tested properlyManager has to establish the Eng.Maintenance.QE team and start enforcing the Quality Bar
19
CST-12041Code formatting issuesConfigure default code formatter adjusted for the project in intelliJ (use Fernando's settings)
20
CST-11717Code formatting issuesConfigure default code formatter adjusted for the project in intelliJ (use Fernando's settings)
21
CST-4562Code formatting issuesConfigure default code formatter adjusted for the project in intelliJ (use Fernando's settings)
22
SL-36731tests failedAdd item to IQB "Ran tests and all succeeded"
23
WMP-49Unit tests weren't addedManager has to establish the Eng.Maintenance.QE team and start enforcing the Quality Bar
24
NVPCID-7658Was not tested properlyManager has to establish the Eng.Maintenance.QE team and start enforcing the Quality Bar
25
SL-36078Was not tested properlyManager has to establish the Eng.Maintenance.QE team and start enforcing the Quality Bar
26
27
Deliverable #4: Stack rank of solutions for QB failures
Impact
28
1. Manager has to establish the Eng.Maintenance.QE team and start enforcing the Quality Bar60%This should be your 1 idea
29
2. Add QB items "PIQB.6 Code is free from formatting issues", "PIQB.7 Code is free from unused import statements"30%
30
3. Add QB item "Ran all unit tests and they all succeed"10%
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
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