Taoufik EiadehProject Manager| HuaweiAbu Dhabi, Az, United Arab Emirates
There is an increasing demand for software project managers recently, and PMs to some extent must be aware or understand coding, SDLC, and how coders work.
Therefore, PMs need to deeply understand the software work envirnment in order to deliver projects successfully. Saving Changes...
i believe PM should be an expert if the organizations wants to create an exceptional product. PM should have a background on computer science. Be knowledgable in programming languages, algorithms, front and back end architecture, virtualization, networks, security. Nowadays is completely possible to domain all these topics.
Of course it's completely possible to manage software projects knowing zero about computer science but guess it would be "hard days" for the PM. Saving Changes...
Peter RapinSubject Matter Expect; Project Delivery| Independent ConsultantOntario, Canada
You make me think of a one-man band competing with a thirty-piece orchestra.
Your PM doesn't need a team, he needs servants.
There's a big gap between knowing everything and knowing zero. I'm guessing the compromise is knowing some and relying on your team for the specifics. Saving Changes...
Taoufik EiadehProject Manager| HuaweiAbu Dhabi, Az, United Arab Emirates
Dec 23, 2020 11:36 AM
Replying to Adrian Carlogea
...
If the team members are some sort of contingent workers such as contractors or consultants what you are saying could be implemented.
However when the team members are permanent employees this would not be possible. For a permanent employee, working on a project is just a work assignment and nothing more. The employee's line manager is responsible for the work the team member is performing and not the PM. I personally saw a case where a project team member was actually a manager having around 5-6 team leads under him and in total over 70 direct and indirect reports. The PM was a consultant. It would be impossible for a contingent worker to appraise a permanent employee that is also a manager in his own right.
Since in software development it is not possible to provide accurate estimates it is very easy for software developers not to reach the so called business-based targets. A PM that does not know how to code would just say: I don't care you haven't reached your targets so poor performance. A software developing manager on the other hand could say that the developer has done an extraordinary work in those circumstances. That's why appraisals should be done by people from the same line of work as those being appraised.
Then the conclusion will be that the software PM must have strong knowledge in the software domain in order to lead his/her project successfully. Saving Changes...
Taoufik EiadehProject Manager| HuaweiAbu Dhabi, Az, United Arab Emirates
Dec 23, 2020 2:17 PM
Replying to Thomas Walenta
...
Maybe this 2019 book by David Epstein can help to understand why a (project) manager better be a generalist than a specialist.
"Range: Why Generalists Triumph in a Specialized World"
Available on Blinkist.
I think so, as a PM should be a generalist.
Thanks for sharing the book. Saving Changes...
Agree with most infact all the posts above. Just to add, with Agile taking precedence over traditional projects, non coder PM's have transitioned either to Product owner or servant leader Scrum Masters after certifications. Some hands-on coder PM have joined scrum teams or SME subject matter experts, individual contributors, etc to satisfy there craving for coding, technical stuff. Saving Changes...
Larry MinerFounder and Sr. Project Management of Decision Memory Systems| Decision Memory SystemsBath, Oh, United States
The quick answer is yes. If you're PMing a software project and you do not understand what being said, presented, and tracked you're in for a long haul, but also you need to ask questions and if you can't it's not your project to manage.
...
1 reply by Adrian Carlogea
Jan 19, 2021 10:12 AM
Adrian Carlogea
...
That's why in some software development projects I have seen the so called technical project managers. These are people who have started as developers and then got training (an experience) in management and project management. They are paired with (non-technical) project managers and manage the technical aspects of the projects.
The technical PMs takes responsibility for the technical part of the project and makes decisions in this area. The PM in this case still does not have full control over the project but at least he should not worry about making technical decisions.
I think a PM should know the basics and the principal keywords/schemes/functions/coding languages/interfaces/technologies that are used in the industry where the project is executed. BUT... you do not need to be a programmer yourself.
Better understanding of the coding principles will give you better results with the stakeholder engagement processes (enhanced exchanges and dialogue with the development team, better understanding of the problems from a development point of view and so on...). Saving Changes...
The quick answer is yes. If you're PMing a software project and you do not understand what being said, presented, and tracked you're in for a long haul, but also you need to ask questions and if you can't it's not your project to manage.
That's why in some software development projects I have seen the so called technical project managers. These are people who have started as developers and then got training (an experience) in management and project management. They are paired with (non-technical) project managers and manage the technical aspects of the projects.
The technical PMs takes responsibility for the technical part of the project and makes decisions in this area. The PM in this case still does not have full control over the project but at least he should not worry about making technical decisions. Saving Changes...
You don't need to be an expert in coding but understand the basic foundations of Software Development, main risks, test practices, error correction, and Quality standards. Of Course, if you are a Software Engineer, it's a plus when managing a Software Development project. Saving Changes...
