Timeline for When subordinate gives the stakeholders a lower time estimation
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 28, 2021 at 13:32 | comment | added | MonkeyZeus | @usr1234567 You should comment on the other answers then =) My answer explicitly abstains from the "fight fire with fire" mindset. | |
| May 28, 2021 at 9:36 | comment | added | usr1234567 | Other answers talk about firing the developer. That would lead to fear. I agree with cohesion and respect. | |
| May 27, 2021 at 19:53 | comment | added | MonkeyZeus | @usr1234567 Well that's a little short-sighted to call it fear; more like cohesion and respect. You like it when your subordinate introduces something to a contractor which you weren't aware of? You assume every stakeholder knows or cares what the heck are tests and buffers and how little or a lot it affects the project estimate. If I'm a financial stakeholder in a large-scale construction project and the project manager's subordinate acted disjointed then that would immediately raise doubts in their ability to do the project. | |
| May 27, 2021 at 19:25 | comment | added | usr1234567 | I hate it when my contractors are not allowed to speak open and without fear. Then I don't need to discuss this in a meeting, then I can write an email. I want to hear the different opinions. Every good costumer is not after the last penny but should have the well-being of his software and "his" development team in mind. | |
| May 27, 2021 at 18:20 | history | edited | MonkeyZeus | CC BY-SA 4.0 |
added 142 characters in body
|
| May 27, 2021 at 18:11 | history | answered | MonkeyZeus | CC BY-SA 4.0 |