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