Why is it helpful to communicate newly refined Features and Enablers to the teams dur-ing the current Program Increment (PI)?

Teams can prepare backlogs, give feedback to the Product Owner/Product Man-agement/System Architect, and begin looking at dependencies, impediments, and knowledge building
Teams can review the Features and Enablers so they have an understanding of the Roadmap for the next PI
Teams can establish face-to-face communication across all team members and stakeholders
Teams can help support overall product integrity and facilitate working agree-merits during PI Planning

Answer(s): A

Why is the problem-solving workshop more effective than traditional lessons learned documents?

Collaboration over documentation is a key recommendation of the Agile Manifes-to
Workshops are more engaging than document writing
It makes improvements actionable through backlog items for the next Program Increment

Answer(s): C

Which two activities take place during Team Breakout #1 on the first day of Program In-crement (PI) Planning? (Choose two.)

Risks on the teams' planning boards are resolved by the Release Train Engineer
Teams use color-coding for their backlog items as a reminder that they are re-quired to have all backlog item types on their planning boards
Draft objectives and uncommitted objectives are written
All teams' planning boards are visible and use the same color-coding
Draft objectives are written but do not include exploration Enablers

Answer(s): C,D