Software AG A Complete Guide - 2020 Edition. Gerardus Blokdyk

Чтение книги онлайн.

СКАЧАТЬ there recognized Software AG problems?

      <--- Score

      79. What does Software AG success mean to the stakeholders?

      <--- Score

      80. How much are sponsors, customers, partners, stakeholders involved in Software AG? In other words, what are the risks, if Software AG does not deliver successfully?

      <--- Score

      81. Which information does the Software AG business case need to include?

      <--- Score

      82. Is the quality assurance team identified?

      <--- Score

      83. Will a response program recognize when a crisis occurs and provide some level of response?

      <--- Score

      84. What should be considered when identifying available resources, constraints, and deadlines?

      <--- Score

      85. How do you identify the kinds of information that you will need?

      <--- Score

      86. Do you recognize Software AG achievements?

      <--- Score

      87. How many trainings, in total, are needed?

      <--- Score

      88. Is the need for organizational change recognized?

      <--- Score

      89. Will new equipment/products be required to facilitate Software AG delivery, for example is new software needed?

      <--- Score

      90. What is the smallest subset of the problem you can usefully solve?

      <--- Score

      91. Does the problem have ethical dimensions?

      <--- Score

      92. Are controls defined to recognize and contain problems?

      <--- Score

      93. To what extent does each concerned units management team recognize Software AG as an effective investment?

      <--- Score

      94. Are your goals realistic? Do you need to redefine your problem? Perhaps the problem has changed or maybe you have reached your goal and need to set a new one?

      <--- Score

      95. How do you assess your Software AG workforce capability and capacity needs, including skills, competencies, and staffing levels?

      <--- Score

      96. What activities does the governance board need to consider?

      <--- Score

      97. Do you have/need 24-hour access to key personnel?

      <--- Score

      98. What is the problem or issue?

      <--- 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.

      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

СКАЧАТЬ