Hey ! Just writting a quick post to avoid you being surprised if things are changing a bit in ZenHub, Discourse, etc. We are working with @danielle @Kirsten and @Rachel on process improvement, with a “try and learn” iterative spirit to refine and fine a way to handle priorization and curation in a smooth and open way.
What do we put in the dev pipeline is taken from 4 “pots”:
- sys admin backlog
- bugs packlog
- tech debt backlog
- new features backlog
For the first 3 ones it is handled usually directly on GH so I just created three columns where we can add the issues we want to enter the backlog (first level of filtering, for example we put only s3 bugs) and within it, we order by level of priority/emergency. So we know that we will take the top issues of those 4 columns to fill in the backlog.
We are not clear yet on how to do the priorization in each column, but suggestion could be:
- tech debt devs decide together with agility and consent base on tech debt and sys admin, like one suggest an order, other review and when new things come up, put it somewhere in the priority list and other will review and suggest something else if they disagree.
- product owners decide together with agility and consent base on bugs (same process)
We are still working on new feature process, the idea we are exploring is to have some voting on wishlist on “what needs to be investigated/incepted first”, inception details feature candidate and enable choose one, those feature candidates enter the new features backlog and we prioritize there, either by voting, or same way we would do for bugs and tech debt (we might not have dozens of incepted feature candidates at the same time, inception takes crazy time!). We’ll come up soon with some more refine proposal, was just sharing that so that you are not surprised to see things moving a bit in GH and Discourse