What are team's PI objectives?

• A. Team PI Objectives often will map directly to the features but not always
• B. They must map exactly to every feature
• C. They are unrelated to features
• D. They are only used for release budgeting

Answer: (A)

PI Objectives describe the outcomes a team commits to delivering during a Program Increment and provide a clear way to communicate value to stakeholders. They typically map to the features planned for the PI, giving a tangible link between what the team builds and the business goals. However, this mapping isn’t strictly one-to-one: some work like architectural enablers or infrastructure may support several features without being a single feature themselves, and a feature may be split across multiple teams or span multiple objectives. This is why they’re described as often mapping to features but not always—allowing for the realities of estimation, dependencies, and technical work. They’re about what value will be delivered and how progress will be measured, not about budgeting alone, nor are they unrelated to the features being planned.