Common Scrum Artifacts Vs Artifacts in Other Agile Frameworks

Correct Answer: Team Backlog

In the SAFe framework, a 'Team Backlog' is a prioritized set of user stories, story points, or backlog items. This artifact is used to guide the team about the work that needs to be done next. It's directly analogous to the Product Backlog in Scrum, so if a Scrum team is struggling with a poorly defined Product Backlog, introducing a Team Backlog could help structure the work more effectively. Now, considering the other options: 'Portfolio Kanban' is a method for visualizing and managing work at the portfolio level, not at the team level. 'PI Objectives' are a set of goals for a Program Increment, which are more broad and strategic, not specifically about organizing team-level work. 'Architectural Runway' refers to the existing code, components, and technical infrastructure needed to implement near-term features without excessive redesign, and it's not directly related to organizing team tasks.

Correct Answer: Kanban Board

The Kanban Board in the Kanban framework is a comparable artifact to the Sprint Backlog in Scrum. Both are used to track progress during a specific period. The Kanban Board provides visualization of all the tasks in various stages of the process, allowing teams to monitor their progress and identify bottlenecks, similar to how the Sprint Backlog is used in Scrum. The 'Product Backlog' is not a correct answer because it’s an Agile artifact for collecting all the work that needs to be done, but it's not used to track progress during a specific time period. 'Velocity Chart' and 'Burndown Chart' are also incorrect, as they are Agile metrics used to track the team's work rate and project progress over time, but they are not artifacts comparable to the Sprint Backlog in Scrum.

Correct Answer: Release Plan

The most comparable XP artifact to a Scrum Product Backlog is the 'Release Plan'. The Release Plan in XP, similar to the Product Backlog in Scrum, maintains a list of required features for the project, their priorities and estimations, and is used to plan for future iterations. On the other hand, the 'Iteration Plan' is closer to the Scrum Sprint Backlog as it defines the tasks for a particular iteration or cycle. 'User Stories' are indeed a part of the planning process but they are the individual tasks or features, not an artifact that holds a grouped list of tasks. 'System Metaphor' is a way to provide a common understanding of the system in XP, but it doesn't provide a backlog or task list, therefore not comparable to the Scrum Product Backlog.