LITMIR.BIZ

Скачать книгу

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

Скачать книгу