Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question
You can still use kanban so you can see progress, and keep the person limited to 1 task. However, having the same person do development and testing is a recipe for disaster. – CaffGeek Dec 28 '11 at 18:05
up vote 6 down vote accepted

I would suggest still using Kanban by slightly changing the process:

Person A does design            Person B does design
Person B Reviews A's Design     Person A Review's B's design
Person A does development and   Person B Does Development and Initial Testing.
initial testing
Person 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.

share|improve this answer
I would also suggest to add "writes unit tests" step along with the development. It is also a good idea to clarify what your done-done state includes (is it done when qa is done? or will it require documentation after all? will it require to be integrated as a part of done?) having clear picture for each state will help you to gain more from Kanban. – Paul Dec 28 '11 at 23:08

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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