Decision Support Software A Complete Guide - 2020 Edition. Gerardus Blokdyk

Score

      10. Who are the Decision support software improvement team members, including Management Leads and Coaches?

      <--- Score

      11. What baselines are required to be defined and managed?

      <--- Score

      12. Do you all define Decision support software in the same way?

      <--- Score

      13. Is the current ‘as is’ process being followed? If not, what are the discrepancies?

      <--- Score

      14. Is the work to date meeting requirements?

      <--- Score

      15. How does the Decision support software manager ensure against scope creep?

      <--- Score

      16. How did the Decision support software manager receive input to the development of a Decision support software improvement plan and the estimated completion dates/times of each activity?

      <--- Score

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

      18. In what way can you redefine the criteria of choice clients have in your category in your favor?

      <--- Score

      19. Is the team formed and are team leaders (Coaches and Management Leads) assigned?

      <--- Score

      20. When is the estimated completion date?

      <--- Score

      21. When are meeting minutes sent out? Who is on the distribution list?

      <--- Score

      22. What constraints exist that might impact the team?

      <--- Score

      23. Are customer(s) identified and segmented according to their different needs and requirements?

      <--- Score

      24. What are the compelling stakeholder reasons for embarking on Decision support software?

      <--- Score

      25. How often are the team meetings?

      <--- Score

      26. Is the team equipped with available and reliable resources?

      <--- Score

      27. What system do you use for gathering Decision support software information?

      <--- Score

      28. Who is gathering Decision support software information?

      <--- Score

      29. What Decision support software services do you require?

      <--- Score

      30. Does the scope remain the same?

      <--- Score

      31. What are the record-keeping requirements of Decision support software activities?

      <--- Score

      32. Are resources adequate for the scope?

      <--- Score

      33. Is the team sponsored by a champion or stakeholder leader?

      <--- Score

      34. What sort of initial information to gather?

      <--- Score

      35. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?

      <--- Score

      36. What sources do you use to gather information for a Decision support software study?

      <--- Score

      37. Has a project plan, Gantt chart, or similar been developed/completed?

      <--- Score

      38. Scope of sensitive information?

      <--- Score

      39. Is there a Decision support software management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?

      <--- Score

      40. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?

      <--- Score

      41. Is there a clear Decision support software case definition?

      <--- Score

      42. How do you gather Decision support software requirements?

      <--- Score

      43. What Decision support software requirements should be gathered?

      <--- Score

      44. Has a Decision support software requirement not been met?

      <--- Score

      45. How do you hand over Decision support software context?

      <--- Score

      46. What defines best in class?

      <--- Score

      47. How do you think the partners involved in Decision support software would have defined success?

      <--- Score

      48. How do you build the right business case?

      <--- Score

      49. What is the scope of the Decision support software work?

      <--- Score

      50. Is special Decision support software user knowledge required?

      <--- Score

      51. What is a worst-case scenario for losses?

      <--- Score

      52. If substitutes have been appointed, have they been briefed on the Decision support software goals and received regular communications as to the progress to date?

      <--- Score

      53. Do you have a Decision support software success story or case study ready to tell and share?

      <--- Score

      54. What is out-of-scope initially?

      <--- Score

      55. Does the team have regular meetings?

      <--- Score

      56. Is the Decision support software scope complete and appropriately sized?

      <--- Score

      57. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?

      <--- Score

      58. How do you gather requirements?

      <--- Score

      59. What information should you gather?

      <--- Score

      60. Are required metrics defined, what are they?

      <--- Score

      61. What are the core elements of the Decision support software business case?

      <--- Score

      62. How and when will the baselines be defined?

      <--- Score

      63. Has a high-level ‘as is’ process map been completed, verified and validated?

      <---