HKSM
Non-core role
A participant who is not a required member of the Scrum Team. These individuals might be interested stakeholders or contributors without an official team position. They can collaborate or communicate with the team and offer input or support, but they are not accountable for the success or delivery of the project.
Key Points
- Optional participants; not mandatory Scrum roles.
- No formal position on the Scrum Team and not accountable for project outcomes.
- May interface with the team as advisors, stakeholders, or subject matter experts.
- Provide input, feedback, or resources but do not make Scrum decisions or own delivery.
Example
On a fintech product, a compliance advisor reviews user stories for regulatory issues when requested. They attend ad-hoc discussions and provide guidance, but they are not part of the Scrum Team and are not responsible for meeting Sprint Goals or delivering the Increment.
PMP Example Question
Which situation best represents a non-core role on a Scrum project?
- A security SME who reviews backlog items for vulnerabilities when asked but is not on the Scrum Team.
- The Product Owner who prioritizes the Product Backlog.
- The Scrum Master who facilitates Scrum events and removes impediments.
- A Developer who commits to Sprint work and builds the Increment.
Correct Answer: A — a subject matter expert who interacts with the team but is not accountable for delivery
Explanation: Non-core roles are optional contributors without an official Scrum Team position; they may advise or support but are not responsible for the project's success.
