I agree with this comment totally. You don't hire the head of the mail room to be the CEO of the company. Same applies here. PM's need to know the technology and know the developers.
The PM should be responsible for the success of failure of the program. They have to know how to identify and mitagate risks. They have to have some knowledge of how long it takes to write code to ensure developers are giving accurate estimates on hours needed to complete tasks. PM's also need to be aware of what it takes to accomplish the mission. Sometimes the complexity of a solution can be over kill in relation to the time that is allowed to develope.
In many cases it is a good idea to make the Lead Architect and the PM the same person. This makes the Architect accountable for the solution to be developed and leads to less over kill.
Slashdot Mirror
I agree with this comment totally. You don't hire the head of the mail room to be the CEO of the company. Same applies here. PM's need to know the technology and know the developers. The PM should be responsible for the success of failure of the program. They have to know how to identify and mitagate risks. They have to have some knowledge of how long it takes to write code to ensure developers are giving accurate estimates on hours needed to complete tasks. PM's also need to be aware of what it takes to accomplish the mission. Sometimes the complexity of a solution can be over kill in relation to the time that is allowed to develope. In many cases it is a good idea to make the Lead Architect and the PM the same person. This makes the Architect accountable for the solution to be developed and leads to less over kill.