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