the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
96. Has the direction changed at all during the course of Construction Estimating Software? If so, when did it change and why?
<--- Score
97. How would you define Construction Estimating Software leadership?
<--- Score
98. Have all of the relationships been defined properly?
<--- Score
99. Is there a Construction Estimating Software management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
100. Are approval levels defined for contracts and supplements to contracts?
<--- Score
101. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
102. How do you keep key subject matter experts in the loop?
<--- Score
103. What is the definition of success?
<--- Score
104. Is there a clear Construction Estimating Software case definition?
<--- Score
105. Are roles and responsibilities formally defined?
<--- Score
106. Are the Construction Estimating Software requirements complete?
<--- Score
107. What key stakeholder process output measure(s) does Construction Estimating Software leverage and how?
<--- Score
108. What are the Construction Estimating Software tasks and definitions?
<--- Score
109. What defines best in class?
<--- Score
110. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
111. Has/have the customer(s) been identified?
<--- Score
112. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
113. Has your scope been defined?
<--- Score
114. Are accountability and ownership for Construction Estimating Software clearly defined?
<--- Score
115. How often are the team meetings?
<--- Score
116. If substitutes have been appointed, have they been briefed on the Construction Estimating Software goals and received regular communications as to the progress to date?
<--- Score
117. What is out of scope?
<--- Score
118. Is the work to date meeting requirements?
<--- Score
119. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
120. Are there different segments of customers?
<--- Score
121. What sort of initial information to gather?
<--- Score
122. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
123. How are consistent Construction Estimating Software definitions important?
<--- Score
124. When is/was the Construction Estimating Software start date?
<--- Score
125. Do you have organizational privacy requirements?
<--- Score
126. How can the value of Construction Estimating Software be defined?
<--- Score
127. Will a Construction Estimating Software production readiness review be required?
<--- Score
128. Does the scope remain the same?
<--- Score
129. Are the Construction Estimating Software requirements testable?
<--- Score
130. What is in scope?
<--- Score
131. Scope of sensitive information?
<--- Score
132. Who is gathering information?
<--- Score
133. Is Construction Estimating Software linked to key stakeholder goals and objectives?
<--- Score
134. What are the record-keeping requirements of Construction Estimating Software activities?
<--- Score
135. How have you defined all Construction Estimating Software requirements first?
<--- 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 Construction Estimating Software Index at the beginning of the Self-Assessment.
CRITERION #3: MEASURE:
INTENT: Gather the correct data. Measure the current performance
