The best project manager I had was a film producer moonlighting as a pm between films. The film producing experience, tight deadlines, tight budgets, scheduling, lots of cross functional teams, bringing them together at the right time etc really carried over well.
First reason, product managers at a company start getting pulled into a lot of client management stuff. They have less time to spend on the product itself and the resulting vacuum is often filled by the lead dev. The lead dev demonstrates they can fill the vacuum, so starts getting asked to fill other vacuums relating to management and hiring.
Second reason, management doesn’t have a clear image of what a “developer” role should look like in their company. E.g. at tiny startups a dev might be entirely responsible for a product and even help answer customer emails. (I’ve done that and I actually think it’s fine, as long as you and the rest of the company know that’s the deal.) At the extreme opposite end, a dev might have little autonomy and be practically writing the Python syntax version of tightly specified business logic. But most companies operate in the fuzzy middle and I think many struggle to define their concepts of dev / QA / product. In those companies, it’s easy for a dev to become someone who is officially “a developer” but with a bunch of semi-official hats.
I might have to add a third reason to my theory, now that you’ve reminded me about cost cutting.
combined with
In those companies, it’s easy for a dev to become someone who is officially “a developer” but with a bunch of semi-official hats.
results in a similar story with Devops and it's younger brother, SRE. My job role officially changed from "Devops Engineer" to "Site Reliability Engineer" when I switched jobs two years ago and I'm lacking in finding ways of differentiating the two.
It's seemingly become the default response now on Devops communities when someone makes a thread saying "I want to get into Devops, what do you do?" that the job role means 'whatever the company wants it to mean', which is how we end up with Devops practitioners and teams getting turned into kitchen sinks for dealing with anything and everything the feature development groups aren't tasked with because of a severely unchallenged assumption that the dev team brings in revenue, while the operations people consume it.
An assumption that's never said outright-mind you, but the organization and delegation of work between the two domains of functional teams, IMO says it pretty loudly.
Early on, the tech lead will be primarily an engineer and hiring manager: there's not enough people to really need a process yet, and so the tech lead lays the technical foundation while building up the team with the right people.
As the team grows, the tech lead will reduce their engineer responsibilities and start focusing on project management in order to deal with the complexities that come from a larger team.
Once the team is at a steady state, both in terms of people and process, the tech lead can focus on people management, primarily by training people to take over the other responsibilities.
I'm not saying there won't be periods where a tech lead is being stretched too far as the team transitions between these phases, but if the stretching persists for too long then something has gone wrong.
There seems to be diminishing returns for salary increases with responsibility increases.
Last couple jobs had Engineering Managers to do (1) and generally manage the team. The problem is that EMs don't really know anything about anything. Maybe at one point they were a developer and knew stuff. But since they're not in the code every day they don't know the reality of the code base and their general programming skills decay. Effectively they become a relayer of messages between the dev team and the business with lots of information being lost along the way. I much preferred the previous way.
It made sense to rebrand to other job titles so as not to attract the same wrong people full of certifications which were irrelevant to software dev.
In the end I can see it being named project management again, but only after the wrong crowd is weeded out.
I'll also point out that this stereotype is widely accepted by engineers, so even if you are a former engineer and do have the technical chops, many engineering teams out there will treat you like a secretary anyway and disregard your technical judgment. I'm a project manager but have been coding for longer than a lot of engineers I work with have been alive. I've seen the spectrum of engineers from great collaborators who treat you as a [technical and professional] equal, to arrogant assholes who treat you like you're their note-taker/janitor/servant.
For a concrete example, I remember a project manager arguing with a senior developer about what a particular wireless specification required, the project manager had a Bernie Sanders moment when she had to remind him, "I wrote the damn spec!"
I do see a new flavor of project management coming back branded as technical program management, which is more a flexible position responsible for the large cross-functional projects while filling the gaps of a dev team via process development, facilitator, and/or scrum master. Usually, this role is only necessary for large orgs with multiple teams or highly regulated industries that require a lot of coordination.
In general, I would consider this trend healthy. Managing your time and your priorities, communicating with stakeholders, etc. are all skills that all engineers should develop over time, even if just for their own personal work. At the team level, shared processes and priorities should be guided by a tech lead/engineering manager who has the incentives to keep process overhead to a minimum. Ideally, once a process has been put into place there should be very little for a dedicated project manager to do on a day-to-day basis.
Where project management skills shine most is when the work involves multiple teams and the "lowest common manager" is either too high up the org chart to be involved in the details or doesn't exist (because the coordination is between separate companies). This usually manifests as "customer success" or "technical program management" roles, though they could just as easily be called "project management".
Typically, a project manager has authority over resource allocation and resource planning, but must defer to the stakeholders for everything else (most importantly, for actual design/implementation decisions). A product manager has authority over the complete lifecycle of his product, including design, implementation and resource allocation.
One would have to articulate a lot to make a point about a project manager being directly associated with sales/revenue etc. -- the top line. "Oh yeah, the project manager can increase customer satisfaction and then contribute to upselling, especially in companies focused on farming and not much on hunting customers!" -- I agree, but it's rare now.
- Reads Jira (or whatever) and moves things around (yes, they may also add things sometimes, but I'm drawing a general distinction).
- Gantt charts.
- Tracks project status, communicates it upward.
- May also do some communicating expectations downward.
- Translates blunt assessments of the project's progress into managerese.
- May have some responsibility for keeping development processes going, especially ones that involve lots of communication (think: Agile shit, or just project status meetings generally)
- Helps unblock process-related shit.
Product manager:
- Writes to Jira a lot.
- Does market research, or works closely with those who do.
- Guides the direction of the product (e.g. which feature do we tackle next, do we pivot).
- Works closely with key stakeholders (clients, product owners, domain experts) to determine that direction.
- Sells that direction to management and such.
- May have some significant sway on final decisions for e.g. design.
- May do quite a bit of business-model analysis.
But PM/PMM roles can vary a fair bit.
I think the role of project manager is dying for a good reason. Developers can organize themselves and it is more important to have that leading person motivating the dev teams with interesting problems while respecting them -> my approach. The rest is shared between product mamager, senior developers maybe some shared delivery lead resources or the engineering manager.