PK0-005 Tools and Documentation Practice Question
A project team is using Jira for an Agile project. Which TWO artefacts are typically managed within Jira for sprint planning and tracking? (Choose two.)
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Product backlog
The product backlog (A) is correct because Jira manages it as the ordered list of epics, stories, bugs, and tasks from which sprint planning draws items, and it is the primary artifact refined and prioritized before each sprint. The sprint backlog (E) is correct because Jira represents it as the set of issues committed to a specific sprint, visible on the active sprint board and tracked through the sprint's lifecycle. Burndown chart (B) and velocity (D) are not the artifacts being managed here; they are reports/metrics that Jira generates from the underlying backlog and sprint data rather than artifacts planned and maintained in the tool. The stakeholder register (C) is a project management document typically maintained outside Jira (e.g., in a PMIS or spreadsheet) and is not a Jira-managed sprint planning or tracking artifact.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Product backlog
Why this is correct
The product backlog is the ordered list of all desired work, and Jira manages it as the master requirements artefact feeding sprint planning. It satisfies the stem's requirement for an artefact used in Agile planning and tracking.
- ✗
Burndown chart
Why it's wrong here
A burndown chart is a generated reporting view of remaining work over time, not a planning artefact a team creates and manages in Jira for sprint planning. It is tempting because Jira produces burndown charts from sprint data, but the question asks for managed artefacts such as the sprint backlog and user stories.
- ✗
Stakeholder register
Why it's wrong here
The stakeholder register is a project management document recording interested parties, their influence and engagement, and is not an Agile sprint planning or tracking artefact held in Jira. It is tempting because it is a genuine PMBOK deliverable, but Jira boards track backlog items, sprints and their progress instead.
- ✗
Velocity
Why it's wrong here
Velocity is a derived metric calculated from completed story points across past sprints; it is reported by Jira rather than being an artefact the team manages for planning and tracking. It is tempting because velocity informs sprint capacity, but the question asks for managed artefacts like the sprint backlog and user stories.
- ✓
Sprint backlog
Why this is correct
The sprint backlog is a core Scrum artefact that Jira manages natively, holding the subset of product backlog items selected for the current sprint plus their tasks. This directly satisfies the stem's sprint planning and tracking requirement, since Jira's active sprint board visualises and updates these items throughout the iteration.
Go deeper
Related to this question
About these practice questions
One of 954 original PK0-005 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PK0-005 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PK0-005 exam.