Project Managers have a wide range of responsibilities when working on a project: they oversee planning the project, create a schedule and timeline, execute each phase, manage budgets, serve as the liaison among all stakeholders, and also troubleshoot and maintenance, plus whatever other tasks that get added to their plate. As such, a Project Manager (PM) must be very organized and detail oriented. They also need to have great people skills because at the end of the day, this person is responsible for leading the team and communicating with all involved parties.
The Project Management Institute describes the role of a project manager as someone who acts as an agent of change. Someone who “makes project goals their own and uses their skills and expertise to inspire a sense of shared purpose within the project team.”
PMs serve as leaders. Aside from ensuring the project is delivered on time and within the agreed-upon budget, they also encourage their teams and inspire their clients. They need to solve problems as they arise with strong critical-thinking capabilities while also possessing strong communication skills to ensure everyone remains informed, motivated, and onboard.
A good PM delivers a final product on time, on budget while meeting or exceeding client expectations. Tracing projects back to business goals is becoming increasingly necessary for project managers.
All brains on deck
The Agile framework focuses on self-organization and team empowerment rather than defining specific roles, which is why there is no need for a Project Manager in the traditional sense; the role is pretty much covered between all the existing roles.
Anyone who's ever taken an Agile class or training has heard of the defined roles of scrum master, product owner, and development team in the scrum framework, which makes no mention of the Project Manager role. Personally, I have taken five Agile classes from different places and never once have heard the word “Project Manager”. So, where does this skill set belong? Is there really no use for a PM in an Agile setting? Is there nothing they can do to add value to an Agile project?
An Agile organization can- and does- function well without a Project Manager. However, there is a huge potential for a PM skill set to add value to an organization, specifically on large projects. I have worked in QA Testing across various complex projects for the past five years, and it is clear to me that a PM can greatly impact both the journey and outcome of the project in regard to budget and risk management, as well as coordination between multiple scrum teams.
In an Agile environment, a Project Manager can add value by managing key aspects of every project, overseeing budgets, risks, etc., especially on large scale projects for enterprise organizations. Having a Project Manager also frees up the Scrum Master to focus solely on his or her core functions.
Take, for example, the below chart from Ken Rubin and his article “What Happens to the Project Manager when Doing Agile Development with Scrum?” While the PM role no longer exists in a traditional sense, you can see how the tasks and roles normally assigned to them still exist within the system, but are spread out throughout the team. As a result, the person who would normally act as the PM, can work very well as the Product Owner, the Scrum Master, or on the Development Team, depending on his or her background and specific skillset.