Agile Project Management Roles

Agile Project Management Roles
Author: PM Majik
Copyright 2019. All rights reserved. www.pmmajik.com

Contents
1.0 Purpose of this presentation
2.0 Agile project management roles summary
3.1 Scrum master
3.2 Project sponsor
3.3 Product manager
3.4 Stakeholders
3.5 Development team
3.6 Agile mentor
4.0 Team characteristics
5.0 Summary
6.0 PMO resources

1.0 Purpose of this presentation
The purpose of this presentation is to provide a quick guide to the core roles involved in
agile project management together with the important team characteristics.
This will help those new to the topic to quickly understand the difference in the roles.
Remember these are general guidelines. You should use them to help determine what
is required for your organisation.

2.0 Agile Project Management Team Roles
Agile Project
Roles
Scrum
Master
Product
Owner
Stakeholders
Team
Members
Agile
Mentor
Project
Sponsor

3.1 Scrum Master
• Also referred to as the Project Facilitator, the Scrum Master is similar to a
Project Manager.
• They are responsible for over-seeing the day-to-day running of the
project, monitoring the Scrum board and ensuring that all tasks are on
target.
• The most effective Scrum Masters will have a high level of organisational
influence, with the ability to make changes without gaining formal
authority.

3.2 Project Sponsor
• As with traditional projects, you need to have a project sponsor.
• This is the person who wants the outcome from the project and is
prepared to invest the required budget and resources.
• They will also be the point of escalation as and when challenges are
identified that cannot be resolved by the project team.

3.3 Product Owner
• The Product Owner connects the customer, stakeholders and the Project
Development Team, and bridges the gap between them.
• They have a clear understanding of the customer’s needs and expert
knowledge of the product.
• Sometimes referred to as a Customer Representative, the Product Owner
works with the Development Team to ensure that they remain focussed
on the process, and is responsible for being decisive and making
important decisions.

3.4 Stakeholders
• Stakeholders are any individuals or groups that have an interest in the
project; they can include staff from other departments within the
business, or external organisations.
• Despite not having overall responsibility, Stakeholders provide input into
the project and are affected by its outcome.
• In agile projects, Stakeholders provide regular support and feedback to
both the Development Team and the Scrum Master.
• Without this, the project is unlikely to succeed.

3.5 Development Team
• The development team have a hands-on role in creating the product; in
other words, they are responsible for getting things done.
• Each team member will bring different skills to the project; they may be
engineers, designers, developers or copywriters amongst many other
roles.
• Having a mixture of skills provides versatility to the project.

3.6 Agile Mentor
• A mentor is invaluable for a team that is new to agile project
management, or those that want to improve their performance.
• They will have extensive experience of implementing agile projects,
which they can share with the team.
• Mentors are not involved in the execution of the project, but are
responsible for sharing their experience in applying the principles of agile
project management and knowledge of the techniques used.

4.0 Team Characteristics
In addition to having the right team members, your team must also possess
certain characteristics.
• Within a scrum team, each
member is equally important;
however, they have clearly
defined responsibilities.
• Each team member is able to
voice an opinion, and is guided
to a mutually agreed solution
by the Scrum Master.
• The team should be located in
the same room, to facilitate
close-collaboration, and
remove communication
barriers.
• When teams are located in
different rooms, places or even
time zones, communication,
and thus the project, can be
subject to delays.
• Switching between projects
and tasks is likely to cause a
distraction, so team members
should be assigned to the
project on a full-time basis
until its completion.
• Dedication to a single project
also allows team members to
self-manage more effectively,
taking ownership and
responsibility for their tasks.
Self Manage Closely Located Focused
• The team should have all of the
knowledge needed to deliver
the product.
• Although each team member
has their own specialism, they
should have some working
knowledge of all of the other
aspects of the process.
• Ideally, the project team
should be kept together with
limited changes.
• Learning to work together in
Scrum teams takes time, and
therefore projects will run
more efficiently if there is a
low turnover of staff.
Cross Functional Established

5.0 Summary
There are a number of roles involved in Agile Project Management.
Reminder of the 6 agile project management roles:
1. Scrum Master
2. Project Sponsor
3. Product Owner
4. Stakeholders
5. Development Team
6. Agile Mentor
Additional Resource
https://www.pmmajik.com/overview-of-agile-project-management/

5.0 PMO resources
If you want more information, visit www.pmmajik.com where you will find lots of project
and PMO resources including the FREE guide, 7 Steps to Set-Up a PMO.
Visit http://www.pmmajik.com/set-pmo/
PM Majik Website
On the PM Majik website you will find over 200 articles that contain practical and
pragmatic tips and insights for designing, mobilising and managing a PMO. New
articles are added weekly. Topic requests are encouraged from the community.

Agile Project Management Roles

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Agile Project Management Roles

Similar to Agile Project Management Roles (20)

More from PM Majik

More from PM Majik (13)

Recently uploaded

Recently uploaded (20)

Agile Project Management Roles