Timeline for How should I report delays caused by software slowness to my supervisor?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 22, 2014 at 13:04 | comment | added | 17 of 26 | My point is simply that in order to get a process changed you need to prove to management that it's causing problems. Generally, the only way to prove something in this scenario is to somehow measure it. | |
| Oct 21, 2014 at 21:28 | comment | added | SJuan76 | Waiting for the project the fail and THEN reporting why it has failed would hardly be seen as helpful... "Yes boss, we knew the deployment was slow so we took the effort to measure how much it took. Not to inform you before the shit hit the fan, just to cover our asses". Measure, record AND report. | |
| Oct 21, 2014 at 20:30 | comment | added | Zibbobz | The time taken for each 'process' isn't set in stone though. And we really can't avoid it, either. They have no control over these standards, and these are computer programming processes, which can't be skipped. Though I can make a note of how long they take to complete. | |
| Oct 21, 2014 at 20:27 | history | answered | 17 of 26 | CC BY-SA 3.0 |