PMI-ACP Exam Dumps - PMI Agile Certified Practitioner (PMI-ACP)

A product roadmap is a strategic plan that outlines the vision for the product, the business objectives that need to be achieved, and the timeframes for delivering key milestones or features. It provides a high-level overview of the product's development, aligning the team and stakeholders on the product's direction and the expected delivery timeline.

Product vision defines what the product aims to achieve and the value it will deliver to customers or the business.

Business objectives outline what the product aims to accomplish in terms of business impact, like increasing revenue or improving customer satisfaction.

Timeframes indicate when key milestones or releases are planned to occur, ensuring that progress can be tracked and expectations set.

This high-level structure is essential for guiding product development and keeping stakeholders aligned, without delving into the specific details of design or project management, which are more suited for other planning documents.

A spike is a time-boxed research activity used in Agile to explore uncertainties or unknowns, such as dependencies in this case. If the product owner is unsure about the risks related to migrating to a new version of a database, they can request a spike from the team. This will allow the team to investigate the dependencies, assess potential risks, and gather the necessary information to move forward with the user story. This helps reduce uncertainty and makes it easier to make informed decisions about the next steps.

Step 1: Identify Total Story Points in the Backlog

From the backlog table:

Total story points = 6 + 4 + 8 + 4 + 21 + 7 + 5 + 9 + 3 + 5 = 72

Step 2: Determine the Team's Velocity

The risk register mentions a burn reduction of 1 story point per sprint from sprint 4 to sprint 6 due to a holiday schedule. However, assuming a normal velocity of 5 story points per sprint, we can estimate sprint completion.

Normal sprint velocity: 5 story points per sprint

Reduced velocity for sprints 4-6: 4 story points per sprint

Step 3: Calculate Total Sprints Needed

First 3 sprints: 5 points per sprint → 5 × 3 = 15 story points completed

Sprints 4-6: 4 points per sprint → 4 × 3 = 12 story points completed

Remaining story points after sprint 6: 72 - (15 + 12) = 45 story points

Remaining sprints needed at normal velocity (5 story points per sprint): 45 ÷ 5 = 9 sprints

Total Sprints Required

Sprints 1-6: Already planned.

Additional 9 sprints needed.

Total sprints to complete the backlog: 6 + 9 = 15 sprints.

In this scenario, the team faced delays due to the absence of a single tester. To prevent similar issues in the future, the team should work on becoming more cross-functional, where team members are skilled in multiple areas (e.g., testing multiple data sources). Encouraging team members to become general specialists reduces bottlenecks and dependency on a single individual, ensuring that the team can continue to make progress even if someone is unavailable. This fosters greater flexibility and resilience within the team, improving overall efficiency and minimizing disruptions in future implementations.

The first step for the Scrum Master should be to identify the key stakeholders as early as possible. Understanding who the key stakeholders are, such as internal or external individuals or groups that have an interest in the project, allows the team to prioritize communication and engagement with them from the outset. Identifying stakeholders early ensures that their needs and expectations can be taken into account when planning and executing the project. This helps avoid misunderstandings or misaligned goals later in the project.