- Dump initial tasks into the Dump without worrying about relationships.
- Affinitize tasks (cluster like with like), then name the task groups to avoid contriving the names of your lists/groups. Task groups should generally not exceed 5 business days (think of 4 days as the time box for each slice).
- Sequence unknowns/risky task group elements first and create inputs and outputs from one cluster to another if doing one set helps you do another (start with things with more outputs than inputs)
- Visualize state movement across: Not started, Unsolved, Solved, and Finished. You can indicate that using colors.
Kanban is great for disjointed ticket (reactive) work. Dumplink is excellent for whole and discrete project (meaningfully large and strategically important proactive) work, like new features or chunks of new products.
This is a great tool when kicking off a project on day one for development so PMs and developers can ensure they are seeing what is in each other's heads.