252. For smaller projects, what is the supporting documentation that could be used to support the details used in establishing project estimates such as assumptions, constraints, level of detail, ranges, and confidence levels?

• Basis of estimates.

• Cost estimates.

• Duration estimates.

• Resource estimates.

253. A documented economic feasibility study used to establish validity of the benefits of a selected component lacking sufficient definition and that is used as a basis for the authorization of further project management activities.

• Business need.

• Business case.

• Benefits realization.

• Case study.

254. A technique for systematically reviewing materials using a list for accuracy and completeness.

• Constraints analysis.

• Assumptions analysis.

• Checklist analysis.

• Flowchart analysis.

255. An analytical technique to determine the information needs of the project stakeholders through interviews, workshops, study of lessons learned from previous projects, etc.

• Communication requirements technology

• Project management information system (PMIS).

• Information management system (IMS).

• Communication requirements analysis.

256. Time or money allocated in the schedule or cost baseline for known risks with active response strategies.

• Management reserve.

• Contingency reserve.

• Top-down reserve.

• Risk allocation reserve.

257. All costs incurred over the life of the product by investment in preventing nonconformance to requirements, appraisal of the product or service for conformance to requirements, and failure to meet requirements.

• Budget at completion (BAC).

• Cost of errors (COE).

• Cost of quality (COQ).

• Total cost (TC).

258. Any activity on the critical path in a project schedule.

• Critical chain activity.

• Positive slack activity.

• Critical path activity.

• Negative slack activity.

259. The amount of time that a schedule activity can be delayed or extended from its early start date without delaying the project finish date or violating a schedule constraint

• Free lag.

• Free float.

• Negative float.

• Total float.

260. An adaptive project life cycle in which the deliverable is produced through a series of iterations that successively add functionality within a predetermined time frame. The deliverable contains the necessary and sufficient capability to be considered complete only after the final iteration.

• Incremental life cycle.

• Waterfall life cycle.

• Critical path life cycle.

• Program life cycle.

261. An adaptive project life cycle in which the deliverable matures through a series of repeated cycles. The deliverable contains the necessary and sufficient capability to be considered complete at the end of each cycle. Each repeated cycle further enhances the capability of the deliverable.

• Project life cycle.

• Iterative life cycle.

• Product life cycle.

• Business analysis life cycle.