Software AG A Complete Guide - 2020 Edition. Gerardus Blokdyk
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.