PSM I Scrum Accountabilities and Self-Management

Study PSM I Scrum Accountabilities and Self-Management: key concepts, common traps, and exam decision cues.

The Scrum Team is self-managing, but that does not mean accountabilities blur together. PSM I often tests whether you can preserve both ideas at the same time: the team manages its work, while each accountability still has a distinct purpose.

Accountability map

Accountability Stronger purpose Common weak reading
Product Owner maximize value and manage the Product Backlog project coordinator or approval clerk
Scrum Master enable Scrum, coach the team, and help remove impediments team secretary or delivery manager
Developers create a usable Increment each Sprint task executors waiting for assignments
Scrum Team self-manage work, plans, and internal responsibilities committee that shares every decision equally

What self-management really means

Self-management means the Scrum Team decides how to turn Product Backlog items into a usable Increment and how to organize internal work. It does not mean the Product Owner gives up backlog accountability, or the Scrum Master stops teaching Scrum, or Developers decide product value priorities on their own.

Example

A stakeholder wants to assign tasks directly to individual Developers and bypass Sprint Planning because it feels faster. The stronger answer protects self-management: the stakeholder may clarify needs, but the Scrum Team decides how work is selected and organized within Scrum.

Common pitfalls

  • Calling everyone interchangeable because Scrum has no titles inside the team.
  • Treating self-management as freedom from goals, commitments, or accountability.
  • Turning the Scrum Master into a people manager.
  • Letting Developers override Product Backlog ordering.

Sample Exam Question

Which statement best reflects self-management in Scrum?

A. The Scrum Team decides how to accomplish its work while preserving clear accountabilities
B. The Scrum Master assigns work because the team needs coordination
C. Developers may reorder the Product Backlog when technical dependencies appear
D. The Product Owner chooses task ownership during the Sprint to protect value

Best answer: A

Why: Scrum Teams self-manage the work of creating value, but Product Owner, Scrum Master, and Developers still keep distinct accountabilities.

Why the others are weaker: B, C, and D all shift Scrum away from its actual accountability model.

Revised on Monday, April 27, 2026