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.
