HKSM

Any document, record, or tangible item produced within a portfolio, program, or project that supports managing the work and communicates information to the team, stakeholders, and leadership.

Key Points

• Exists at portfolio, program, and project levels across the entire life cycle.
• Typical examples include charters, roadmaps, product backlogs, risk registers, reports, and dashboards.
• Purpose is to enable decision making, track progress, and share information transparently.
• Should have clear ownership, version control, and access management to remain accurate and useful.

Example

In an agile project, the team updates a sprint burndown chart each day. This artifact shows remaining work versus time, helping the team adjust their plan and giving stakeholders a clear view of progress.

PMP Example Question

Which option best describes an artifact in the context of portfolio, program, or project work?

1. A meeting used to review progress and remove impediments
2. A document or tangible item produced to support management and information sharing
3. A change request approved by the change control board
4. A role responsible for coordinating team activities

Correct Answer: B — a document or tangible item produced to support management and information sharing

Explanation: An artifact is a created item (e.g., plan, log, report) used to manage the work and communicate with stakeholders; it is not a meeting, role, or specific approval.