CompTIA Updated PK0-005 Exam Questions and Answers by saul

A velocity chart is a tool used in agile project management to track the progress and performance of a project team over time. It shows the number of features or user stories completed in each iteration or sprint. The planned timeline line represents the expected or ideal velocity, while the actual effort line shows the actual or achieved velocity. By comparing the two lines, the Scrum master can identify any gaps, trends, or issues in the project delivery.

Based on the image, the most likely update that the Scrum master can provide to the senior management team is D. The project is trending ahead of schedule. This is because the actual effort line is above the planned timeline line for most of the time, indicating that the project team is completing more features than expected in each sprint. This means that the project is ahead of schedule and has a positive velocity variance. 

In an Agile environment, when leadership introduces a new strategy that changes what features matter most, the team should reprioritize the backlog. Agile delivery relies on an ordered backlog to ensure the team builds the highest-value work first, and strategic shifts are handled by re-ranking upcoming features so the next iterations deliver what best supports the organization’s direction. CompTIA Project+ covers Agile concepts and emphasizes adapting plans and work sequencing based on stakeholder needs and business priorities.

The other options don’t fit the immediate Agile response. Resource loading is more about capacity assignment across tasks; it may happen after reprioritization, but it’s not the first move when strategy changes. Critical path analysis is a scheduling technique most associated with predictive planning and isn’t the primary mechanism to respond to changing feature priorities in Agile. Contingency reserves address risk buffers for schedule/cost uncertainty, not strategic feature changes.

Therefore, the team should update the backlog order (often with the product owner and stakeholders), clarify acceptance criteria for the newly important features, and then plan upcoming sprints based on that revised priority list.

The Scrum team should break the stories into workable items that can be completed within one sprint, which is a time-boxed period of 7 to 30 days, during which the team delivers a potentially releasable product increment. Breaking the stories into smaller and more manageable items can help the team to estimate them more accurately, plan them more effectively, and deliver them more reliably. Breaking the stories also aligns with the agile principle of delivering working software frequently and satisfying the customer through early and continuous delivery of valuable software.

The other options are not the best steps for the Scrum team to take next. Assigning more resources to complete similar stories in the future may not solve the problem of underestimation, and may introduce additional complexity and communication overhead. Extending the sprint duration when required with the approval of the product owner may compromise the consistency and predictability of the Scrum process, and may delay the feedback and validation from the stakeholders. Releasing the current progress into production and carrying over the rest of the code for the next sprint may result in an incomplete or unstable product increment, and may violate the definition of done, which is a shared understanding of the quality criteria that the product increment must meet. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 5: Project Scope Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 5: Project Scope Management2; The 3 Scrum Roles and Responsibilities Explained3; Implementation of Scrum - 7 Steps for an Effective Process4

The number of items in the backlog can be determined by looking at the “Commitment” column for each sprint in the provided chart. For Sprint 5, there is a commitment of completing 23 items, which is the highest among all sprints. This indicates that there are at least 23 items in the backlog to be worked on. This is consistent with the concept of agile project management, which allows for changes and additions to the project scope based on customer feedback and changing requirements. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 14: Agile Project Management, page 321. CompTIA Project+ Cert Guide: Exam PK0-005, Chapter 9: Agile Project Management, page 287