up for kanban w/ Huboard?

[chadwhitacre]

Over on Gittip proper we've started using Huboard to manage our dev process kanban-style. As a follow-on to #85 I thought I would suggest that we try the same here. Yinz up for it?

Here's the board for Shields.io:

https://huboard.com/gittip/shields.io/beta

Click the "+" arrow to see the Backlog. Use filters to constrain (e.g.) to the Launch milestone.

Implementation

I've set up four workflow stages: Backlog, Ready, Work in Progress, and Review. These manifest as four labels in GitHub.

I propose that we adopt the following practices:

• Everyone is responsible for assigning their own tickets to themselves and moving their tickets through the workflow.
• Everyone gets 3 tickets under Ready, 1 under WIP, and 1 under Review.
• When your WIP is ready for review, move it to Review and unassign yourself.
• Someone else has to review and merge your code. You can't merge your own code. You can merge anyone else's code.
• If you notice a PR awaiting review, assign yourself to it. If you need to send it back for more work, move it to WIP and assign it to the original author.

Remember that kanban is pull-based. To the right of "Review" is Heroku, and it is constantly pulling, gently tugging, as if to say, "Please, give me more code to deploy!" What this means is that PRs ready for review should take precedent over WIP.

This isn't a huge project but if we want to make the January 29th deadline we're going to need some sort of discipline. Hopefully the above is light-weight and gives us some structure to keep us moving steadily forward.

Eh?

@olivierlacan @ackerdev @bryanveloso @jbowes @nathany

[chadwhitacre]

P.S. I went for Huboard over the somewhat slicker Waffle.io because Huboard is open-source:

https://github.com/rauhryan/huboard

[chadwhitacre]

@olivierlacan Can we entrust it to you to curate the tickets on the Launch milestone?

[chadwhitacre]

cc: @OriPekelman, since you seem interested in helping. :-)

[chadwhitacre]

I'm using it, anyway. :-)

[chadwhitacre]

Here's one for img.shields.io: https://huboard.com/gittip/img.shields.io/beta.

[nathany]

What's the advantage over GitHub Issues? Unless it's at a higher level of granularity? (not per-repository)

[chadwhitacre]

@nathany Higher level of granularity, yes. Could be overkill for this project. Gittip has more going on so we were struggling with process and found a higher-level tool helpful. I guess let's keep it in our back pocket if we need it?

[chadwhitacre]

Derp. Meant to "Close & Comment" but it was already closed so I accidentally reopened. :-)