Explanation/Reference:
Explanation:
4.4.1.5 Work Performance Information
Work performance information is the performance data collected from various controlling processes, analyzed in context, and integrated based on relationships across areas. Thus work performance data has been transformed into work performance information. Data in itself cannot be used in the decision-making process as it has only out-of-context meaning. Work performance information, however, is correlated and contextualized, and provides a sound foundation for project decisions.
Work performance information is circulated through communication processes. Examples of performance information are status of deliverables, implementation status for change requests, and forecasted estimates to complete.
9.4.1.4 Issue Log
Issues arise in the course of managing the project team. An issue log can be used to document and monitor who is responsible for resolving specific issues by a target date.

Explanation/Reference:
Explanation:
Fixed-price contracts. This category of contracts involves setting a fixed total price for a defined product, service, or result to be provided. Fixed-price contracts may also incorporate financial incentives for achieving or exceeding selected project objectives, such as schedule delivery dates, cost and technical performance, or anything that can be quantified and subsequently measured. Sellers under fixed-price contracts are legally obligated to complete such contracts, with possible financial damages if they do not.
Under the fixed-price arrangement, buyers need to precisely specify the product or services being procured. Changes in scope may be accommodated, but generally with an increase in contract price.

Explanation/Reference:
Explanation:
5.1.3.2 Requirements Management Plan
The requirements management plan is a component of the project management plan that describes how requirements will be analyzed, documented, and managed. The phase-to-phase relationship, described in Section 2.4.2.1, strongly influences how requirements are managed. The project manager chooses the most effective relationship for the project and documents this approach in the requirements management plan. Many of the requirements management plan components are based on that relationship.
Components of the requirements management plan can include, but are not limited to:
* How requirements activities will be planned, tracked, and reported;
* Configuration management activities such as: how changes to the product will be initiated, how impacts will be analyzed, how they will be traced, tracked, and reported, as well as the authorization levels required to approve these changes;
* Requirements prioritization process;
* Product metrics that will be used and the rationale for using them; and
* Traceability structure to reflect which requirement attributes will be captured on the traceability matrix.