Clever Geek Handbook

What is the most efficient time frame for changing pairs?

In your experience, what's the most efficient time slot for changing pairs in pair programming?

Is it 90 minutes, 4 hours, a full day?

-1


source to share


4 answers


I prefer at least a couple of hours, but experimenting at intervals up to 45 minutes has shown that the optimal time is around 90 minutes.



Links, see para-programming explanation

+3


source


I believe the best idea is to split the problem you are working on into smaller logical sub-problems. Each such task should be completed in about 45 minutes (for example, a high school lesson). Programmers can switch after each such task.

Note that dividing the task is already some work on the target. Any task can (and should) be split into smaller pieces as soon as possible. It is a good idea to break up the task into smaller parts at the pair level (the team leader or manager does not need to be included in this process) - remember that agile helps groups self-organize.



Of course, if the sub-task is taking longer (more than 45 minutes), then you don't need to switch until it's complete.

+1


source


It depends on how long each task will take - if you fix minor bugs, you can change quite often; if you add a new new feature that you will keep together longer.

0


source


I've found that as soon as a discrete piece of work is done, or you start to run into an obstacle, it's always a good time to switch it over.

Instead of splitting the stream just because time is limited.

0


source






More articles:


All Articles