Data Issue and Defect Management Repositories in Project Control

PMBOK v8 Definition

Data repositories for issue and defect management contain issue and defect status, control information, issue and defect resolution, and action item results. These repositories also track labor hours, incurred costs, budgets, and any project cost overruns associated with issues and defects. They function as organizational process assets that are continually updated throughout the project lifecycle.

Why It Matters for the Exam

The PMI exam frequently tests your understanding of where issue and defect data is stored and how it integrates with cost control and performance reporting. Questions appear in the Monitoring and Controlling Process Group, testing your ability to distinguish between data repositories, work performance information, and work performance reports.

Key Points to Remember (for the exam)

• Primary Location: Organizational process assets (not enterprise environmental factors)
• Data Stored: Issue and defect status, control information, resolution details, action item results
• Cost Tracking: Labor hours, incurred costs, budgets, and cost overruns related to issues/defects
• Update Frequency: Continually updated throughout the project
• Related Repositories: Financial data repositories (labor hours, incurred costs, budgets, cost overruns) and historical information/lessons learned repositories
• Common Confusion: Issue and defect data repositories are NOT the same as the issue log or defect register (these are project documents, while repositories are organizational process assets)
• Key Connection: Feeds into work performance information and work performance reports

Typical PMI Exam Example

A project manager notices that defect resolution costs are exceeding the budget. To analyze historical patterns of defect-related cost overruns, the PM should consult the issue and defect management data repositories within the organizational process assets. This data helps perform trend analysis and root cause analysis for the cost variance.

PMI Exam Traps

• Trap: Confusing issue and defect data repositories with the issue log

  • Reality: Issue log is a project document updated during project work; repositories are organizational process assets containing historical data from multiple projects

• Trap: Thinking issue/defect data only contains status information

  • Reality: Repositories also track labor hours, incurred costs, budgets, and cost overruns

• Trap: Treating these repositories as enterprise environmental factors

  • Reality: They are organizational process assets, specifically data repositories within the organization's knowledge base

• Trap: Assuming defect data is only used during quality management

  • Reality: This data feeds into multiple processes including cost control, schedule control, and overall performance reporting

Important PMI Connections

Quick Review Questions

1. When a project manager needs historical data on defect-related cost overruns from previous projects, which organizational process asset should they consult?

2. What four types of information are tracked in issue and defect management data repositories?

3. How often are issue and defect data repositories updated according to PMBOK v8?

4. A project sponsor asks for a summary of defect resolution costs to date. Which output would contain this information: work performance information or work performance reports?

5. What is the key difference between the issue log (project document) and issue and defect management data repositories (organizational process asset)?

PMBOK v8 Reference

Section 2.2.2 - Organizational Process Assets (Data Repositories subsection)