Timeline for Is it sound project management practice to make software engineers fix bugs "off the clock"?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 10, 2017 at 15:10 | history | edited | Paddy | CC BY-SA 3.0 |
deleted 2 characters in body
|
| Aug 6, 2016 at 15:57 | comment | added | jpmc26 | @Paddy I mean straight up lying about how long a particular task will take, over-estimating it so it's enough time for feature + bug. If they were being honest, they'd give a lower estimate for the actual feature and then have separate time for the bug. I can't say I'd really blame someone in this situation, but wouldn't be exactly honest. | |
| Aug 6, 2016 at 9:13 | comment | added | Paddy | @jpmc26 I wouldn't call that padding, rather just good estimating. There will always be bugs to fix in any iteration. | |
| Aug 6, 2016 at 1:26 | comment | added | jpmc26 | Another possibility is padding other estimates to include bug fixes so they don't have to work off hours. | |
| Aug 5, 2016 at 8:26 | history | edited | Paddy | CC BY-SA 3.0 |
deleted 3 characters in body
|
| Aug 4, 2016 at 20:56 | comment | added | JimmyJames | My father saw this exact problem in (emerging market) factories decades ago where the workers were docked pay for making mistakes. The result was that mistakes would be hidden and not be found until the cost to correct them was much higher. This policy was causing really big problems and doing little to prevent mistakes. | |
| Aug 4, 2016 at 20:33 | comment | added | Dan Henderson | +1 for calling out the actual effect that such a policy is likely to have, when applied to the very personality type that predisposes a person to a career in software development. | |
| Aug 4, 2016 at 15:49 | review | First posts | |||
| Aug 5, 2016 at 6:49 | |||||
| Aug 4, 2016 at 15:47 | history | answered | Paddy | CC BY-SA 3.0 |