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