HKSM

The Scrum Core Team in SBOK is the group of core roles for a project: Product Owner, Scrum Master, and the cross-functional Scrum Team. It is an output of Initiate processes and a key input to planning, estimation, implementation, review, and release activities.

Key Points

• Includes Product Owner, Scrum Master, and the Scrum Team members.
• Formed during Initiate and then used across all later Scrum processes.
• Enables estimation, commitment, delivery, inspection, and adaptation.
• Should be stable, cross-functional, and empowered to self-organize.
• Typical team size is small (often 5–9) to support fast feedback.
• Acts as the accountable unit for product increments and sprint outcomes.

Purpose

The Scrum Core Team exists to provide a clearly identified, empowered group that can plan, build, and deliver increments while collaborating closely with stakeholders. It concentrates decision rights, domain knowledge, and execution capability so the product backlog can be refined, estimated, and turned into working outcomes each sprint.

This ITTO ensures there is a stable nucleus for transparency, inspection, and adaptation throughout the project or release.

Key Terms & Clauses

• Core roles: Product Owner, Scrum Master, Scrum Team members (developers, testers, designers, etc.).
• Non-core roles: Stakeholders, vendors, and supporting groups that influence but are not part of the core team.
• Cross-functional: The team collectively has all skills needed to deliver a Done increment.
• Self-organizing: The team decides how to do the work without external micromanagement.
• Capacity and velocity: Availability and historical throughput used for planning and forecasting.
• Working agreements: Team norms for collaboration, Definition of Done, and tooling practices.

How to Develop/Evaluate

Developing the Scrum Core Team:

• Appoint a single Product Owner and a single Scrum Master for the team.
• Select cross-functional members who cover required skills for near-term backlog items.
• Confirm availability, time-zone considerations, and preferred team size.
• Establish working agreements, Definition of Done, and communication channels.
• Align with organizational standards or Scrum Guidance Body policies as applicable.

Evaluating readiness:

• All core roles identified and committed.
• Skills coverage is sufficient for upcoming epics/user stories.
• Capacity and onboarding plan are understood.
• Team norms and Definition of Done are visible and agreed.

How to Use

As an input, the Scrum Core Team participates in and enables:

• Release and sprint planning: estimating, forecasting, and selecting work.
• Backlog refinement: clarifying acceptance criteria and splitting stories.
• Implementation: creating deliverables and managing quality to the Definition of Done.
• Review and validation: demonstrating increments and capturing feedback.
• Retrospectives: inspecting process and agreeing on improvement actions.
• Risk and issue management: raising impediments and collaborating on resolution.

As an output, it results from initiating processes that appoint the Product Owner and Scrum Master and form the Scrum Team, making the project ready for detailed planning and execution.

Example Snippet

A company launches a new product initiative. The sponsor appoints a Product Owner and a Scrum Master, and six cross-functional members are selected. With roles confirmed, working agreements drafted, and tools configured, the Scrum Core Team is now established and can begin backlog refinement and estimation toward the first sprint plan.

Risks & Tips

• Risk: Part-time or frequently changing members reduce velocity and quality. Tip: Aim for stable, dedicated membership.
• Risk: Missing key skills causes handoffs and delays. Tip: Ensure cross-functional coverage or add skills early.
• Risk: Role confusion between Product Owner and Scrum Master. Tip: Clarify accountabilities and decision rights.
• Risk: Overlarge team slows decision-making. Tip: Keep teams small and split when necessary.
• Risk: External command-and-control undermines self-organization. Tip: Empower the team and protect focus.
• Risk: Weak Definition of Done leads to hidden work. Tip: Make DoD explicit and enforce it every sprint.

PMP/SCRUM Example Question

During Initiate, a sponsor appoints the Product Owner and Scrum Master, and a cross-functional set of members commits to the work. What item is now complete and will act as an input to estimation and sprint planning?

1. Sprint Backlog
2. Scrum Core Team
3. Release Burnup Chart
4. Definition of Ready

Correct Answer: B — Scrum Core Team

Explanation: Forming the Scrum Core Team (PO, SM, and Scrum Team) is an output of initiation and becomes a key input for estimation and planning. The Sprint Backlog and charts are created later, and Definition of Ready is optional.