Score
11. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
12. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
13. Does the team have regular meetings?
<--- Score
14. What Virtual operating system requirements should be gathered?
<--- Score
15. Are the Virtual operating system requirements complete?
<--- Score
16. What happens if Virtual operating system’s scope changes?
<--- Score
17. Do you all define Virtual operating system in the same way?
<--- Score
18. What are the rough order estimates on cost savings/opportunities that Virtual operating system brings?
<--- Score
19. How are consistent Virtual operating system definitions important?
<--- Score
20. What are the Virtual operating system tasks and definitions?
<--- Score
21. Are accountability and ownership for Virtual operating system clearly defined?
<--- Score
22. What critical content must be communicated – who, what, when, where, and how?
<--- Score
23. Is there a clear Virtual operating system case definition?
<--- Score
24. What is the scope of the Virtual operating system effort?
<--- Score
25. How do you manage changes in Virtual operating system requirements?
<--- Score
26. Are the Virtual operating system requirements testable?
<--- Score
27. Why are you doing Virtual operating system and what is the scope?
<--- Score
28. Has/have the customer(s) been identified?
<--- Score
29. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?
<--- Score
30. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
31. How did the Virtual operating system manager receive input to the development of a Virtual operating system improvement plan and the estimated completion dates/times of each activity?
<--- Score
32. How is the team tracking and documenting its work?
<--- Score
33. How would you define Virtual operating system leadership?
<--- Score
34. What is out-of-scope initially?
<--- Score
35. What information do you gather?
<--- Score
36. Have all of the relationships been defined properly?
<--- Score
37. What are the dynamics of the communication plan?
<--- Score
38. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
39. What sources do you use to gather information for a Virtual operating system study?
<--- Score
40. What customer feedback methods were used to solicit their input?
<--- Score
41. What Virtual operating system services do you require?
<--- Score
42. Has the Virtual operating system 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
43. Is Virtual operating system linked to key stakeholder goals and objectives?
<--- Score
44. Has your scope been defined?
<--- Score
45. The political context: who holds power?
<--- Score
46. What gets examined?
<--- Score
47. How do you keep key subject matter experts in the loop?
<--- Score
48. How do you build the right business case?
<--- Score
49. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
50. What baselines are required to be defined and managed?
<--- Score
51. Are required metrics defined, what are they?
<--- Score
52. What is the definition of success?
<--- Score
53. What key stakeholder process output measure(s) does Virtual operating system leverage and how?
<--- Score
