0

My team is not interested in following the principle of Jira tickets only flow forward on the board and rework happens in whatever column the problem was found.

I don’t share this method with the team but I don’t want to cause resentment but I believe it distorts the board and hides bottlenecks and disfunction.

Should I be democratic and allow them to move tickets back and forth and persist with making them understand why tickets should move forward only?

|improve this question
  • What specific problem does the team want to solve by allowing tickets to move backward? – RubberDuck Nov 22 '17 at 16:37
  • @RubberDuck they say they don’t keep track of their tickets which are being reworked after code review or re-code reviewed after rework. They want the activity the ticket is currently undergoing to reflect on the board as appose to the status of the board/team as a whole. – TheLearner Nov 23 '17 at 3:07
2

Is it working? Then don't stress it.

There are some schools of Kanban that adhere to what you are saying. It is not, however, a hard and fast rule. I tend to teach and use a two-way Kanban board as I've found it more effective.

The key to a two-way board is WIP limit. If you move something from test, back to development, then you may have to remove something from development back to the backlog queue.

Check out the slide 11, Using WIP limits, in my Requirements to Done Flow presentation for a visual example of this. It's animated so go into presentation mode.

|improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.