Process improvement experiments

Hi everyone ! After the delivery train catchup this morning I said I would sum up the discussion and new adjustments we did on ZenHub.
Now there are:

  • 4 backlogs column where we put bugs / sys admin / tech debt / features that are ready to be put in the pipe (dev ready)

  • 1 dev ready column where we put the high level epics for feature and some tech debt (like spree), and stories for bugs, tech debt, sys admin. The idea is to enable better visibility and understanding of the whole team of what are the priorities, and enable to include bugs and tech issues in between epics so we get them done as well.
    Given discussion on limiting WIP is seems the plan is to limit to

      3 epics (including tech epics like spree upgrade or api work)
      5 bugs
      5 tech issues (tech debt and sys admin)
    
  • Then 1 column per epic where we can prioritize stories. So if a dev jump on epic n°2 (because epic 1 is almost done and would take too much time to dive into it), she can then expand the column for this epic and take the top issue.

That’s a summary of it, and we propose to test and see if that feels better for everyone !

3 Likes