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