style="font-size:15px;"> 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.
