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