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