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