Score
61. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
62. What information do you gather?
<--- Score
63. What key stakeholder process output measure(s) does Collaborative tools leverage and how?
<--- Score
64. Are audit criteria, scope, frequency and methods defined?
<--- Score
65. Where can you gather more information?
<--- Score
66. What Collaborative tools requirements should be gathered?
<--- Score
67. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
68. Are roles and responsibilities formally defined?
<--- Score
69. Is there a Collaborative tools management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
70. How would you define Collaborative tools leadership?
<--- Score
71. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
72. What are the requirements for audit information?
<--- Score
73. Who is gathering Collaborative tools information?
<--- Score
74. Will team members perform Collaborative tools work when assigned and in a timely fashion?
<--- Score
75. What is in the scope and what is not in scope?
<--- Score
76. What information should you gather?
<--- Score
77. When is the estimated completion date?
<--- Score
78. What is in scope?
<--- Score
79. Have all basic functions of Collaborative tools been defined?
<--- Score
80. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
81. How have you defined all Collaborative tools requirements first?
<--- Score
82. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
83. Is scope creep really all bad news?
<--- Score
84. Will a Collaborative tools production readiness review be required?
<--- Score
85. Is special Collaborative tools user knowledge required?
<--- Score
86. Is the Collaborative tools scope manageable?
<--- Score
87. Are all requirements met?
<--- Score
88. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
89. What is the context?
<--- Score
90. How do you think the partners involved in Collaborative tools would have defined success?
<--- Score
91. What knowledge or experience is required?
<--- Score
92. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
93. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
94. Are approval levels defined for contracts and supplements to contracts?
<--- Score
95. Has your scope been defined?
<--- Score
96. Is the Collaborative tools scope complete and appropriately sized?
<--- Score
97. Has/have the customer(s) been identified?
<--- Score
98. Who defines (or who defined) the rules and roles?
<--- Score
99. Has the Collaborative tools 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
100. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
101. What is the scope of the Collaborative tools effort?
<--- Score
102. 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
103. Will team members regularly document their Collaborative tools work?
<--- Score
104.
