What information should you gather?
<--- Score
97. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
98. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
99. What are the compelling stakeholder reasons for embarking on Stakeholder engagement software?
<--- Score
100. Do you have a Stakeholder engagement software success story or case study ready to tell and share?
<--- Score
101. Is there a clear Stakeholder engagement software case definition?
<--- Score
102. Are the Stakeholder engagement software requirements testable?
<--- Score
103. What is in the scope and what is not in scope?
<--- Score
104. How do you hand over Stakeholder engagement software context?
<--- Score
105. What defines best in class?
<--- Score
106. How and when will the baselines be defined?
<--- Score
107. Will a Stakeholder engagement software production readiness review be required?
<--- Score
108. How often are the team meetings?
<--- Score
109. What is the definition of success?
<--- Score
110. Have specific policy objectives been defined?
<--- Score
111. How do you manage changes in Stakeholder engagement software requirements?
<--- Score
112. Is the Stakeholder engagement software scope complete and appropriately sized?
<--- Score
113. What Stakeholder engagement software services do you require?
<--- Score
114. Are there any constraints known that bear on the ability to perform Stakeholder engagement software work? How is the team addressing them?
<--- Score
115. What intelligence can you gather?
<--- Score
116. Is the Stakeholder engagement software scope manageable?
<--- Score
117. What are (control) requirements for Stakeholder engagement software Information?
<--- Score
118. Are approval levels defined for contracts and supplements to contracts?
<--- Score
119. How is the team tracking and documenting its work?
<--- Score
120. How do you think the partners involved in Stakeholder engagement software would have defined success?
<--- Score
121. How does the Stakeholder engagement software manager ensure against scope creep?
<--- Score
122. What are the requirements for audit information?
<--- Score
123. What system do you use for gathering Stakeholder engagement software information?
<--- Score
124. What happens if Stakeholder engagement software’s scope changes?
<--- Score
125. How are consistent Stakeholder engagement software definitions important?
<--- Score
126. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
127. Is special Stakeholder engagement software user knowledge required?
<--- Score
128. Has the direction changed at all during the course of Stakeholder engagement software? If so, when did it change and why?
<--- Score
129. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
130. Is it clearly defined in and to your organization what you do?
<--- Score
131. What sort of initial information to gather?
<--- Score
132. Is Stakeholder engagement software currently on schedule according to the plan?
<--- Score
Add up total points for this section: _____ = Total points for this section
Divided by: ______ (number of statements answered) = ______ Average score for this section
Transfer your score to the Stakeholder engagement software Index at the beginning of the Self-Assessment.
CRITERION #3: MEASURE:
INTENT: Gather the correct data. Measure the current performance and evolution of the situation.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. How are costs allocated?
