Timeline for Productivity - Pushing towards 3 (at max 4) completed requests followed by code commits in a span of 8 hour interval on novel support requests
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 4, 2021 at 17:49 | comment | added | Christophe | No problem with the steps :-). I wrote "rigid" not as a blind criticism, but because in reality some support requests are user issues that would stop at capture, and sometimes the test case formulation is done at capturing when confirming the way to reproduce the error. Sometimes the test case already exist (recurring bug). And some times, correcting a typo in the code is just faster than formulating it as a solution. So some degree of flexibility will anyhow appear. | |
| Jan 4, 2021 at 17:11 | comment | added | Vahe | I can replace times, but process steps are guidelines at this point given the amount of criticism toward the appoach | |
| Jan 4, 2021 at 16:20 | history | answered | Christophe | CC BY-SA 4.0 |