Скачать книгу

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

      <--- Score

      123. What specifically is the problem? Where does it occur? When does it occur? What is its extent?

      <--- Score

      124. Is there a Firmware as a Service management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?

      <--- Score

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

      <--- Score

      126. Are all requirements met?

      <--- Score

      127. Is Firmware as a Service currently on schedule according to the plan?

      <--- Score

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

      <--- Score

      129. Who is gathering Firmware as a Service information?

      <--- Score

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

      <--- Score

      131. Has your scope been defined?

      <--- Score

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

      <--- Score

      133. How do you keep key subject matter experts in the loop?

      <--- Score

      134. If substitutes have been appointed, have they been briefed on the Firmware as a Service goals and received regular communications as to the progress to date?

      <--- Score

      135. How will the Firmware as a Service team and the group measure complete success of Firmware as a Service?

      <--- Score

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

      <--- Score

      Add up total points for this section: _____ = Total points for this section

      Divided by: ______ (number of statements answered) = ______ Average score for this section

      Transfer your score to the Firmware as a Service Index at the beginning of the Self-Assessment.

      CRITERION #3: MEASURE:

      INTENT: Gather the correct data. Measure the current performance and evolution of the situation.

      In my belief, the answer to this question is clearly defined:

      5 Strongly Agree

      4 Agree

      3 Neutral

      2 Disagree

      1 Strongly Disagree

      1. Are supply costs steady or fluctuating?

      <--- Score

      2. Where is it measured?

      <--- Score

      3. When are costs are incurred?

      <--- Score

      4. How do you verify if Firmware as a Service is built right?

      <--- Score

      5. How can you measure Firmware as a Service in a systematic way?

      <--- Score

      6. Do you aggressively reward and promote the people who have the biggest impact on creating excellent Firmware as a Service services/products?

      <--- Score

      7. What would be a real cause for concern?

      <--- Score

      8. How do you measure efficient delivery of Firmware as a Service services?

      <--- Score

      9. Which Firmware as a Service impacts are significant?

      <--- Score

      10. What causes innovation to fail or succeed in your organization?

      <--- Score

      11. Does management have the right priorities among projects?

      <--- Score

      12. Are the Firmware as a Service benefits worth its costs?

      <--- Score

      13. What relevant entities could be measured?

      <--- Score

      14. How will your organization measure success?

      <--- Score

      15. How can you manage cost down?

      <--- Score

      16. How will measures be used to manage and adapt?

      <--- Score

      17. What tests verify requirements?

      <--- Score

      18. Is the solution cost-effective?

      <--- Score

      19. What disadvantage does this cause for the user?

      <--- Score

      20. Are actual costs in line with budgeted costs?

      <--- Score

      21. What is the total cost related to deploying Firmware as a Service, including any consulting or professional services?

      <--- Score

      22. What causes extra work or rework?

      <--- Score

      23. Do you have an issue in getting priority?

      <--- Score

      24. Is the cost worth the Firmware as a Service effort ?

      <--- Score

      25. How sensitive must the Firmware as a Service strategy be to cost?

      <--- Score

      26. Are there measurements based on task performance?

      <--- Score

      27. Are the measurements objective?

      <--- Score

      28. At what cost?

      <--- Score

      29. What could cause delays in the schedule?

      <--- Score

      30. What are your operating costs?

      <--- Score

      31. What are the costs of delaying Firmware as a Service action?

      <--- Score

      32. Why do the measurements/indicators matter?

      <--- Score

      33. How do you measure variability?

      <--- Score

      34. Where is the cost?

      <--- Score

      35. Do the benefits outweigh the costs?

      <--- Score

      36. What are the costs of reform?

      <--- Score

      37. How can you measure the performance?

      <--- Score

      38.

Скачать книгу