61. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
62. What customer feedback methods were used to solicit their input?
<--- Score
63. Has the SAN file 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
64. Are there different segments of customers?
<--- Score
65. What is in the scope and what is not in scope?
<--- Score
66. Will a SAN file system production readiness review be required?
<--- Score
67. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
68. What are the record-keeping requirements of SAN file system activities?
<--- Score
69. What information should you gather?
<--- Score
70. What key stakeholder process output measure(s) does SAN file system leverage and how?
<--- Score
71. What are the dynamics of the communication plan?
<--- Score
72. How do you manage changes in SAN file system requirements?
<--- Score
73. Is the SAN file system scope complete and appropriately sized?
<--- Score
74. Why are you doing SAN file system and what is the scope?
<--- Score
75. Who are the SAN file system improvement team members, including Management Leads and Coaches?
<--- Score
76. Is it clearly defined in and to your organization what you do?
<--- Score
77. Are the SAN file system requirements complete?
<--- Score
78. 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
79. Scope of sensitive information?
<--- Score
80. How do you build the right business case?
<--- Score
81. How and when will the baselines be defined?
<--- Score
82. Are roles and responsibilities formally defined?
<--- Score
83. What are the SAN file system tasks and definitions?
<--- Score
84. The political context: who holds power?
<--- Score
85. Are there any constraints known that bear on the ability to perform SAN file system work? How is the team addressing them?
<--- Score
86. Is there any additional SAN file system definition of success?
<--- Score
87. What are the SAN file system use cases?
<--- Score
88. What happens if SAN file system’s scope changes?
<--- Score
89. How will the SAN file system team and the group measure complete success of SAN file system?
<--- Score
90. Who is gathering information?
<--- Score
91. Has a SAN file system requirement not been met?
<--- Score
92. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
93. What is the worst case scenario?
<--- Score
94. What constraints exist that might impact the team?
<--- Score
95. How often are the team meetings?
<--- Score
96. How do you gather requirements?
<--- Score
97. What critical content must be communicated – who, what, when, where, and how?
<--- Score
98. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
99. Has your scope been defined?
<--- Score
100. What is the scope of SAN file system?
<--- Score
101. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
102. What are the compelling stakeholder reasons for embarking on SAN file system?
<--- Score
103. Has/have the customer(s) been identified?
<--- Score
104. Are audit criteria, scope, frequency and methods defined?
<--- Score
105. Is there a completed
