6 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Codeblack commented  ·  May 9, 2013 2:15 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  +1

  We usually don't break down our PBI's or user stories into sub-items. Using the kanban-board could be an alternative, but it needs some extensions and improvements.

• Matthias commented  ·  October 23, 2012 5:01 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Bugs are possibly part of the work planned for this iteration as are user stories. In our case, bugs are rarely broken down into tasks, which makes using the task board pointless.
  So I agree with the other comments that the users should be able to choose how to use the board.
  In general, I think a work item should move across the board unless it has children tasks; then those should move across the board.

• Philip Rieck commented  ·  March 18, 2012 10:10 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Broken down to tasks or not, the people getting the most use from the board are not concerned with task level information.

• Bryan Hinton commented  ·  February 17, 2012 12:58 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Having the ability to not use tasks, but simply stories on the board is critical - Agile at its core is about stories on the board - not tasks

• OsirisTerje commented  ·  January 15, 2012 1:52 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  And I am all in favour of this (have given my positive vote) (someone asked). There are two reasons for this. 1) Projects differ, people differ, sometimes the team always breaks down PBI's in tasks, but sometimes the PBI's (user stories) are so small they might not be broken down further, and developers check in code on the PBIs. Best practice is to always have sub tasks, but the tool should not enforce this. 2) Further, I find the ability to be able to handle PBI's on a board is very useful regardless of whether the PBIs are broken down into tasks or not. The PBI's move through the same sequence of states, and that can be very nicely visualized using the board.

• OsirisTerje commented  ·  January 7, 2012 2:12 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  The Task Board should show columns corresponding to all valid states for the relevant WITs. A given WI should only be allowed to move to columns valid for that type.