Goal templates — Scrum Project Management — P5
Scrum Project Management · Scrum Project Management · P5 — Expert Professional
These are canon-derived frames, not advice: every line is either verbatim JobFrame canon text or a fixed template wrapping it. ⟨target⟩ / ⟨baseline⟩ / ⟨date⟩ are placeholders for the manager to fill in. Nothing here is generated by AI — rows are omitted, never invented, when the canon lacks the underlying field.
SMART goals
One row per canon core output / responsibility this level owns.
JFM responsibility (P5)
Coaches an Agile Release Train (team of teams, ~50–125 people) as Release Train Engineer, or leads organization-level Agile coaching to create high-performing Scrum Masters.
- Specific
- Deliver: "Coaches an Agile Release Train (team of teams, ~50–125 people) as Release Train Engineer, or leads organization-level Agile coaching to create high-performing Scrum Masters."
- Measurable
- Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
- Achievable
- Scoped to this level's jfm complexity/problem-solving rubric: "Addresses strategic, often intangible organizational agility issues with high independence; optimizes value flow and removes enterprise-level barriers to agility."
- Relevant
- Advances the Scrum Project Management · Scrum Project Management mandate for a P5 — Expert Professional.
- Time-bound
- ⟨date⟩
JFM responsibility (P5)
Manages and optimizes the flow of value through the ART using information radiators and Program and Solution Kanbans.
- Specific
- Deliver: "Manages and optimizes the flow of value through the ART using information radiators and Program and Solution Kanbans."
- Measurable
- Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
- Achievable
- Scoped to this level's jfm complexity/problem-solving rubric: "Addresses strategic, often intangible organizational agility issues with high independence; optimizes value flow and removes enterprise-level barriers to agility."
- Relevant
- Advances the Scrum Project Management · Scrum Project Management mandate for a P5 — Expert Professional.
- Time-bound
- ⟨date⟩
JFM responsibility (P5)
Facilitates the PI planning event and establishes annual calendars for Program Increments and iterations.
- Specific
- Deliver: "Facilitates the PI planning event and establishes annual calendars for Program Increments and iterations."
- Measurable
- Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
- Achievable
- Scoped to this level's jfm complexity/problem-solving rubric: "Addresses strategic, often intangible organizational agility issues with high independence; optimizes value flow and removes enterprise-level barriers to agility."
- Relevant
- Advances the Scrum Project Management · Scrum Project Management mandate for a P5 — Expert Professional.
- Time-bound
- ⟨date⟩
JFM responsibility (P5)
Handles cross-team orchestration, dependency management, and program-level coordination across the train.
- Specific
- Deliver: "Handles cross-team orchestration, dependency management, and program-level coordination across the train."
- Measurable
- Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
- Achievable
- Scoped to this level's jfm complexity/problem-solving rubric: "Addresses strategic, often intangible organizational agility issues with high independence; optimizes value flow and removes enterprise-level barriers to agility."
- Relevant
- Advances the Scrum Project Management · Scrum Project Management mandate for a P5 — Expert Professional.
- Time-bound
- ⟨date⟩
JFM responsibility (P5)
Works closely with leadership teams to remove impediments to agility at the organizational level and advance enterprise-wide Agile initiatives.
- Specific
- Deliver: "Works closely with leadership teams to remove impediments to agility at the organizational level and advance enterprise-wide Agile initiatives."
- Measurable
- Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
- Achievable
- Scoped to this level's jfm complexity/problem-solving rubric: "Addresses strategic, often intangible organizational agility issues with high independence; optimizes value flow and removes enterprise-level barriers to agility."
- Relevant
- Advances the Scrum Project Management · Scrum Project Management mandate for a P5 — Expert Professional.
- Time-bound
- ⟨date⟩
Copy / print as textshow ▾hide ▴
1. Coaches an Agile Release Train (team of teams, ~50–125 people) as Release Train Engineer, or leads organization-level Agile coaching to create high-performing Scrum Masters. [source: JFM responsibility (P5)] Specific: Deliver: "Coaches an Agile Release Train (team of teams, ~50–125 people) as Release Train Engineer, or leads organization-level Agile coaching to create high-performing Scrum Masters." Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩. Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Addresses strategic, often intangible organizational agility issues with high independence; optimizes value flow and removes enterprise-level barriers to agility." Relevant: Advances the Scrum Project Management · Scrum Project Management mandate for a P5 — Expert Professional. Time-bound: ⟨date⟩ 2. Manages and optimizes the flow of value through the ART using information radiators and Program and Solution Kanbans. [source: JFM responsibility (P5)] Specific: Deliver: "Manages and optimizes the flow of value through the ART using information radiators and Program and Solution Kanbans." Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩. Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Addresses strategic, often intangible organizational agility issues with high independence; optimizes value flow and removes enterprise-level barriers to agility." Relevant: Advances the Scrum Project Management · Scrum Project Management mandate for a P5 — Expert Professional. Time-bound: ⟨date⟩ 3. Facilitates the PI planning event and establishes annual calendars for Program Increments and iterations. [source: JFM responsibility (P5)] Specific: Deliver: "Facilitates the PI planning event and establishes annual calendars for Program Increments and iterations." Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩. Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Addresses strategic, often intangible organizational agility issues with high independence; optimizes value flow and removes enterprise-level barriers to agility." Relevant: Advances the Scrum Project Management · Scrum Project Management mandate for a P5 — Expert Professional. Time-bound: ⟨date⟩ 4. Handles cross-team orchestration, dependency management, and program-level coordination across the train. [source: JFM responsibility (P5)] Specific: Deliver: "Handles cross-team orchestration, dependency management, and program-level coordination across the train." Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩. Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Addresses strategic, often intangible organizational agility issues with high independence; optimizes value flow and removes enterprise-level barriers to agility." Relevant: Advances the Scrum Project Management · Scrum Project Management mandate for a P5 — Expert Professional. Time-bound: ⟨date⟩ 5. Works closely with leadership teams to remove impediments to agility at the organizational level and advance enterprise-wide Agile initiatives. [source: JFM responsibility (P5)] Specific: Deliver: "Works closely with leadership teams to remove impediments to agility at the organizational level and advance enterprise-wide Agile initiatives." Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩. Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Addresses strategic, often intangible organizational agility issues with high independence; optimizes value flow and removes enterprise-level barriers to agility." Relevant: Advances the Scrum Project Management · Scrum Project Management mandate for a P5 — Expert Professional. Time-bound: ⟨date⟩
OKRs
Objectives from this level's core outputs; key results only where a real dimension or capability backs them.
JFM responsibility (P5)
Coaches an Agile Release Train (team of teams, ~50–125 people) as Release Train Engineer, or leads organization-level Agile coaching to create high-performing Scrum Masters.
- From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Coaches an Agile Release Train (team of teams, ~50–125 people) as Release Train Engineer, or leads organization-level Agile coaching to create high-performing Scrum Masters."
- Evidence at this level's scope bar: "Multiple systems or a technical domain" — ⟨target⟩ by ⟨date⟩
JFM responsibility (P5)
Manages and optimizes the flow of value through the ART using information radiators and Program and Solution Kanbans.
- From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Manages and optimizes the flow of value through the ART using information radiators and Program and Solution Kanbans."
- Evidence at this level's autonomy bar: "Sets direction within the domain" — ⟨target⟩ by ⟨date⟩
JFM responsibility (P5)
Facilitates the PI planning event and establishes annual calendars for Program Increments and iterations.
- From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Facilitates the PI planning event and establishes annual calendars for Program Increments and iterations."
- Evidence at this level's complexity bar: "Novel, high-ambiguity problems; establishes the approach" — ⟨target⟩ by ⟨date⟩
JFM responsibility (P5)
Handles cross-team orchestration, dependency management, and program-level coordination across the train.
- From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Handles cross-team orchestration, dependency management, and program-level coordination across the train."
- Evidence at this level's impact bar: "Org / multi-team outcomes" — ⟨target⟩ by ⟨date⟩
JFM responsibility (P5)
Works closely with leadership teams to remove impediments to agility at the organizational level and advance enterprise-wide Agile initiatives.
- From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Works closely with leadership teams to remove impediments to agility at the organizational level and advance enterprise-wide Agile initiatives."
- Evidence at this level's decision rights bar: "Authority over a technical domain" — ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾hide ▴
Objective 1: Coaches an Agile Release Train (team of teams, ~50–125 people) as Release Train Engineer, or leads organization-level Agile coaching to create high-performing Scrum Masters. [source: JFM responsibility (P5)] KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Coaches an Agile Release Train (team of teams, ~50–125 people) as Release Train Engineer, or leads organization-level Agile coaching to create high-performing Scrum Masters." KR2. Evidence at this level's scope bar: "Multiple systems or a technical domain" — ⟨target⟩ by ⟨date⟩ Objective 2: Manages and optimizes the flow of value through the ART using information radiators and Program and Solution Kanbans. [source: JFM responsibility (P5)] KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Manages and optimizes the flow of value through the ART using information radiators and Program and Solution Kanbans." KR2. Evidence at this level's autonomy bar: "Sets direction within the domain" — ⟨target⟩ by ⟨date⟩ Objective 3: Facilitates the PI planning event and establishes annual calendars for Program Increments and iterations. [source: JFM responsibility (P5)] KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Facilitates the PI planning event and establishes annual calendars for Program Increments and iterations." KR2. Evidence at this level's complexity bar: "Novel, high-ambiguity problems; establishes the approach" — ⟨target⟩ by ⟨date⟩ Objective 4: Handles cross-team orchestration, dependency management, and program-level coordination across the train. [source: JFM responsibility (P5)] KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Handles cross-team orchestration, dependency management, and program-level coordination across the train." KR2. Evidence at this level's impact bar: "Org / multi-team outcomes" — ⟨target⟩ by ⟨date⟩ Objective 5: Works closely with leadership teams to remove impediments to agility at the organizational level and advance enterprise-wide Agile initiatives. [source: JFM responsibility (P5)] KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Works closely with leadership teams to remove impediments to agility at the organizational level and advance enterprise-wide Agile initiatives." KR2. Evidence at this level's decision rights bar: "Authority over a technical domain" — ⟨target⟩ by ⟨date⟩
MBO areas
Key result areas from this level's responsibilities, each with a standard grounded in the canon leveling rubric where one exists.
| Area | Standard | Target | Due |
|---|---|---|---|
| Coaches an Agile Release Train (team of teams, ~50–125 people) as Release Train Engineer, or leads organization-level Agile coaching to create high-performing Scrum Masters. | Consistent with this level's jfm knowledge-application rubric: "Applies expert command of scaled Agile (SAFe), flow management, and enterprise transformation to coach an Agile Release Train or lead organization-wide Agile adoption." | ⟨target⟩ | ⟨date⟩ |
| Manages and optimizes the flow of value through the ART using information radiators and Program and Solution Kanbans. | Consistent with this level's jfm knowledge-application rubric: "Applies expert command of scaled Agile (SAFe), flow management, and enterprise transformation to coach an Agile Release Train or lead organization-wide Agile adoption." | ⟨target⟩ | ⟨date⟩ |
| Facilitates the PI planning event and establishes annual calendars for Program Increments and iterations. | Consistent with this level's jfm knowledge-application rubric: "Applies expert command of scaled Agile (SAFe), flow management, and enterprise transformation to coach an Agile Release Train or lead organization-wide Agile adoption." | ⟨target⟩ | ⟨date⟩ |
| Handles cross-team orchestration, dependency management, and program-level coordination across the train. | Consistent with this level's jfm knowledge-application rubric: "Applies expert command of scaled Agile (SAFe), flow management, and enterprise transformation to coach an Agile Release Train or lead organization-wide Agile adoption." | ⟨target⟩ | ⟨date⟩ |
| Works closely with leadership teams to remove impediments to agility at the organizational level and advance enterprise-wide Agile initiatives. | Consistent with this level's jfm knowledge-application rubric: "Applies expert command of scaled Agile (SAFe), flow management, and enterprise transformation to coach an Agile Release Train or lead organization-wide Agile adoption." | ⟨target⟩ | ⟨date⟩ |
Copy / print as textshow ▾hide ▴
1. Area: Coaches an Agile Release Train (team of teams, ~50–125 people) as Release Train Engineer, or leads organization-level Agile coaching to create high-performing Scrum Masters. [source: JFM responsibility (P5) — reused, no distinct responsibility content] Standard: Consistent with this level's jfm knowledge-application rubric: "Applies expert command of scaled Agile (SAFe), flow management, and enterprise transformation to coach an Agile Release Train or lead organization-wide Agile adoption." Target: ⟨target⟩ Due: ⟨date⟩ 2. Area: Manages and optimizes the flow of value through the ART using information radiators and Program and Solution Kanbans. [source: JFM responsibility (P5) — reused, no distinct responsibility content] Standard: Consistent with this level's jfm knowledge-application rubric: "Applies expert command of scaled Agile (SAFe), flow management, and enterprise transformation to coach an Agile Release Train or lead organization-wide Agile adoption." Target: ⟨target⟩ Due: ⟨date⟩ 3. Area: Facilitates the PI planning event and establishes annual calendars for Program Increments and iterations. [source: JFM responsibility (P5) — reused, no distinct responsibility content] Standard: Consistent with this level's jfm knowledge-application rubric: "Applies expert command of scaled Agile (SAFe), flow management, and enterprise transformation to coach an Agile Release Train or lead organization-wide Agile adoption." Target: ⟨target⟩ Due: ⟨date⟩ 4. Area: Handles cross-team orchestration, dependency management, and program-level coordination across the train. [source: JFM responsibility (P5) — reused, no distinct responsibility content] Standard: Consistent with this level's jfm knowledge-application rubric: "Applies expert command of scaled Agile (SAFe), flow management, and enterprise transformation to coach an Agile Release Train or lead organization-wide Agile adoption." Target: ⟨target⟩ Due: ⟨date⟩ 5. Area: Works closely with leadership teams to remove impediments to agility at the organizational level and advance enterprise-wide Agile initiatives. [source: JFM responsibility (P5) — reused, no distinct responsibility content] Standard: Consistent with this level's jfm knowledge-application rubric: "Applies expert command of scaled Agile (SAFe), flow management, and enterprise transformation to coach an Agile Release Train or lead organization-wide Agile adoption." Target: ⟨target⟩ Due: ⟨date⟩
Scorecard
Only perspectives with real canon backing are shown — no Financial or Customer perspective, since nothing in the canon grounds business-financial or customer measures for a role alone.
Internal process
- "Coaches an Agile Release Train (team of teams, ~50–125 people) as Release Train Engineer, or leads organization-level Agile coaching to create high-performing Scrum Masters."→ ⟨target⟩ by ⟨date⟩
- "Manages and optimizes the flow of value through the ART using information radiators and Program and Solution Kanbans."→ ⟨target⟩ by ⟨date⟩
- "Facilitates the PI planning event and establishes annual calendars for Program Increments and iterations."→ ⟨target⟩ by ⟨date⟩
- "Handles cross-team orchestration, dependency management, and program-level coordination across the train."→ ⟨target⟩ by ⟨date⟩
- "Works closely with leadership teams to remove impediments to agility at the organizational level and advance enterprise-wide Agile initiatives."→ ⟨target⟩ by ⟨date⟩
Role calibration
- Meets the scope bar: "Multiple systems or a technical domain"→ ⟨target⟩ by ⟨date⟩
- Meets the autonomy bar: "Sets direction within the domain"→ ⟨target⟩ by ⟨date⟩
- Meets the complexity bar: "Novel, high-ambiguity problems; establishes the approach"→ ⟨target⟩ by ⟨date⟩
- Meets the impact bar: "Org / multi-team outcomes"→ ⟨target⟩ by ⟨date⟩
- Meets the decision rights bar: "Authority over a technical domain"→ ⟨target⟩ by ⟨date⟩
- Meets the leadership bar: "Leads cross-team technical initiatives"→ ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾hide ▴
Internal process - "Coaches an Agile Release Train (team of teams, ~50–125 people) as Release Train Engineer, or leads organization-level Agile coaching to create high-performing Scrum Masters." → ⟨target⟩ by ⟨date⟩ [source: JFM responsibility (P5)] - "Manages and optimizes the flow of value through the ART using information radiators and Program and Solution Kanbans." → ⟨target⟩ by ⟨date⟩ [source: JFM responsibility (P5)] - "Facilitates the PI planning event and establishes annual calendars for Program Increments and iterations." → ⟨target⟩ by ⟨date⟩ [source: JFM responsibility (P5)] - "Handles cross-team orchestration, dependency management, and program-level coordination across the train." → ⟨target⟩ by ⟨date⟩ [source: JFM responsibility (P5)] - "Works closely with leadership teams to remove impediments to agility at the organizational level and advance enterprise-wide Agile initiatives." → ⟨target⟩ by ⟨date⟩ [source: JFM responsibility (P5)] Role calibration - Meets the scope bar: "Multiple systems or a technical domain" → ⟨target⟩ by ⟨date⟩ [source: level dimension (Scope)] - Meets the autonomy bar: "Sets direction within the domain" → ⟨target⟩ by ⟨date⟩ [source: level dimension (Autonomy)] - Meets the complexity bar: "Novel, high-ambiguity problems; establishes the approach" → ⟨target⟩ by ⟨date⟩ [source: level dimension (Complexity)] - Meets the impact bar: "Org / multi-team outcomes" → ⟨target⟩ by ⟨date⟩ [source: level dimension (Impact)] - Meets the decision rights bar: "Authority over a technical domain" → ⟨target⟩ by ⟨date⟩ [source: level dimension (Decision rights)] - Meets the leadership bar: "Leads cross-team technical initiatives" → ⟨target⟩ by ⟨date⟩ [source: level dimension (Leadership)]