PI Planning
ART Sync
ART Backlog Refinement
System Demo
Inspect & Adapt
100

Who schedules and facilitates PI Planning?

The Release Train Engineer

100

Which two sync events are included in the ART Sync?

Scrum of Scrums & PO Sync

100

How often should ART Backlog Refinement occur?

Between 1 - 2 times per week.

100

When should the System Demo occur?

As close to the end of a sprint as possible - ideally, the next day.

100

What are the three key parts of Inspect & Adapt?

- PI System Demo

- Quantitative and Qualitative Measurement

- Problem Solving Workshop

200

When should PI Planning occur?

In the final 2 - 3 days of the IP Sprint.
200

Who facilitates the ART Sync?

RTE or APO

200
Who should facilitate ART Backlog Refinement?

APM

200

Who should attend the System Demo?

- Product Managers

- Product Owners

- Tech Leads

- Business Stakeholders

- RTE

- ART Team Members (when possible)

200

What is the purpose of the PI Retrospective?

To inspect how the work was completed during the PI and adjust ART working norms, guardrails, etc. to resolve issues and continuously improve.

300

Which part of PI Planning is when teams plan work for each sprint in the PI?

Team Breakout Sessions

300

Who are required attendees for the ART Sync?

- RTE

- APO

- SMs

- Tech Leads

300

Which activities are included in ART Backlog Refinement?

- Discovering New Features

- Reviewing and updating backlog item details

- Identifying enablers

- Prioritizing using WSJF or a similar technique

- Deleting aging or no longer relevant work items.

300

Who should facilitate the system demo?

Product Managers and/or Product Owner

300

Who facilitates the Problem Solving Workshop?

RTE

400

How many days should PI Planning take?

2 Days

400

What are the key areas of focus for the ART Sync?

- Execution Progress

- Risks/Dependencies

- Manage PI Scope

- Adjust Priorities

- Future PI Readiness

- Feature Refinement

400
What is the name of the list of criteria that are used to determine if a feature is ready for execution?

Definitions of Ready (DoR) for a Feature

400

What is included in the agenda?

- Review PI Objectives

- Explain and Demo each new feature

- Identify current risks and impediments

- Open discussion, questions and feedback

- Summarize progress, feedback and action items

500

What 5 tasks should be completed at the end of PI Planning?

- Final Plan Review

- ART Risks & Dependencies Review

- Confidence Vote

- Plan rework (if needed)

- Planning Retrospective

500

How often should the ART Sync occur and for how long?

Weekly for 30 - 60 Minutes

500

On which screen in Rally do we represent features that have met the DoR?

The Ready column on the Portfolio Kanban Board for Features.

500

What are some general guidelines or best practices for executing system demos?

- Timeboxed to no more then 1 hour

- Demo responsibilities should be shared across the team

- Only demo working, tested capabilities

- Demo screen snaps where appropriate

M
e
n
u