Basically nothing gets back from the right to the left in any case (except of things from todo going back to backlog). When we encounter a bug fixing it is still a part of testing phase. If developers wouldn't fix bugs a blocker in test column would emerge, quickly followed by filling limits in earlier stages.

We don't have very strict iterations of testing – it's often case when we're going through tests and developer instantly starts fixing bugs which are submitted. In this moments it would be even hard to say whether a "sticky note" is under development or under tests because it's under both.

Keeping bug fixing as a part of testing stage just feels easier.

I don't agree on 3 boards. I work a lot switching sticky notes between backlog and todo (setting priorities) and it would be strange to have them in different places. It's not like in Scrum that priorities are set once every iteration. Sometimes it works that way but sometimes I change todo list twice a week.

It also works for the team to see what we're going to do in middle- and long-term perspective. To give you one example – we decided not to do any administration GUI at the moment, but it sits there in the backlog so we already know we can prepare some hooks to make later development smooth.

Another thing is RTS which I clear from time to time to clear the board a bit. It doesn't clutter the board much anyway since usually notes are stuck there one on another.

Clearing RTS column is going to work while we start deploying our project in production environment rigidly. We may add a limit for the column then.

Question for you. In your testing area you say that you fix bugs there too. Is that correct, or if you encounter a bug does it go back to dev? Thanks.