← Scrum Project Management — P4

Goal templates — Scrum Project Management — P4

Scrum Project Management · Scrum Project Management · P4 — Senior 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 (P4)

Manages multiple Scrum teams concurrently under more complex conditions, working with more demanding teams or products.

Specific
Deliver: "Manages multiple Scrum teams concurrently under more complex conditions, working with more demanding teams or products."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex delivery variables across teams; removes difficult organizational impediments and resolves systemic process issues."
Relevant
Advances the Scrum Project Management · Scrum Project Management mandate for a P4 — Senior Professional.
Time-bound
⟨date⟩

JFM responsibility (P4)

Mentors junior Scrum Masters and Agile champions, selecting facilitation and coaching methods appropriate to each team's maturity.

Specific
Deliver: "Mentors junior Scrum Masters and Agile champions, selecting facilitation and coaching methods appropriate to each team's maturity."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex delivery variables across teams; removes difficult organizational impediments and resolves systemic process issues."
Relevant
Advances the Scrum Project Management · Scrum Project Management mandate for a P4 — Senior Professional.
Time-bound
⟨date⟩

JFM responsibility (P4)

Removes more difficult organizational impediments that span teams, functions, or leadership decisions.

Specific
Deliver: "Removes more difficult organizational impediments that span teams, functions, or leadership decisions."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex delivery variables across teams; removes difficult organizational impediments and resolves systemic process issues."
Relevant
Advances the Scrum Project Management · Scrum Project Management mandate for a P4 — Senior Professional.
Time-bound
⟨date⟩

JFM responsibility (P4)

Influences process improvements beyond their own teams, driving adoption of better Agile practices across the function.

Specific
Deliver: "Influences process improvements beyond their own teams, driving adoption of better Agile practices across the function."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex delivery variables across teams; removes difficult organizational impediments and resolves systemic process issues."
Relevant
Advances the Scrum Project Management · Scrum Project Management mandate for a P4 — Senior Professional.
Time-bound
⟨date⟩

JFM responsibility (P4)

Coordinates across groups on scope, success criteria, and timelines, influencing delivery decisions among technical and non-technical stakeholders.

Specific
Deliver: "Coordinates across groups on scope, success criteria, and timelines, influencing delivery decisions among technical and non-technical stakeholders."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex delivery variables across teams; removes difficult organizational impediments and resolves systemic process issues."
Relevant
Advances the Scrum Project Management · Scrum Project Management mandate for a P4 — Senior Professional.
Time-bound
⟨date⟩
Copy / print as textshow ▾
1. Manages multiple Scrum teams concurrently under more complex conditions, working with more demanding teams or products.  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Manages multiple Scrum teams concurrently under more complex conditions, working with more demanding teams or products."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex delivery variables across teams; removes difficult organizational impediments and resolves systemic process issues."
   Relevant:    Advances the Scrum Project Management · Scrum Project Management mandate for a P4 — Senior Professional.
   Time-bound:  ⟨date⟩

2. Mentors junior Scrum Masters and Agile champions, selecting facilitation and coaching methods appropriate to each team's maturity.  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Mentors junior Scrum Masters and Agile champions, selecting facilitation and coaching methods appropriate to each team's maturity."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex delivery variables across teams; removes difficult organizational impediments and resolves systemic process issues."
   Relevant:    Advances the Scrum Project Management · Scrum Project Management mandate for a P4 — Senior Professional.
   Time-bound:  ⟨date⟩

3. Removes more difficult organizational impediments that span teams, functions, or leadership decisions.  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Removes more difficult organizational impediments that span teams, functions, or leadership decisions."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex delivery variables across teams; removes difficult organizational impediments and resolves systemic process issues."
   Relevant:    Advances the Scrum Project Management · Scrum Project Management mandate for a P4 — Senior Professional.
   Time-bound:  ⟨date⟩

4. Influences process improvements beyond their own teams, driving adoption of better Agile practices across the function.  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Influences process improvements beyond their own teams, driving adoption of better Agile practices across the function."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex delivery variables across teams; removes difficult organizational impediments and resolves systemic process issues."
   Relevant:    Advances the Scrum Project Management · Scrum Project Management mandate for a P4 — Senior Professional.
   Time-bound:  ⟨date⟩

5. Coordinates across groups on scope, success criteria, and timelines, influencing delivery decisions among technical and non-technical stakeholders.  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Coordinates across groups on scope, success criteria, and timelines, influencing delivery decisions among technical and non-technical stakeholders."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex delivery variables across teams; removes difficult organizational impediments and resolves systemic process issues."
   Relevant:    Advances the Scrum Project Management · Scrum Project Management mandate for a P4 — Senior 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 (P4)

Manages multiple Scrum teams concurrently under more complex conditions, working with more demanding teams or products.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Manages multiple Scrum teams concurrently under more complex conditions, working with more demanding teams or products."
  • Evidence at this level's scope bar: "A system or set of related features" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P4)

Mentors junior Scrum Masters and Agile champions, selecting facilitation and coaching methods appropriate to each team's maturity.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Mentors junior Scrum Masters and Agile champions, selecting facilitation and coaching methods appropriate to each team's maturity."
  • Evidence at this level's autonomy bar: "Self-directed; reviewed at critical decision points" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P4)

Removes more difficult organizational impediments that span teams, functions, or leadership decisions.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Removes more difficult organizational impediments that span teams, functions, or leadership decisions."
  • Evidence at this level's complexity bar: "Complex, ambiguous problems; devises new approaches" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P4)

Influences process improvements beyond their own teams, driving adoption of better Agile practices across the function.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Influences process improvements beyond their own teams, driving adoption of better Agile practices across the function."
  • Evidence at this level's impact bar: "Multi-team / function outcomes" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P4)

Coordinates across groups on scope, success criteria, and timelines, influencing delivery decisions among technical and non-technical stakeholders.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Coordinates across groups on scope, success criteria, and timelines, influencing delivery decisions among technical and non-technical stakeholders."
  • Evidence at this level's decision rights bar: "Owns technical decisions for a system; influences adjacent design" — ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾
Objective 1: Manages multiple Scrum teams concurrently under more complex conditions, working with more demanding teams or products.  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Manages multiple Scrum teams concurrently under more complex conditions, working with more demanding teams or products."
  KR2. Evidence at this level's scope bar: "A system or set of related features" — ⟨target⟩ by ⟨date⟩

Objective 2: Mentors junior Scrum Masters and Agile champions, selecting facilitation and coaching methods appropriate to each team's maturity.  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Mentors junior Scrum Masters and Agile champions, selecting facilitation and coaching methods appropriate to each team's maturity."
  KR2. Evidence at this level's autonomy bar: "Self-directed; reviewed at critical decision points" — ⟨target⟩ by ⟨date⟩

Objective 3: Removes more difficult organizational impediments that span teams, functions, or leadership decisions.  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Removes more difficult organizational impediments that span teams, functions, or leadership decisions."
  KR2. Evidence at this level's complexity bar: "Complex, ambiguous problems; devises new approaches" — ⟨target⟩ by ⟨date⟩

Objective 4: Influences process improvements beyond their own teams, driving adoption of better Agile practices across the function.  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Influences process improvements beyond their own teams, driving adoption of better Agile practices across the function."
  KR2. Evidence at this level's impact bar: "Multi-team / function outcomes" — ⟨target⟩ by ⟨date⟩

Objective 5: Coordinates across groups on scope, success criteria, and timelines, influencing delivery decisions among technical and non-technical stakeholders.  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Coordinates across groups on scope, success criteria, and timelines, influencing delivery decisions among technical and non-technical stakeholders."
  KR2. Evidence at this level's decision rights bar: "Owns technical decisions for a system; influences adjacent design" — ⟨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.

AreaStandardTargetDue
Manages multiple Scrum teams concurrently under more complex conditions, working with more demanding teams or products.Consistent with this level's jfm knowledge-application rubric: "Applies in-depth Agile expertise across multiple teams and more demanding products; familiar with scaling concepts (SAFe) and selects facilitation methods to fit team maturity."⟨target⟩⟨date⟩
Mentors junior Scrum Masters and Agile champions, selecting facilitation and coaching methods appropriate to each team's maturity.Consistent with this level's jfm knowledge-application rubric: "Applies in-depth Agile expertise across multiple teams and more demanding products; familiar with scaling concepts (SAFe) and selects facilitation methods to fit team maturity."⟨target⟩⟨date⟩
Removes more difficult organizational impediments that span teams, functions, or leadership decisions.Consistent with this level's jfm knowledge-application rubric: "Applies in-depth Agile expertise across multiple teams and more demanding products; familiar with scaling concepts (SAFe) and selects facilitation methods to fit team maturity."⟨target⟩⟨date⟩
Influences process improvements beyond their own teams, driving adoption of better Agile practices across the function.Consistent with this level's jfm knowledge-application rubric: "Applies in-depth Agile expertise across multiple teams and more demanding products; familiar with scaling concepts (SAFe) and selects facilitation methods to fit team maturity."⟨target⟩⟨date⟩
Coordinates across groups on scope, success criteria, and timelines, influencing delivery decisions among technical and non-technical stakeholders.Consistent with this level's jfm knowledge-application rubric: "Applies in-depth Agile expertise across multiple teams and more demanding products; familiar with scaling concepts (SAFe) and selects facilitation methods to fit team maturity."⟨target⟩⟨date⟩
Copy / print as textshow ▾
1. Area: Manages multiple Scrum teams concurrently under more complex conditions, working with more demanding teams or products.  [source: JFM responsibility (P4) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth Agile expertise across multiple teams and more demanding products; familiar with scaling concepts (SAFe) and selects facilitation methods to fit team maturity."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Mentors junior Scrum Masters and Agile champions, selecting facilitation and coaching methods appropriate to each team's maturity.  [source: JFM responsibility (P4) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth Agile expertise across multiple teams and more demanding products; familiar with scaling concepts (SAFe) and selects facilitation methods to fit team maturity."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Removes more difficult organizational impediments that span teams, functions, or leadership decisions.  [source: JFM responsibility (P4) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth Agile expertise across multiple teams and more demanding products; familiar with scaling concepts (SAFe) and selects facilitation methods to fit team maturity."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Influences process improvements beyond their own teams, driving adoption of better Agile practices across the function.  [source: JFM responsibility (P4) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth Agile expertise across multiple teams and more demanding products; familiar with scaling concepts (SAFe) and selects facilitation methods to fit team maturity."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Coordinates across groups on scope, success criteria, and timelines, influencing delivery decisions among technical and non-technical stakeholders.  [source: JFM responsibility (P4) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth Agile expertise across multiple teams and more demanding products; familiar with scaling concepts (SAFe) and selects facilitation methods to fit team maturity."
   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

  • "Manages multiple Scrum teams concurrently under more complex conditions, working with more demanding teams or products."→ ⟨target⟩ by ⟨date⟩
  • "Mentors junior Scrum Masters and Agile champions, selecting facilitation and coaching methods appropriate to each team's maturity."→ ⟨target⟩ by ⟨date⟩
  • "Removes more difficult organizational impediments that span teams, functions, or leadership decisions."→ ⟨target⟩ by ⟨date⟩
  • "Influences process improvements beyond their own teams, driving adoption of better Agile practices across the function."→ ⟨target⟩ by ⟨date⟩
  • "Coordinates across groups on scope, success criteria, and timelines, influencing delivery decisions among technical and non-technical stakeholders."→ ⟨target⟩ by ⟨date⟩

Role calibration

  • Meets the scope bar: "A system or set of related features"→ ⟨target⟩ by ⟨date⟩
  • Meets the autonomy bar: "Self-directed; reviewed at critical decision points"→ ⟨target⟩ by ⟨date⟩
  • Meets the complexity bar: "Complex, ambiguous problems; devises new approaches"→ ⟨target⟩ by ⟨date⟩
  • Meets the impact bar: "Multi-team / function outcomes"→ ⟨target⟩ by ⟨date⟩
  • Meets the decision rights bar: "Owns technical decisions for a system; influences adjacent design"→ ⟨target⟩ by ⟨date⟩
  • Meets the leadership bar: "Technical lead for focused efforts; mentors several"→ ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾
Internal process
  - "Manages multiple Scrum teams concurrently under more complex conditions, working with more demanding teams or products."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]
  - "Mentors junior Scrum Masters and Agile champions, selecting facilitation and coaching methods appropriate to each team's maturity."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]
  - "Removes more difficult organizational impediments that span teams, functions, or leadership decisions."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]
  - "Influences process improvements beyond their own teams, driving adoption of better Agile practices across the function."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]
  - "Coordinates across groups on scope, success criteria, and timelines, influencing delivery decisions among technical and non-technical stakeholders."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]

Role calibration
  - Meets the scope bar: "A system or set of related features"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Scope)]
  - Meets the autonomy bar: "Self-directed; reviewed at critical decision points"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Autonomy)]
  - Meets the complexity bar: "Complex, ambiguous problems; devises new approaches"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Complexity)]
  - Meets the impact bar: "Multi-team / function outcomes"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Impact)]
  - Meets the decision rights bar: "Owns technical decisions for a system; influences adjacent design"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Decision rights)]
  - Meets the leadership bar: "Technical lead for focused efforts; mentors several"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Leadership)]