Amir AliProject Manager| Northbay Solutions Pvt LtdLahore, Punjab, Pakistan
Through a poll, I got multiple comments about technical input of a project manager. I want to clarify that If a manager does one or all among following:
(1) Participate in technical/design discussions
(2) Does some technical work practically
(3) Perform testing
Is it recommended approach or he/she should focus on key management aspects like communication, risk management, monitoring, reporting, influencing etc.? Saving Changes...
Larry MinerFounder and Sr. Project Management of Decision Memory Systems| Decision Memory SystemsBath, Oh, United States
For some context here, my experience has always been a technical PM managing software or infrastructure projects. Second I was a developer for 20 years, with a lot of testing, so I understand the development and testing processes.
Given this background being in on the technical design allows me to know what the team is up against, allows me to better estimate the project, provide the team with some perspective and then manage the development in a way that has some solid understanding. I can speak to it up and down the food chain. I can't code anymore so I'm not even going to try.
Should I do some testing, yes. Otherwise again I have no overall perspective on what the team is up against. I need to understand their reasoning.
If I don't do #1 and #3 then I don't have any understanding, as a PM, of the project whether waterfall or agile and where we're "really" at on the timeline. It's the practical side of being responsible from my point of view. Saving Changes...
"Not all chemicals are bad. Without chemicals such as hydrogen and oxygen, for example, there would be no way to make water, a vital ingredient in beer."
