Agile Scrum Roles and Responsibilities
Agile Scrum Roles and Responsibilities
Agile Scrum Roles and Responsibilities
Responsibilities
Agile techniques have become very popular and effective approaches to delivering
benefit on a project. For this reason, we will focus on Agile frameworks, techniques,
principles and ideas as well.
Agile SCRUM is one of many Agile frameworks. SCRUM is a very specific framework
that focuses on the following roles.
1. ScrumMaster
2. Product Owner
3. Team
4. Stakeholders
The following graphic depicts each role and the relationship of the role with the other
SCRUM roles.
The ScrumMaster Role
The ScrumMaster, despite popular belief, is not the Agile term for a project manager. In
fact, the ScrumMaster serves a very different purpose. The ScrumMaster does not have
responsibility for delivering the project. Rather, the ScrumMaster is a facilitator, coach
and champion of the Scrum framework and process.
The biggest challenge to applying Scrum within an organization is not the actual Scrum
process. It is the cultural change and acceptance of the new roles that an organization
finds most difficult (e.g., the enhanced power of the Team to commit to a Sprint goal,
and to deliver it with little interference from management). More on the differences
later, but because the organization does need to accept a significant change in
philosophy, there is a need for a ScrumMaster, who serves as the coach, mentor,
facilitator, champion, and cheerleader.
It is for the above stated reasons that a full-time ScrumMaster is recognized as the
authority on Scrum and needed to continue to facilitate and champion the process, to
ensure that the process is followed as intended, and to coach members as needed.
Within the Scrum framework, Stakeholders are responsible for communicating their
needs, and providing feedback on the product.
They have to breakdown the requirements, create task, estimate and distribute
them. In other words this means that they have to create the Sprint Backlog.
They have to perform the short Daily Sprint Meeting.
They have to ensure that at the end of the Sprint potentially shippable
functionality is delivered.
They have to update the status and the remaining efforts for their tasks to allow
creation of a Sprint Burndown Diagram.