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
65. What gets examined?
<--- Score
66. Does the scope remain the same?
<--- Score
67. How will variation in the actual durations of each activity be dealt with to ensure that the expected Firmware as a Service results are met?
<--- Score
68. What sources do you use to gather information for a Firmware as a Service study?
<--- Score
69. What Firmware as a Service requirements should be gathered?
<--- Score
70. Does the team have regular meetings?
<--- Score
71. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
72. 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
73. How do you manage unclear Firmware as a Service requirements?
<--- Score
74. Is Firmware as a Service required?
<--- Score
75. How is the team tracking and documenting its work?
<--- Score
76. Have all of the relationships been defined properly?
<--- Score
77. Do you have organizational privacy requirements?
<--- Score
78. Is there a clear Firmware as a Service case definition?
<--- Score
79. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
80. What sort of initial information to gather?
<--- Score
81. Has/have the customer(s) been identified?
<--- Score
82. What is the scope of Firmware as a Service?
<--- Score
83. Are resources adequate for the scope?
<--- Score
84. What would be the goal or target for a Firmware as a Service’s improvement team?
<--- Score
85. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
86. What is the scope?
<--- Score
87. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
88. What happens if Firmware as a Service’s scope changes?
<--- Score
89. What is the context?
<--- Score
90. What defines best in class?
<--- Score
91. How would you define Firmware as a Service leadership?
<--- Score
92. Is it clearly defined in and to your organization what you do?
<--- Score
93. Who defines (or who defined) the rules and roles?
<--- Score
94. What is out-of-scope initially?
<--- Score
95. How often are the team meetings?
<--- Score
96. How do you gather Firmware as a Service requirements?
<--- Score
97. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
98. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
99. Is the Firmware as a Service scope complete and appropriately sized?
<--- Score
100. Are customer(s) identified and segmented according to their different needs and requirements?
