ticket reordering concern

6 views

Skip to first unread message

Sagi Mann

unread,

Apr 30, 2020, 3:09:32 PM4/30/20

to kanbanize

Hello,

I'm new to Kanban and Kanbanize. I'm working on migrating from Waterfall to Kanban on a legacy project, with a purpose of generating short release cycles. I have the following challenge and am looking for some advice:

What if developers commit changes into the main branch in one order, but QA end up testing them in some other order (because each card takes a different time to test)? For example: developers commited the following fixes in that order to the main branch: a->b->c->d->e and, after each commit, we created a build for QA. But QA ended up signing off on a, b and e only (c, d are taking too long to enter the release).

I would ideally like to collect whatever it is that QA has managed to test (a, b, e) and release it. But there is no build that includes these exact 3. If I make another special build for release - it's a new build and was not tested. Besides, how can I make such a build in the first place - all the commits at this point are already merged into a main branch and it's virtually impossible to cherry pick them.