I recently introduced Kanban in our software development team, but I'm struggling with some things. The main problem I have is how to handle 'small tasks'?
Let me explain some background: We develop some products which are used by several clients. Some clients use our generic product, and some clients have some customized things.
Let's take a practical example from this week. We released the beta version a web-application to a client of us. This client did a test run, and delivered us all his little remarks. In total about 30 point or so. But this points are really small like 'move the logo 10px up', 'change the order of the list'..
How can I handle this on my Kanban board? This is how our current board looks like. The green card is a feature (to be defined userstory), the yellow ones are tasks.
If I create a task for every point of the client's feedback, my board will be overloaded (I have a WIP of 6 in the selected column). The separate tasks will only take some minutes to fix. And also, is it bad to skip some steps of the Kanban board? It doesn't need an analysis or so..
So my question is: do I need to bundle small tasks into 'fixes client x'? Or how to handle such things?