Pair Programming Estimates comparision

For adaptation of pair programming several people feel about the burn down chart (Man hours estimations).

Let’s say a task for estimation of 10 hours for a single developer. When the same is done in pairing Statics are as below:

Sub Task Single Pair Pairing Advantage
Design and analysis 3 to 4 hours 2 hours Brain storming and better solution design comes up when pairing
Coding and Implementation 3 to 4 hours 3 to 4 hours Better code without need of further peer code review. Several faults are caught then and there while pairing
Overall tesing 1 to 2 hours 1 to 2 hours More scenarios are covered when two brains are working together
Refactoring/Modification 1 to 2 hours 1 hour Lesser need to refractor and impact analysis is quick.
Over all 10 16 hours Better code quality and solution comes up (when you feel stuck, you have some support all the time to motivate)

In short, the productivity of two developer working alone compared to two developers working together is always higher in terms of quality, performance, bugs and overall solution.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s