Game As A Service A Complete Guide - 2020 Edition. Gerardus Blokdyk

      <--- Score

      12. Is there a critical path to deliver Game as a service results?

      <--- Score

      13. What constraints exist that might impact the team?

      <--- Score

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

      <--- Score

      15. Is special Game as a service user knowledge required?

      <--- Score

      16. Will team members perform Game as a service work when assigned and in a timely fashion?

      <--- Score

      17. What defines best in class?

      <--- Score

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

      <--- Score

      19. Is the Game as a service scope manageable?

      <--- Score

      20. How do you manage unclear Game as a service requirements?

      <--- Score

      21. Is scope creep really all bad news?

      <--- Score

      22. Are all requirements met?

      <--- Score

      23. What is out-of-scope initially?

      <--- Score

      24. How did the Game as a service manager receive input to the development of a Game as a service improvement plan and the estimated completion dates/times of each activity?

      <--- Score

      25. What Game as a service requirements should be gathered?

      <--- Score

      26. What are the core elements of the Game as a service business case?

      <--- Score

      27. How do you manage scope?

      <--- Score

      28. What key stakeholder process output measure(s) does Game as a service leverage and how?

      <--- Score

      29. Does the team have regular meetings?

      <--- Score

      30. How and when will the baselines be defined?

      <--- Score

      31. Is Game as a service currently on schedule according to the plan?

      <--- Score

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

      33. Is data collected and displayed to better understand customer(s) critical needs and requirements.

      <--- Score

      34. Are task requirements clearly defined?

      <--- Score

      35. How do you manage changes in Game as a service requirements?

      <--- Score

      36. Who is gathering information?

      <--- Score

      37. What system do you use for gathering Game as a service information?

      <--- Score

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

      <--- Score

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

      <--- Score

      40. How was the ‘as is’ process map developed, reviewed, verified and validated?

      <--- Score

      41. How would you define the culture at your organization, how susceptible is it to Game as a service changes?

      <--- Score

      42. What is out of scope?

      <--- Score

      43. Do you all define Game as a service in the same way?

      <--- Score

      44. Have specific policy objectives been defined?

      <--- Score

      45. Is Game as a service required?

      <--- Score

      46. Have all basic functions of Game as a service been defined?

      <--- Score

      47. What is the scope?

      <--- Score

      48. Do you have organizational privacy requirements?

      <--- Score

      49. Scope of sensitive information?

      <--- Score

      50. What gets examined?

      <--- Score

      51. Are approval levels defined for contracts and supplements to contracts?

      <--- Score

      52. Do you have a Game as a service success story or case study ready to tell and share?

      <--- Score

      53. Are required metrics defined, what are they?

      <--- Score

      54. Has the direction changed at all during the course of Game as a service? If so, when did it change and why?

      <--- Score

      55. When is the estimated completion date?

      <--- Score

      56. What knowledge or experience is required?

      <--- Score

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

      <--- Score

      58. What scope to assess?

      <--- Score

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

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

      <--- Score

      61. What are the requirements for audit information?

      <--- Score

      62. How do you gather requirements?

      <--- Score

      63. Will team members regularly document their Game as a service work?

      <--- Score

      64. How do you catch Game as a service definition inconsistencies?

      <--- Score

      65. What are the compelling stakeholder reasons for embarking on Game as a service?

      <--- Score

      66. What is the definition of success?

      <--- Score

      67. Has a Game as a service requirement not been met?

      <--- Score

      68. What information should you gather?