Timeline for Iterative tasks in Machine Learning
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2023 at 18:19 | comment | added | Todd A. Jacobs♦ | Well, I understand that. But the fact that they are perennial means (at least to me) that they should be baked into the process or part of the DoD, rather than separate work items that should be tracked outside the basic workflow. As you know, I'm a big fan of avoiding "invisible work," but evergreen tasks, process flows, and Definitions of Ready/Done are pretty visible anyway. It just seems like unnecessary overhead to me, but if it works for a given team I wouldn't say it's wrong—I'd just question the necessity and utility value, is all. | |
| Mar 9, 2023 at 8:47 | comment | added | Barnaby Golden | The sub-tasks are there to allow the team to coordinate and to divide work between them. | |
| Mar 9, 2023 at 2:39 | comment | added | Todd A. Jacobs♦ | Is there a reason not to turn the evergreen sub-tasks into part of the Definition of Done? I don't understand the value of creating a perennial punch list outside of a DoD, even if some elements of the DoD then say "where applicable." | |
| Mar 7, 2023 at 11:08 | history | answered | Barnaby Golden | CC BY-SA 4.0 |