In our team all task's steps are always done by the same developer. I.e for task 1, person A does design, development, and testing; for task 2, person B does does design, development, and testing, etc. Does it make sense to use Kanban in this case?
Does it make sense to use Kanban if all steps are done by the same person?
kanban
I would suggest still using Kanban by slightly changing the process:Person A does design            Person B does designPerson B Reviews A's Design     Person A Review's B's designPerson A does development and   Person B Does Development and Initial Testing.initial testingPerson B QA's person A's work   Person A QA's Person B's work.Putting all tasks with 1 developer as Chad pointed out is a recipe for disaster while not in the initial stage but most certainly down the road when maintenance on the project would be required.