Scrum task board: tracking task completion and who does what. #27
Comments
|
Does the integration go in both directions, so that if somebody posts an issue in github, does it get picked up by HuBoard as a story? Have you looked at waffle.io? Seems to have similar functionality. I am not familiar with either of these tools. |
|
Yeah, huboard has access to github, so it keeps both the board and github in sync. Just looked at waffle, and it looks great. Similar functionality to huboard. Waffle's interface on iOS is actually readable, unlike huboard. I'm not 100% sure, but we should be able to use either one of them simultaneously. I'll try waffle some more and see. |
|
I am pretty keen to go with either of those tools. Should we decide which one to use and make it active on all repositories? |
|
Yeah, I think so. It depends on the system that waffle uses. Huboard co-opts the issue labeling to organize issues in its interface. On Jun 28, 2016, at 4:39 PM, Thomas Pasquier <notifications@github.commailto:notifications@github.com> wrote: I am pretty keen to go with either of those tools. Should we decide which one to use and make it active on all repositories? — |
|
Ok so installed wafle there on an other project: From the github side of things the way they work seems exactly identical. One thing missing from Waffle is the milestone view (allows to see what needs to be done for release X, if that's how we plan to use milestone). If being able to have the thing presented nicely on smartphone is a big issue we could go with Waffle, otherwise stick with huboard? |
|
I'm game to try one of these. Milestones seems more important to me Barb
http://www.getpostbox.comBarbara Lerner |
|
Oki, it should be setup, please have a look there: Move the task in progress where they belong and assign them. That should also helps in Tuesdays meetings. |
You may have heard of scrum task board it looks something like this:
It would allow to track who is doing what and what needs to be done relatively easily. All wanted features are added to the "stories" column.
Once clear with the requirements of a given feature, they can be moved to the "ready" column where they will wait for assignment. (Here someone is needed to keep the "stories" clean, and make sure they progress to a ready state depending on their priority). Stories should be assigned to millestone (e.g. release number once it becomes clear).
People pick stories from the ready column and assign it to themselves. Once they start working on it they move it to the "In Progress" column. Once the task is completed it can be moved to the "Testing" column where the person responsible for merge/review on the project do his/her job (he should therefore be assigned to the task). From there the story either goes to "Done" or back to "Ready" with comments on what went wrong or what more is needed.
The good news is that there is tools for this to integrate nicely with github. I created an example on another project I work on, it looks like this:
https://huboard.com/CamFlow/camflow-dev
https://huboard.com/CamFlow/camflow-dev#/milestones
The "stories" appear as issues on github:
https://github.com/CamFlow/camflow-dev/issues
What do people think? I am happy to have a try at this with DDG-Explorer if I have the green light, then once we are comfortable with the tool extend to the other packages.
The text was updated successfully, but these errors were encountered: