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