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

Score

      10. Is scope creep really all bad news?

      <--- Score

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

      <--- Score

      12. What is the scope of the Hardware as a service effort?

      <--- Score

      13. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?

      <--- Score

      14. How do you catch Hardware as a service definition inconsistencies?

      <--- Score

      15. Are audit criteria, scope, frequency and methods defined?

      <--- Score

      16. Is there a clear Hardware as a service case definition?

      <--- Score

      17. Is Hardware as a service required?

      <--- Score

      18. Is Hardware as a service currently on schedule according to the plan?

      <--- Score

      19. How will variation in the actual durations of each activity be dealt with to ensure that the expected Hardware as a service results are met?

      <--- Score

      20. How do you gather the stories?

      <--- Score

      21. How do you build the right business case?

      <--- Score

      22. What Hardware as a service requirements should be gathered?

      <--- Score

      23. What information should you gather?

      <--- Score

      24. What are the compelling stakeholder reasons for embarking on Hardware as a service?

      <--- Score

      25. What knowledge or experience is required?

      <--- Score

      26. Is special Hardware as a service user knowledge required?

      <--- Score

      27. How do you manage unclear Hardware as a service requirements?

      <--- Score

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

      29. Is the scope of Hardware as a service defined?

      <--- Score

      30. How do you manage changes in Hardware as a service requirements?

      <--- Score

      31. What sort of initial information to gather?

      <--- Score

      32. What are the tasks and definitions?

      <--- Score

      33. What customer feedback methods were used to solicit their input?

      <--- Score

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

      <--- 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. Are different versions of process maps needed to account for the different types of inputs?

      <--- Score

      37. Has a team charter been developed and communicated?

      <--- Score

      38. Have specific policy objectives been defined?

      <--- Score

      39. Are required metrics defined, what are they?

      <--- Score

      40. How will the Hardware as a service team and the group measure complete success of Hardware as a service?

      <--- Score

      41. What is in scope?

      <--- Score

      42. Are improvement team members fully trained on Hardware as a service?

      <--- Score

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

      <--- Score

      44. What is the definition of success?

      <--- Score

      45. What sources do you use to gather information for a Hardware as a service study?

      <--- Score

      46. Is it clearly defined in and to your organization what you do?

      <--- Score

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

      <--- Score

      48. Who are the Hardware as a service improvement team members, including Management Leads and Coaches?

      <--- Score

      49. How do you gather requirements?

      <--- Score

      50. What is out of scope?

      <--- Score

      51. Has a Hardware as a service requirement not been met?

      <--- Score

      52. Are task requirements clearly defined?

      <--- Score

      53. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?

      <--- Score

      54. Has the Hardware as a service 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

      55. Is Hardware as a service linked to key stakeholder goals and objectives?

      <--- Score

      56. What is the context?

      <--- Score

      57. What Hardware as a service services do you require?

      <--- Score

      58. Is full participation by members in regularly held team meetings guaranteed?

      <--- Score

      59. Are roles and responsibilities formally defined?

      <--- Score

      60. Are the Hardware as a service requirements testable?

      <--- Score

      61. What are (control) requirements for Hardware as a service Information?

      <--- Score

      62. How do you think the partners involved in Hardware as a service would have defined success?

      <--- Score

      63. What is the scope?

      <--- Score

      64. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?

      <--- Score

      65.