What you own, influence, and observe
Agile decisions involve PMs, Scrum Masters, Developers, and stakeholders. These are the accountability lines for PMs. Own means you make the call. Influence means your input shapes it. Observe means you need visibility but it is not your decision.
Own
You make the decision
•Defining the Sprint Goal for every sprint before Sprint Planning
•Writing User Stories in the format: As a [persona], I want [goal], so that [benefit]
•Ordering the Product Backlog using explicit prioritisation criteria
•Backlog Refinement, not "Grooming": Sizing, detailing, and ordering items with the team
•Defining Acceptance Criteria for each user story before it enters a sprint
•Running the Sprint Review: Demo to stakeholders, collect feedback, update backlog
•Release Planning: Sequencing features across sprints toward a release milestone
Influence
Your input shapes the decision
•
Sprint length and ceremony structure with the Scrum Master
•
Definition of Done: Criteria must reflect PM quality expectations alongside engineering standards
•
Technical debt prioritisation: Negotiating debt paydown against feature work in sprint planning
•
Velocity targets and delivery forecasts for roadmap planning
•
Cross-team coordination and dependency resolution in multi-squad setups
•
WIP limits and board design in Kanban setups
Observe
Not your call, but you need visibility
•
How the Scrum Master facilitates retrospectives and resolves team dynamics
•
Technical architecture and implementation decisions (what the Developers build)
•
Engineering effort breakdowns within individual stories
•
Infrastructure, DevOps, and CI/CD pipeline decisions
•
Individual Developer performance: This belongs to the Scrum Master and Engineering Manager