0

There are 3 issues in Kanban.

enter image description here

As per the screenshot, my team should finish issues in the order 1-3-2, right? 1st issue should be delivered before starting 2nd issue, right?

0

As per the screenshot, my team should finish issues in the order 1-3-2, right? 1st issue should be delivered before starting 2nd issue, right?

No. The backlog in a Kanban board is ordered in order of importance, so the most important stuff to work on next should be at the top. This mostly tells you something about the order in which tasks are started, but it does not necessarily say anything about the order in which they are completed.

If you have multiple people on your team, it will be rare that you only have a single ticket that is being worked on, unless your tickets cover a huge amount of work that can easily be shared out among the team members. It is also a given that not all tickets on your backlog will be exactly the same size, even if you try to break them down until they are all of comparable size. This means that a smaller ticket that is picked up later can be completed before a larger ticket that was started first.

It can be that you have dependencies between tickets, for example that ticket 2 needs the results from ticket 1 before meaningful work can be done on it. Such relations are sometimes unavoidable, but the more you hve them, the harder it becomes to do project planning in a meaningful way, because a delay in one task can cause a huge ripple effect in the timeline of the whole project.

| improve this answer | |
  • 1
    But if he can make it work (the whole dev team working on the same task w/o stepping on each other shoes too often) - he should do so. – Stanislav Bashkyrtsev Jun 16 at 12:18

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.