Do Project Managers Make Good Scrum Masters? Insights from the Agile Mentor Community

We recently asked members of the Agile Mentor community whether project managers can be good Scrum Masters, inviting them to answer “yes,” “no,” or “it depends.” The responses ranged from strong opposition to enthusiastic support, and the blog summarizes several of these viewpoints.

No way! Project managers make terrible Scrum Masters! One participant initially said, “No! Project managers become terrible Scrum Masters,” but later added that former project managers can become excellent Scrum Masters.

Another member warned that many organizations simply rename the project‑manager title to Scrum Master while retaining traditional project‑management responsibilities, which can hinder agile adoption.

Several contributors noted that while it is difficult for a project manager to assume the Scrum Master role, the reverse transition—Scrum Master to project manager—is often smoother.

One story described a project manager who, after struggling with an agile transition, joined a Scrum Master community, paid for certification, served as a Scrum Master for two years, and eventually became an agile coach, emphasizing curiosity and humility as key to success.

It depends. Opinions varied, with many stating that the suitability of a project manager as a Scrum Master depends on the team, product, business, and especially the people involved.

Another participant highlighted the biggest pain point: in Scrum, many responsibilities (budget, release dates, stakeholder expectations) fall to the Product Owner, which can be uncomfortable for a traditional project manager.

The most important factor, according to the community, is a mindset shift—from command‑and‑control supervision to a guiding, supportive, and service‑oriented agile mindset.

Project managers who adopt agile thinking become champions of transformation, acting as agile engines that focus on delivering user value rather than siloed functions.

Conversely, project managers with only partial agile knowledge can become obstacles, speaking agile terminology while behaving like traditional managers.

Roles in agile teams are defined by responsibilities, not by who holds them, so a project manager can evolve into a Scrum Master, a Product Owner, or even an agile coach, depending on experience and career goals.

In some organizations, project managers may simultaneously handle traditional project duties (contracts, client interaction) and agile responsibilities (coaching, Scrum Master duties), becoming “agile project managers” who consider agile contracts and scaling.

For organization‑wide agile transformation, it is crucial that project‑management offices train and certify their project managers in agile practices; otherwise, agile coaching may remain superficial and fade when coaches leave.

A final tip for project managers: understand basic software engineering, coding, and testing activities to better empathize with the team and build consensus.