Timeline for Best algorithm to sort tasks by priorities by a human
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot |
Commonmark migration
|
|
| Apr 7, 2020 at 16:03 | comment | added | Joel Harmon | @MickaelFM It's a bit different from a sprint. A sprint is the stuff you think you'll get done in two weeks (or your preferred sprint duration). If your first 20 items are all front end, and the team thinks they'll get seven done, then you still have the back end team start from item 21, even though they're lower priority. That's because the goal of a sprint is to know what will be done in two weeks, not necessarily to have the highest priority stuff done. Not all devs have the same skill sets or project context, so sometimes you skip stuff. | |
| Apr 7, 2020 at 14:36 | vote | accept | MickaelFM | ||
| Apr 7, 2020 at 14:35 | comment | added | MickaelFM | That's a really good idea to make buckets, it's like sprints in Agility, and sort tasks inside them, with the ability to move tasks between buckets, (thus changing priority) if needed. I will implement that. It does not answer directly my need to ease the reviewing of all tasks, but it will greatly improve the ordering / prioritization, and that do anwer my original question in some ways. Thank you ! | |
| Apr 7, 2020 at 12:06 | history | answered | Joel Harmon | CC BY-SA 4.0 |