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