PMI Agile Certified Practitioner (ACP) Practice Exam

Disable ads (and more) with a membership for a one time $2.99 payment

Prepare for the PMI Agile Certified Practitioner Exam with multiple choice questions and flashcards. Each question includes explanations to help you gear up for your test!

Each practice test/flash card set has 50 randomly selected questions from a bank of over 500. You'll get a new set of questions each time!

Practice this question and more.


How is the term "artifact" commonly used in Agile?

  1. To refer to a meeting type

  2. To identify physical project deliverables

  3. To describe outputs from Agile processes

  4. To categorize team roles

The correct answer is: To describe outputs from Agile processes

In Agile, the term "artifact" is commonly used to describe outputs from Agile processes. Artifacts are essential components that provide valuable information to all stakeholders, helping to guide and inform the project. These artifacts can include various documents and work items, such as the product backlog, sprint backlog, and increment, which encapsulate the work completed and the progress made throughout the project. By focusing on artifacts, teams can ensure transparency and facilitate communication. They serve as vital tools for tracking progress, understanding team velocity, and ensuring that everyone involved has access to the same information. This overarching concept emphasizes the importance of iterative improvements and feedback within Agile methodologies, reinforcing how artifacts contribute to the adaptation and evolution of a project. The other options do not align with the common understanding of artifacts in Agile. Meeting types pertain to collaboration and communication formats rather than output, while physical project deliverables might be part of the artifacts but do not capture the full breadth of what "artifact" means in Agile. Additionally, categorizing team roles does not relate to artifacts, as it focuses on the structure and responsibilities within a team, not the tangible outputs that emerge from Agile processes.