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