In a Software Advice study, we found that small businesses are increasingly using agile tools and processes. But, as more SMBs take up agile project management, questions about the correct way to perform agile are naturally going to come up.
One of the most common questions is regarding the need for traditional roles, such as project managers, in agile frameworks. After all, isn’t the scrum master responsible for managing the project? And since agile already has product owners and product managers, does it really need a project manager too?
However, this sort of reasoning doesn’t mean that small businesses practicing agile project management should completely disregard the need for project managers. Instead, they must understand the evolving role of project managers to ensure that their agile team comprises the right people to cover the necessary roles and responsibilities.
SMBs that fail to fill the necessary agile roles on their project teams will breed decision-making ambiguity among team members, stifling employee productivity and causing project failure.
In this report, we explore questions regarding the evolving role of project managers, their key responsibilities and the reasons why your small business might or might not need one.
Let’s get into the details!
Here’s what we’ll cover:
Do Agile Teams Need Project Managers?
A common disagreement is regarding the need for and role of project managers on agile teams.
Two Opposing Views
1. Are ‘Agile’ Project Managers Simply a Myth?
The argument is that the project manager’s traditional role of tracking the team’s performance, efficiently allocating resources and charting out detailed project plans is antithetical to self-organizing teams that plan, manage and track their own work.
When this doesn’t make sense: While the logic behind agile project management is based around eliminating the need for long-term planning—one year or more before projects are underway—this doesn’t mean that agile projects can do away with planning altogether.
For instance, planning the project budget, task timelines and promising key deliverables with agile contracts is necessary if you’re a small business working with external clients. In this case, you need project managers skilled at creating the project plans that you’ll present to clients when signing the contract.
2. Are Agile Project Managers a Practical Necessity?
The other side maintains that project managers are necessary because businesses still need to manage budgets, allocate resources and identify project risks.
They go on to say that the assumption that agile team members will automatically pick up those responsibilities is essentially flawed. And, in the “real word” where projects have to meet specific targets and businesses have to work within constraints, project managers are essential to ensure things run smoothly.
When this doesn’t make sense: One thing that will surely ruin the momentum of an agile team is over planning.
For example, scrum teams hold sprint planning meetings to commit to tasks the development team will complete in a time-boxed (one week to one month) event. And, one of the key factors behind sprint planning failures is when teams spend too much time in these meetings.
Teams that are led by traditional project managers, who typically stress the importance of planning, can waste hours discussing the details of a feature and planning how to build it.
Walking the Fine Line
While both of the above views have their merits, we have seen how in certain scenarios, these arguments don’t hold up.
The answer to whether your business needs project managers therefore lies in understanding out how extensive your need for project planning is.
Dedicate Project Manager Resources to the Riskiest Projects
In the Gartner report, “Not Every Project Needs a Project Manager” (content available to clients), Research VP Lars Mieritz offers two key recommendations for enterprises:
- Help smaller, self-managed teams manage their work by creating a project specialist role.
- Save project managers with the most experience dedicated to working on complex projects for your most critical or risky projects.
While the above report is written for large organizations that have project management offices (PMOs), the recommendations are relevant for small businesses, as well.
For instance, small businesses that have limited financial and human resources should judiciously allocate project managers for handling “complex and critical projects.”
These “critical” projects include those that need detailed scope analysis, collaboration between multiple teams, complex stakeholder management and constant project tracking of what’s going well—and what’s not—to quickly identify risks.
SMBs should keep these points in mind and only designate project managers for critical projects that require 400+ hours of work.
On the other hand, if your business has small teams (zero to five team members) that work on projects requiring fewer than 400 hours of work, you’ll benefit more by designating a project specialist role.
What is the project specialist role, and how does it differ from a project manager?
The project specialist is responsible for creating the project schedule, analyzing risks and ensuring that the team delivers high-quality projects within the estimated time and budget.
However, the project specialist is not someone dedicated to the PM role, but an existing member of the core agile team to whom you offer project manager responsibilities. As we can see in the image, the project specialist does not exist independent of the team.
A version of this image originally appeared in the Gartner report, “Not Every Project Needs a Project Manager” (content available to clients)
To sum it up, the key difference between a project manager and project specialist is that the former is a leadership role dedicated to governing the team, while the latter is a person that takes cares of basic project management but does not conduct advanced project planning for the team.
A key point to remember is that the project specialist should be used for small teams and should actively work alongside other team members, such as the subject matter expert (SME) and development lead/scrum master to engage with stakeholders.
- Save your project managers for complex and critical projects that require more than 400+ hours of work.
- Create a project specialist role for managing small projects where team members are mostly working out of the same location and coordination is not a challenge.
- Don’t assign project specialists to a team that is facing internal conflicts or handling high-risk projects, as this is not a leadership role but someone who can handle a few necessary project management aspects for the small team.
Explore New Project Manager Roles to Support Agile Teams
In a survey conducted by VersionOne, a large number of respondents say their organizations still don’t have mature agile practices in place. This report should raise the alarm for SMBs, because nearly 40 percent of the total respondents work for small organizations with fewer than 1,000 employees.
A clear sign that your business lacks mature agile practices is that your team doesn’t have clarity on their roles and responsibilities. For example, businesses just starting with scrum (a popular agile project management framework) face project failure if their team lacks a clear understanding of agile roles.
This confusion occurs primarily when SMBs stick rigidly to predefined agile roles without considering their team’s needs or business priorities.
In agile project management, the focus is on continuously improving products instead of managing time-bound projects. As a result, roles such as scrum master and product owner have emerged. These team members take on tasks such as tracking projects, managing schedules and so on, which were historically handled by project managers.
However, small businesses typically have budget and human resource constraints which can lead product owners to overcompensate and take on additional tasks. This reduces their efficiency as they deviate from executing their core tasks of managing stakeholder expectations and conducting market research to project governance such as tracking the work of development teams.
Instead, explore evolving project manager roles to support product owners, scrum masters and the team.
An example of such a role that small businesses should establish is the “protector project manager,” which according to Gartner (content available to clients only), is one of the new roles of project managers involved in solutions delivery projects.
What is a protector project manager and how is it different from a traditional project manager?
The protector project manager helps to remove distractions, allowing product owners to focus on their key tasks and helping the development team in project execution. Here’s a graphic to explain this person’s key responsibilities:
The protector project manager is essentially a project manager “lite.” One key difference is that the protector project manager acts to remove outside distractions for the delivery team and product owner by taking up status reporting and stakeholder communication responsibilities.
A typical project manager, on the other hand, does all this as well as project planning, creating budgets and tracking project KPIs.
- Establish a protector project manager only if your product owners are facing challenges in managing the team.
- Create this role if project status reporting and managing stakeholders is a key requirement. This is typical of small businesses working on client projects.
Conclusion and Next Steps
The Gartner report, “Become an Agile Superhero: 8 Attributes for Success,” points out that successful agile teams are those that have sound knowledge about agile processes and techniques (full content available to clients).
Establishing a sound agile process does not mean that you should blindly follow agile definitions without analyzing their suitability to your business priorities.
If you’re a small business facing agile project management issues, begin by analyzing the current roles and responsibilities on your teams.
Summing up, here are the key takeaways:
- Explore new agile project manager roles such as the project specialist and protector project manager to support product owners and delivery teams.
- If you’re a business with microteams, then there’s no real requirement for a traditional project manager. Establishing a project specialist role instead would be more beneficial.
- If your business has teams that are constantly missing their deadlines or facing issues with project quality, then establishing a protector project manager role is a viable option. This is especially true for businesses working on client-facing projects.
In a similar vein, you must also have clearly defined roles for not just team members, but for anyone who can influence the project outcome. The inability to identify project stakeholders and understand their roles can lead to project failure.
Leveraging the right agile project management solutions can help your team perform their roles and and responsibilities.
Agile project management solutions are designed to suit the workflows of agile teams, including tracking progress of tasks in iterations (teams following Scrum) or managing tasks in a continuous flow (teams following kanban).
As a next step, you can learn more about agile project management processes and tools by reading these select reports and buyers guides: