Scrum Project Roles – Part 6
Non-Core Roles
Non-core roles are also essential to the scrum process and consist of individuals, organizations, or groups that are interested in the project but are not involved in the daily sprints, ceremonies, or every day scrum processes. This includes, but is not limited to, vendors, suppliers, implementation managers, customers, external departments, users, and sponsors. These external stakeholders typically do not contribute to the development of the product or scrum team, but likely use, benefit from or financially support the project. The non-core roles will depend on what is necessary for a project and situation.
Therefore, the Scrum Master’s role in managing non-core roles is two-fold. First, they are responsible for bringing in external stakeholders when necessary and managing expectations, communication, and understanding among these diverse members. Secondly, they are responsible for protecting the Scrum team from uninformed, potentially harmful, or unnecessary opinions and decisions imposed by non-core stakeholders.
External stakeholders may create disturbances for a number of reasons: “ignorance, weak enforcement, failed support, habit, lack of faith, contention for control, or legitimate input”. Thus, a number of suggested solutions for a Scrum Master addressing these difficulties include: “be consistent, conduct training, have a contract, use the retrospective pro-actively, bring stakeholders to the Scrum,” and protect your team as a guard dog protects his post. Balancing between bringing external stakeholders and setting rules for levels of involvement should be of the utmost importance to the Scrum Master.
59 Seconds Training Video
Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)
Introductory Offer: Free Course
Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)
What is this course?
This ‘Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)’ provides an in-depth understanding of the Agile Scrum Developer roles and responsibilities
You will explore the Agile Scrum project life-cycle, including how an Agile User Story is created, to how we know when it is ‘done’
This course is aimed at those with or without prior knowledge and experience of the Agile values and principles
During this course you will learn the tools needed to succeed as an Agile Scrum Developer
What will you learn?
You will gain an in-depth understanding of the Agile Scrum Developer roles and responsibilities, and you will be able to
- Fully understand the role of the Agile Scrum Developer
- Understand the roles involved in an Agile project
- Create an effective Product Backlog
- Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
- Identify the roles involves in the Scrum Team
What topics are covered within this course
You will cover the following topics during this course:
- An Introduction to Agile Project Management (Developer)
- The 12 Agile Principles (Developer)
- Introduction to Scrum (Developer)
- Scrum Project Roles (Developer)
- The Agile Project Life-cycle (Developer)
- Acceptance Criteria and the Prioritised Product Backlog (Developer)
- Initiating an Agile Project (Developer)
- Forming the Scrum Team (Developer)
- Epics and Personas (Developer)
- User Stories and Tasks (Developer)
- Implementation of Scrum (Developer)
- The Daily Scrum (Developer)
- The Product Backlog (Developer)
- Scrum Charts (Developer)
- Review and Retrospective (Developer)
- Validating a Sprint (Developer)
- Retrospective Sprint (Developer)
- Releasing the Product (Developer)
- The Communication Plan (Developer)
- Formal Business Sign-off (Developer)
Our Book Recommendations
We found these books great for finding out more information on Agile Scrum: