This question is locked. New answers and comments are not allowed.
- What is the general practice when doing Kanban with TeamPulse - use Stories board or Tasks board?
- Also, can we automatically have the status of a story updated when all its tasks are in done status?
2 Answers, 1 is accepted
0
Hi Sunil,
You can use both Story and Task boards. Task board will give you a bit more detailed view on the progress of your stories. You can setup the status workflow for both stories and tasks as you wish in the project settings. Also you can specify Work in progress limits for each state on both types of boards.
But keep in mind that in Agile and in Kanban you want to deliver new features (aka stories) to your customers as soon as possible. But not not half backed stories that only have 50%of their tasks done. Only truly done work. So tracking the story progress on task level could be a bit misleading as it wont give you enough context - a single story could be on track but many more could be waiting to be implemented or stuck somewhere else in your process.
So you can setup a board with all the stories, bugs, feedback etc you are working on and monitor the progress on the entire workload of your team. The Work In Progress limits on each column of the board will allow you to see if there are problems and bottlenecks at certain stages of your development process so you can make adjustments
We have a section in our documentation regarding Kanban:
http://docs.telerik.com/teampulse/faq/kanban
http://docs.telerik.com/teampulse/user-guide/quick-start/Track-Progress
Check it out and see if that works for you.
As for the automatically setting the state of the story when all tasks are done - we have received similar feedback but still haven't implemented it. Check out our feedback portal, vote and share what would work best for you there:
http://feedback.telerik.com/Project/8/Feedback/Details/406-tie-story-bug-and-task-statuses
http://feedback.telerik.com/Project/8/Feedback/Details/680-prompt-to-change-the-items-status-when-all-of-its-tasks-are-completed
Regards,
Georgi
Telerik
You can use both Story and Task boards. Task board will give you a bit more detailed view on the progress of your stories. You can setup the status workflow for both stories and tasks as you wish in the project settings. Also you can specify Work in progress limits for each state on both types of boards.
But keep in mind that in Agile and in Kanban you want to deliver new features (aka stories) to your customers as soon as possible. But not not half backed stories that only have 50%of their tasks done. Only truly done work. So tracking the story progress on task level could be a bit misleading as it wont give you enough context - a single story could be on track but many more could be waiting to be implemented or stuck somewhere else in your process.
So you can setup a board with all the stories, bugs, feedback etc you are working on and monitor the progress on the entire workload of your team. The Work In Progress limits on each column of the board will allow you to see if there are problems and bottlenecks at certain stages of your development process so you can make adjustments
We have a section in our documentation regarding Kanban:
http://docs.telerik.com/teampulse/faq/kanban
http://docs.telerik.com/teampulse/user-guide/quick-start/Track-Progress
Check it out and see if that works for you.
As for the automatically setting the state of the story when all tasks are done - we have received similar feedback but still haven't implemented it. Check out our feedback portal, vote and share what would work best for you there:
http://feedback.telerik.com/Project/8/Feedback/Details/406-tie-story-bug-and-task-statuses
http://feedback.telerik.com/Project/8/Feedback/Details/680-prompt-to-change-the-items-status-when-all-of-its-tasks-are-completed
Regards,
Georgi
Telerik
Visit our Ideas & Feedback portal to submit a feature request, vote on existing requests or submit general feedback.
0
SUNIL
Top achievements
Rank 2
Iron
Rank 2
Iron
answered on 23 Sep 2014, 02:38 PM
Hi Georgi,
Thanks for your reply as it helped make many things clear.
It seems user stories is a better option when sharing progress with customers, but the task board is best if used within the internal team. I hope that the auto-update of user story when tasks are updated is implemented soon since it would help minimize extra work in keeping user stories as well as tasks updated.
Also, task board is only useful if there are always going to be at least 2 tasks for a user story else its just a duplication of user stories.
Thanks for your reply as it helped make many things clear.
It seems user stories is a better option when sharing progress with customers, but the task board is best if used within the internal team. I hope that the auto-update of user story when tasks are updated is implemented soon since it would help minimize extra work in keeping user stories as well as tasks updated.
Also, task board is only useful if there are always going to be at least 2 tasks for a user story else its just a duplication of user stories.