Scrum Aspects
Overview

Clearly defined roles and responsibilities are fundamental to Scrum. This aspect addresses how a project is structured, including the composition of the Scrum Team and the distinction between core and non-core roles.

SCRUMstudy identifies three core roles: the Product Owner, who drives business value and represents the customer's perspective; the Scrum Master, who facilitates the process and clears obstacles for the team; and the Scrum Team, which estimates effort and produces the project deliverables.

Non-core roles - including business stakeholders, supporting services, vendors, and the optional Scrum Guidance Body - are also recognized. While they may not participate continuously, their involvement can have a meaningful impact on project outcomes.

SCRUMstudy emphasizes that a sound business justification and a clear Project Vision Statement should be in place before a project gets underway. These elements help decision-makers evaluate whether the effort is worthwhile and give the Product Owner a basis for building a prioritized backlog.

In Scrum, business justification is directly connected to value-driven delivery. Because all projects carry some level of uncertainty, Scrum promotes early delivery of working results so stakeholders can assess value sooner, validate the direction, and reinvest with greater confidence.

Business justification is not a one-time exercise. It should be revisited throughout the project to confirm that the initiative remains relevant as priorities, constraints, and expectations shift.

SCRUMstudy defines quality as the degree to which completed deliverables meet acceptance criteria and fulfill the business value the customer expects. Rather than treating quality as a final-stage concern, Scrum builds it into the process through continuous improvement.

Because work is delivered in increments across Sprints, defects and gaps are identified earlier in the process. Development, testing, and documentation are completed within the same Sprint, making quality an integral part of the work rather than a separate phase.

Ongoing dialogue between the Scrum Core Team and business stakeholders - combined with reviews of actual product increments - helps narrow the gap between what customers expect and what teams are delivering.

No project is immune to change, regardless of the methodology in use. SCRUMstudy makes clear that Scrum development processes are built to accommodate change, helping organizations capture the benefits that come with new information while limiting negative disruption.

Scrum recognizes that business stakeholders frequently refine their expectations over time, and that pinning down every requirement at project initiation is rarely realistic. Short, iterative Sprints allow teams to gather feedback regularly and course-correct before issues compound.

Rather than treating change as a problem to be controlled, Scrum treats it as expected. This approach fosters responsiveness, stronger stakeholder engagement, and a tighter fit between the final product and the evolving needs of the business.

SCRUMstudy defines risk as an uncertain event or condition that can affect project objectives - either positively or negatively. Positive risks represent opportunities to be leveraged; negative risks are threats to be mitigated. In Scrum, risk management is an ongoing activity that starts early and runs throughout the project.

Risks are evaluated based on two key factors: the likelihood of occurrence and the potential impact. Those with high probability and high impact demand more immediate attention than risks that are less likely or less consequential.

Scrum's incremental delivery model helps expose risks sooner. Smaller units of work, faster feedback cycles, and regular Sprint reviews give teams the opportunity to respond to issues before they escalate.