LITMIR.BIZ

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

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. When is/was the Collaborative tools start date?

      <--- Score

      105. How and when will the baselines be defined?

      <--- Score

      106. Is the scope of Collaborative tools defined?

      <--- Score

      107. In what way can you redefine the criteria of choice clients have in your category in your favor?

      <--- Score

      108. How do you gather the stories?

      <--- Score

      109. How do you gather Collaborative tools requirements?

      <--- Score

      110. What are the Collaborative tools tasks and definitions?

      <--- Score

      111. Who approved the Collaborative tools scope?

      <--- Score

      112. What is the scope of Collaborative tools?

      <--- Score

      113. Are required metrics defined, what are they?

      <--- Score

      114. How did the Collaborative tools manager receive input to the development of a Collaborative tools improvement plan and the estimated completion dates/times of each activity?

      <--- Score

      115. Is Collaborative tools linked to key stakeholder goals and objectives?

      <--- Score

      116. How do you gather requirements?

      <--- Score

      117. Does the scope remain the same?

      <--- Score

      118. What is the worst case scenario?

      <--- Score

      119. Are there any constraints known that bear on the ability to perform Collaborative tools work? How is the team addressing them?

      <--- Score

      120. What sort of initial information to gather?

      <--- Score

      121. Is there a critical path to deliver Collaborative tools results?

      <--- Score

      122. What critical content must be communicated – who, what, when, where, and how?

      <--- Score

      123. Is data collected and displayed to better understand customer(s) critical needs and requirements.

      <--- Score

      124. Do you all define Collaborative tools in the same way?

      <--- Score

      125. What are the Roles and Responsibilities

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