Timeline for Is it sound project management practice to make software engineers fix bugs "off the clock"?
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 4, 2018 at 16:01 | comment | added | JimmyJames | @Krishnan "Dev time" in this graph represents the amount of time a developer initially spends on a given item, like a feature. In this graph I'm excluding time spent fixing defects. Cost is money i.e. QA and development costs money primarily because testers and developers expect to be paid. | |
May 4, 2018 at 15:24 | comment | added | Krishnan | I did not understand what the dev time and its cost. Please explain | |
Aug 4, 2016 at 20:53 | history | edited | JimmyJames | CC BY-SA 3.0 |
clarified terms to align with labels on axes
|
Aug 4, 2016 at 20:38 | history | edited | JimmyJames | CC BY-SA 3.0 |
added axes to the graph
|
Aug 4, 2016 at 20:34 | comment | added | JimmyJames | @Philipp I could probably make it more clear but essentially the x-axis is time spent on development. The y-axis is the time for each of the various related activities and or totals. That's why the blue line is straight. I'll make a better version with labelled axes. Thanks for the feedback. | |
Aug 4, 2016 at 19:13 | comment | added | Philipp | I looked at the diagram for a while but I can not tell what are the axis' on that diagram are supposed to represent. Could you label them, please? | |
Aug 4, 2016 at 15:44 | review | First posts | |||
Aug 5, 2016 at 6:49 | |||||
Aug 4, 2016 at 15:43 | history | answered | JimmyJames | CC BY-SA 3.0 |