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

Are improvement team members fully trained on Firmware as a Service?

      <--- Score

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

      <--- Score

      10. Has a Firmware as a Service requirement not been met?

      <--- Score

      11. Where can you gather more information?

      <--- Score

      12. What information do you gather?

      <--- Score

      13. Is the scope of Firmware as a Service defined?

      <--- Score

      14. What scope to assess?

      <--- Score

      15. How did the Firmware as a Service manager receive input to the development of a Firmware as a Service improvement plan and the estimated completion dates/times of each activity?

      <--- Score

      16. What are the dynamics of the communication plan?

      <--- Score

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

      <--- Score

      18. The political context: who holds power?

      <--- Score

      19. What are the compelling stakeholder reasons for embarking on Firmware as a Service?

      <--- Score

      20. Who is gathering information?

      <--- Score

      21. What are the record-keeping requirements of Firmware as a Service activities?

      <--- Score

      22. How do you catch Firmware as a Service definition inconsistencies?

      <--- Score

      23. How have you defined all Firmware as a Service requirements first?

      <--- Score

      24. How do you gather the stories?

      <--- Score

      25. What constraints exist that might impact the team?

      <--- Score

      26. Do you all define Firmware as a Service in the same way?

      <--- Score

      27. Will team members regularly document their Firmware as a Service work?

      <--- Score

      28. What is the worst case scenario?

      <--- Score

      29. What critical content must be communicated – who, what, when, where, and how?

      <--- Score

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

      <--- Score

      31. What are the core elements of the Firmware as a Service business case?

      <--- Score

      32. What information should you gather?

      <--- Score

      33. What was the context?

      <--- Score

      34. Is the Firmware as a Service scope manageable?

      <--- Score

      35. What system do you use for gathering Firmware as a Service information?

      <--- Score

      36. What is the scope of the Firmware as a Service effort?

      <--- Score

      37. Has everyone on the team, including the team leaders, been properly trained?

      <--- Score

      38. Has the Firmware 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

      39. What are the rough order estimates on cost savings/opportunities that Firmware as a Service brings?

      <--- Score

      40. Are there different segments of customers?

      <--- Score

      41. What Firmware as a Service services do you require?

      <--- Score

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

      <--- Score

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

      44. Have specific policy objectives been defined?

      <--- Score

      45. Have all basic functions of Firmware as a Service been defined?

      <--- Score

      46. Who approved the Firmware as a Service scope?

      <--- Score

      47. What is the scope of the Firmware as a Service work?

      <--- Score

      48. What is out of scope?

      <--- Score

      49. How and when will the baselines be defined?

      <--- Score

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

      <--- Score

      51. How does the Firmware as a Service manager ensure against scope creep?

      <--- Score

      52. What are the tasks and definitions?

      <--- Score

      53. Has the direction changed at all during the course of Firmware as a Service? If so, when did it change and why?

      <--- Score

      54. How can the value of Firmware as a Service be defined?

      <--- Score

      55. Is Firmware as a Service linked to key stakeholder goals and objectives?

      <--- Score

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

      <--- Score

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

      <--- Score

      58. Do you have a Firmware as a Service success story or case study ready to tell and share?

      <--- Score

      59. What are (control) requirements for Firmware as a Service Information?

      <--- Score

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

      <--- Score

      61. Is there any additional Firmware as a Service definition of success?

      <--- Score

      62. Has a team charter been developed and communicated?

      <--- Score

      63. How do you manage scope?

      <--- Score

      64. Is there a critical path to deliver Firmware as a Service results?

      <--- Score