Exam CAPM topic 1 question 364 discussion

Keyword "scrum" = sprint

The question states that the adaptive team is using a Scrum board as an information radiator. An information radiator is a visual tool used in Agile environments to transparently display work status to the team and stakeholders. A Scrum board typically shows the flow of work in a sprint, including: Sprint Backlog: The selected user stories/tasks for the current sprint. Product Backlog (if included): Sometimes visible to provide context, although it's more commonly managed in the product owner’s tool or document. Task status columns: e.g., To Do, In Progress, Done.

Explanation In an adaptive team using Scrum methodology, the scrum board serves as an essential information radiator for tracking project progress and managing workflow. For a project involving the merger of a legacy system from an acquired company, the scrum board should primarily include the product backlog and sprint backlog. Product Backlog: This is a prioritized list of all features, requirements, enhancements, and fixes that constitute the changes to be made to the product. In this case, it would include all the tasks necessary to merge the legacy system successfully. Sprint Backlog: This is a subset of the product backlog, containing the items selected for the current sprint, along with the plan for delivering them. It represents the team’s immediate focus and commitment for the ongoing sprint.

The Scrum board is a visual tool in Agile that tracks work progress. It shows tasks from the product backlog (all project tasks) and the sprint backlog (tasks for the current sprint), helping the team see what’s in progress and what’s done.

Burndown and burnup charts are essential tools in Scrum for tracking progress. They provide visibility into the remaining work (burndown chart) or the completed work (burnup chart) over time. These charts help the team and stakeholders understand if the project is on track to meet its goals and deadlines. Key performance indicators (KPIs) and baseline measurements (option A) are used for monitoring overall project health and performance but are usually tracked separately. Product and sprint backlogs (option B) are managed and updated within the team but are not typically displayed on the scrum board itself. Increments and bottlenecks (option D) are important to identify and address during project execution but are not commonly shown on the scrum board.