This question is locked. New answers and comments are not allowed.
Just as in Backlog Management, there's a need for Sprint Management (Current workload).
Personally I prefer a hierarchy approach rather than "Boards". More information is managed in central location for a sprint.
- The Story board & Task board don't show bugs that are assigned for the current sprint.
- Also there needs to be the ability to add tasks to Bugs. Just like a story it can be worked on my multiple people. Part of it can be tested early, while a secondary part of the bug is still being worked on.
- The time associated to tasks from bugs should affect the burndown.
- If bugs are associated to a User Story, it's helpful to show that relationship in the Sprint Management.
- Have the ability to show a "work-in-progress" bug as another task, and be able to convert it to a bug, if it needs to be carried over. Anything not fixed in the current sprint is now considered a bug.
Personally I prefer a hierarchy approach rather than "Boards". More information is managed in central location for a sprint.
- Time left on tasks (Can view in one column). Let's me know if someone needs help on a task or if it can be broken out.
- Is there a blocker on the task, show with an icon without requiring extra steps of explaining why. A comment can always be added.
- Maybe you want to group multiple bugs to be fixed together with one user story.
- One story could have multiple bugs "shake out", and you want to track it with the story. It's easier to see them all grouped together in a linear fashion.