Читать книгу Software Reliability A Complete Guide - 2020 Edition - Gerardus Blokdyk - Страница 8
ОглавлениеCRITERION #2: DEFINE:
INTENT: Formulate the stakeholder problem. Define the problem, needs and objectives.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. Has a Software reliability requirement not been met?
<--- Score
2. How can the value of Software reliability be defined?
<--- Score
3. What critical content must be communicated – who, what, when, where, and how?
<--- Score
4. What system do you use for gathering Software reliability information?
<--- Score
5. How did the Software reliability manager receive input to the development of a Software reliability improvement plan and the estimated completion dates/times of each activity?
<--- Score
6. Has a team charter been developed and communicated?
<--- Score
7. Has the direction changed at all during the course of Software reliability? If so, when did it change and why?
<--- Score
8. What intelligence can you gather?
<--- Score
9. What is out-of-scope initially?
<--- Score
10. How often are the team meetings?
<--- Score
11. Is the team equipped with available and reliable resources?
<--- Score
12. What information should you gather?
<--- Score
13. What is a worst-case scenario for losses?
<--- Score
14. How do you gather Software reliability requirements?
<--- Score
15. Have all of the relationships been defined properly?
<--- Score
16. What Software reliability requirements should be gathered?
<--- Score
17. How do you catch Software reliability definition inconsistencies?
<--- Score
18. How would you define Software reliability leadership?
<--- Score
19. How do you think the partners involved in Software reliability would have defined success?
<--- Score
20. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
21. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
22. Are all requirements met?
<--- Score
23. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
24. Who defines (or who defined) the rules and roles?
<--- Score
25. Is it clearly defined in and to your organization what you do?
<--- Score
26. How do you hand over Software reliability context?
<--- Score
27. Is the work to date meeting requirements?
<--- Score
28. What are the tasks and definitions?
<--- Score
29. Do you all define Software reliability in the same way?
<--- Score
30. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
31. Are there different segments of customers?
<--- Score
32. Are the Software reliability requirements complete?
<--- Score
33. What sources do you use to gather information for a Software reliability study?
<--- Score
34. Are task requirements clearly defined?
<--- Score
35. What are the Software reliability tasks and definitions?
<--- Score
36. What baselines are required to be defined and managed?
<--- Score
37. Do you have a Software reliability success story or case study ready to tell and share?
<--- Score
38. What are the record-keeping requirements of Software reliability activities?
<--- Score
39. Have specific policy objectives been defined?
<--- Score
40. Who approved the Software reliability scope?
<--- Score
41. Is there any additional Software reliability definition of success?
<--- Score
42. What are the Software reliability use cases?
<--- Score
43. How and when will the baselines be defined?
<--- Score
44. Have all basic functions of Software reliability been defined?
<--- Score
45. How do you manage changes in Software reliability requirements?
<--- Score
46. What Software reliability services do you require?
<--- Score
47. What key stakeholder process output measure(s) does Software reliability leverage and how?
<--- Score
48. What is in scope?
<--- Score
49. How do you gather requirements?
<--- Score
50. If substitutes have been appointed, have they been briefed on the Software reliability goals and received regular communications as to the progress to date?
<--- Score
51. Do you have organizational privacy requirements?
<--- Score
52. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
53. Does the scope remain the same?
<--- Score
54. Are audit criteria, scope, frequency and methods defined?
<--- Score
55. The political context: who holds power?
<--- Score
56. Who is gathering Software reliability information?
<--- Score
57. How are consistent Software reliability definitions important?
<--- Score
58. What happens if Software reliability’s scope changes?
<--- Score
59. How will the Software reliability team and the group measure complete success of Software reliability?
<--- Score
60. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
61. Is there a Software reliability management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
62. What customer feedback methods were used to solicit their input?
<--- Score
63. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
64. What are the rough order estimates on cost savings/opportunities that Software reliability brings?
<--- Score
65. Is Software reliability currently on schedule according to the plan?
<--- Score
66. Has the Software reliability work been fairly and/or equitably divided and delegated among team members who are qualified and capable to perform the work? Has everyone contributed?
<--- Score
67. Is the scope of Software reliability defined?
<--- Score
68. What gets examined?
<--- Score
69. Is there a critical path to deliver Software reliability results?
<--- Score
70. Is special Software reliability user knowledge required?
<--- Score
71. How have you defined all Software reliability requirements first?
<--- Score
72. Is scope creep really all bad news?
<--- Score
73. How do you gather the stories?
<--- Score
74. How will variation in the actual durations of each activity be dealt with to ensure that the expected Software reliability results are met?
<--- Score
75. Is Software reliability required?
<--- Score
76. Is the Software reliability scope manageable?
<--- Score
77. What is the scope of the Software reliability work?
<--- Score
78. What scope to assess?
<--- Score
79. What constraints exist that might impact the team?
<--- Score
80. Is there a clear Software reliability case definition?
<--- Score
81. What are the requirements for audit information?
<--- Score
82. How is the team tracking and documenting its work?
<--- Score
83. Has/have the customer(s) been identified?
<--- Score
84. What are the dynamics of the communication plan?
<--- Score
85. What is the definition of success?
<--- Score
86. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
87. What are (control) requirements for Software reliability Information?
<--- Score
88. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
89. Who is gathering information?
<--- Score
90. What is in the scope and what is not in scope?
<--- Score
91. What is the worst case scenario?
<--- Score
92. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
93. What sort of initial information to gather?
<--- Score
94. How do you build the right business case?
<--- Score
95. What are the core elements of the Software reliability business case?
<--- Score
96. What is out of scope?
<--- Score
97. How would you define the culture at your organization, how susceptible is it to Software reliability changes?
<--- Score
98. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
99. Does the team have regular meetings?
<--- Score
100. Are accountability and ownership for Software reliability clearly defined?
<--- Score
101. How do you manage unclear Software reliability requirements?
<--- Score
102. Are there any constraints known that bear on the ability to perform Software reliability work? How is the team addressing them?
<--- Score
103. How do you keep key subject matter experts in the loop?
<--- Score
104. Where can you gather more information?
<--- Score
105. Why are you doing Software reliability and what is the scope?
<--- Score
106. Are required metrics defined, what are they?
<--- Score
107. What information do you gather?
<--- Score
108. How does the Software reliability manager ensure against scope creep?
<--- Score
109. What are the compelling stakeholder reasons for embarking on Software reliability?
<--- Score
110. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
111. Scope of sensitive information?
<--- Score
112. What is the scope of Software reliability?
<--- Score
113. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
114. Is Software reliability linked to key stakeholder goals and objectives?
<--- Score
115. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
116. Are roles and responsibilities formally defined?
<--- Score
117. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
118. What would be the goal or target for a Software reliability’s improvement team?
<--- Score
119. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
120. When is the estimated completion date?
<--- Score
121. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?
<--- Score
122. What is the scope of the Software reliability effort?
<--- Score
123. Has your scope been defined?
<--- Score
124. What is the definition of Software reliability excellence?
<--- Score
125. What is the context?
<--- Score
126. When is/was the Software reliability start date?
<--- Score
127. What are the boundaries of the scope? What is in bounds and what is not? What is the start point? What is the stop point?
<--- Score
128. How do you manage scope?
<--- Score
129. Who are the Software reliability improvement team members, including Management Leads and Coaches?
<--- Score
130. What knowledge or experience is required?
<--- Score
131. Are approval levels defined for contracts and supplements to contracts?
<--- Score
132. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
133. Is the improvement team aware of the different versions of a process: what they think it is vs. what it actually is vs. what it should be vs. what it could be?
<--- Score
134. Is the Software reliability scope complete and appropriately sized?
<--- Score
135. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
136. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
137. Will a Software reliability production readiness review be required?
<--- Score
138. What was the context?
<--- Score
Add up total points for this section: _____ = Total points for this section
Divided by: ______ (number of statements answered) = ______ Average score for this section
Transfer your score to the Software reliability Index at the beginning of the Self-Assessment.
