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