Loading Profile...
How to mark tasks and items as completed
A few people have asked how to mark tasks and backlog items as completed in Banana Scrum. The rule is extremely simple:
1) A task is marked as completed (checked off and displayed in gray) when the number of hours remaining falls to zero.
2) A backlog item is marked as completed when there is at least one task for it, and all the tasks are completed.
We decided not to implement a dedicated "completed" button, as we believe that tasks should cover all there is to complete the user story (and you can always add more tasks if needed) and obviously it wouldn't make sense to have completed items with unfinished tasks remaining.
1) A task is marked as completed (checked off and displayed in gray) when the number of hours remaining falls to zero.
2) A backlog item is marked as completed when there is at least one task for it, and all the tasks are completed.
We decided not to implement a dedicated "completed" button, as we believe that tasks should cover all there is to complete the user story (and you can always add more tasks if needed) and obviously it wouldn't make sense to have completed items with unfinished tasks remaining.
Follow this discussion to get notifications on your dashboard.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?The team is all located together with the exception of the product owner, who is on site regularly. We'll use a web-based tool for the product backlog, but tasks are only on the board. We'd like to mark user stories as complete without entering tasks, since they (and the sprint burndown) are only on the board.
I’m disappointed
-
Inappropriate?I lost 30 minutes looking for how to close a task and I was resigning with Bananascrum. I gave a last chance by looking in this forum.
If you don't put a completed task button and people already asked the question, it could mean that you need some hint in the screen where people are looking for the "complete task button".
I’m frustrated
1 Comment
Add a comment
-
Exactly, I don't like the way your did it in Banana Scrum. Any way it depend on developers and Scrum Master to make up decision which task is COMPLETED (not to some program) . -
Inappropriate?Thank you for your feedback! Now we are aware of the fact that it is not as intuitive for everybody as for us, and we will try to address this somehow in one of the future releases. -
Inappropriate?(btw you mark an item complete by marking all the tasks complete - and this is achieved by changing their estimate to 0)1 Comment Add a comment
-
RIDICULOUS! Guys I haven't seen that in any program- PLEASE change it and add complete button
Actually there is missing all board , where you could arrange tasks as:
To Do, In Progress, Ready To test, Completed/Done -
Inappropriate?Just one more user who feels a "completed" button or status would make his life complete. :) -
Inappropriate?I don't know about the rest of you but our time estimates tend to be "ESTIMATES" which some time go over and some time take less time. It seems intuitive to be able to hit a Complete button (which in turn would just set the time to 0).
Consider me another user that thinks a complete button makes sense. Seems like a natural step and I don't know about the rest of you but I look forward to striking off items from my list. -
Inappropriate?I also would like a completed button.
Something I do not understand: if I set the estimate of a task to zero, then I lose all information I had on how long I THOUGHT it was going to take. I'd really like to be able to tell how long I thought it would take versus how long it actually took.
I’m confused
-
Inappropriate?I do not feel the completed button is needed at all if you use Bananascrum for both the user stories / features and tasks. The team members simply update the remaining time of a given task to zero and that closes the task. The story points are earned when all the tasks of a story are closed. Simple, and I like it that way.
I’m happy
-
Inappropriate?Pasi, thanks for your supportive feedback. We also like it this way, because we feel task estimates should be updated daily anyway and that is how we practice Scrum. However, from a purely functional point of view there should be a simpler way of "zeroing" a task - and we'll think of one.
EMPLOYEE
