Which of the following best describes PI Objectives mapping?

• A. They often map directly to features but not always
• B. They must map exactly to all features
• C. They are unrelated to features
• D. They replace features

Answer: (A)

PI Objectives mapping focuses on linking the planned value in a Program Increment to the work that delivers it. Features are the main units of value, and teams aim to show which features (or groups of features) support each objective. This mapping is not a strict one-to-one rule. In practice, an objective may be satisfied by several features, and a single feature can contribute to multiple objectives. There are also enablers and technical work that support a business objective without being a direct feature themselves. The goal is to communicate how the increment will realize value, which is why direct, explicit mappings are common but not mandatory for every case.

That’s why the option describing mapping to features often, but not always, aligns best. The other possibilities imply rigid one-to-one mappings, or that PI Objectives are unrelated or replace features, which isn’t how PI Objectives are used in SAFe.