Who should give project evaluations at a high level?

Question

I just came from a discussion about who gives the best ratings for this work.

At a detailed level, I would always say that the best score comes from the person who really needs to do this work, because they have a full understanding, and this gives them a full buy-in, but at a higher level, abstraction (i.e. at general project level) I'm not sure.

I recall Chapter 5 in Peopleware, which has been showing the results of an Australian study since 1985 - the best link I could find is here .

I am particularly interested in your attention here - do you respond as a developer, architect, prject manager or something else?

Answer 1

I answer this both to the manager (present) and to the developer (past).

High level evaluations should come from the team / project leader, but with the help of the developers. They should also be presented in the form of a range - most likely, the worst case, indicating the level of reliability of each of them.

In no case can the team leader fully know everything about the project, so they will need some input from the developers, but the danger is that you get too late in the details. Equally, individual developers will not have a sufficiently wide knowledge of the project (if it is not very small) to be able to give estimates for everything.

, " " - , .

, , , , "" .

Answer 2

, , . .

, PM .

, - - , .. - . , .

- .

, , ( CPA - ). . A BA . -. .

PM , , .

Answer 3

• . , . (: , , , , , ). ( ). . , .

Answer 4

: , .

PM, , .

Answer 5

: , .

Answer 6

, . , , , , .

, , , . , , , , .

, , , , , schar. , , ..

Answer 7

(), ().

. , -.

- ( ) .

( , -, , ). , .

, , . -.

x x 3 .

: 40 120 .

, //. X , .