Paired Programming is worth the Expense

2

Posted by Lawrence Sinclair on 05 Feb 2013 at 00:39

Content_paired_programming_east_agile_-_abstract

Research has long found that paired programming makes sense. But I still regularly come across people who feel it costs twice as much for the same results.

Actual scientific experimentation has found thatfrom a financial perspective, paired programming costs about 20% more to develop a given product, but it produces that product almost twice as fast and with fewer defects. Laurie Williams and Robert Kessler put it another way in "All I Really Need to Know about Paired Programming I learned in Kindergarden"[1]:

An experiment by John Nosek at Temple University studied 15 full-time, experienced programmers working for 45 minutes on a challenging problem, important to their organization, in their own environment, and with their own equipment. Five worked individually, 10 worked...

Buzz: East Agile in Vietnam

0

Posted by Lawrence Sinclair on 18 Dec 2010 at 14:34

"East Agile ...has retained its firm commitment to pair programming and a rigorous application of Agile process ...counting among its clients twitter.com ...and jibe.com."

http://alkimie.com/?p=184

Agile Estimation - The East Agile Way

0

Posted by Anonymous on 04 Nov 2010 at 06:19

Agile Estimation Of Iterations

If you haven’t done so already, take a moment to read the blog on Reliable Estimates Using Agile.

In this blog, I will talk about the actual process of estimating an iteration and specifically how we do it at East Agile. I had the chance to take a class with Mike Cohn (right) and he is really good at explaining the estimation process. His book on estimation can be found on Amazon.

Estimating against a project that hasn’t been accepted (bidding, ROI analysis, etc.) is left for another blog.

Agile Estimation

Before You Start

Once again, lets make sure that you have everything you need to start estimation. So:

  • You are a member of the team.

  • You know your availability and all your team members availability.

  • You’ve studied and understand the...

"Managing" a Project to Success Using Agile

0

Posted by Anonymous on 26 Jul 2010 at 19:51

Agile tools shine at managing projects and providing quality. But what is required to “manage” a project to success?

What is the purpose of a project?

The purpose of a project is to provide a deliverable: a product or service. A deliverable is defined using specified requirements. Quality is meeting the specified requirements using measurements based on quantitative objective evidence.

To provide a deliverable, the following are required:

  • Tools necessary to provide the deliverable such as buildings, wrenches, computers, specifications, education material, etc.
  • Instructions provided by operation procedures, manuals, safety standards, specifications, requirements, etc.
  • Qualifications of those who are providing the deliverable. Are the people qualified? Are they being trained so they...

East Agile and Agile Tools

0

Posted by Anonymous on 21 Jul 2010 at 13:01

One of the great aspects of Agile is that it can be continually reviewed and improved through retrospection. At East Agile, we apply Scrum, an Agile management process, but with a few changes. Agile itself is a collection of tools that are available to Agile users (Pair Programming, Standup meetings, Retrospective Meetings, Test Driven Development, etc.). XP (http://www.agilealliance.org/), Scrum (http://www.scrumalliance.org/ ) and Crystal (http://alistair.cockburn.us/Crystal+methodologies ) are examples of branded systems that draw from the set of Agile tools available. As such, there is nothing wrong, and it is quite Agile, to draw the best from these branded Agile systems (just as the founders of Agile did when they choose which tools were most Agile when engineering).

Scrum, as...

Why Paired Programming?

0

Posted by Lawrence Sinclair on 20 Jul 2010 at 20:18

It is very important for us to not compromise on paired programming.

eXtreme Programming, orXP, (especially at East Agile) is an engineering process designed to create a consistent, reliable, scalable and low risk software development environment that reduces risks especially in already unstructured, uncertain and risky business ventures.Not doing full paired programming can introduce the potential to complete a project faster, but also introduces a very significant risk of catastrophic failure.We never choose to make the speed in exchange for substantially increased risk.

That is not to stay that we must pair program 100% of the time. There will be timeswhen it makes sense for a team to splittheir focus or for individuals to work alone.Examplesof this include (1) reading and...

Uniquely East Agile

0

Posted by Lawrence Sinclair on 11 Jan 2010 at 04:58

One thing that seems to be very unique about us is that we really do paired programming. This practice is not for everyone by far. A lot of people don't get it and won't get it. But for those that get it, we are one of the few deep practitioners. Pivotal Labs, of course, is another one. Just from talking to people from other leading development shops it seems like 90% or more of Ruby on Rails agile companies do not practice it to the extent that we do. Paired = higher quality & lower risk of project interruption.

Learn more about Paired Programming on Wikipedia, including information about research on its effectiveness.

Not the best screen hygiene, but a sign of good develpment

0

Posted by Lawrence Sinclair on 24 Dec 2009 at 06:11

If your screens don't look like this then (a) you have better screen hygiene than these developers, but perhaps (b) you're not doing eXtreme Programming right, and in particular, you're not doing paired programming. Having fingerprints all over the screens is an artifact of active collaborative development.

Learn more about Paired Programming on Wikipedia, including references to research on its effectiveness.

Frequently Asked Questions 15

0

Posted by Lawrence Sinclair on 20 Nov 2009 at 23:13

Development process

Please provide details of your process and the way you like to run projects. Do you use an Agile or iterative system - will we see regular releases throughout development?. Do you like to communicate via email, phone, IM? Do you have an issue tracker that you use with clients? Do you have weekly status meetings with clients? Do you send status reports every few days? Do you provide one point of contact? How do you handle change requests?


Whenever we have the option, we develop usingeXtreme Programming methodologies.Pivotal Tracker(http://Pivotaltracker.com)manages our tasks, progress, client interaction, and bugs, chores, and issues.


We askclients to provide at least 4 hours per week of time from a business or product managerwho understands the product, how it...

Coffee with East Agile

0

Posted by Lawrence Sinclair on 28 Aug 2009 at 23:33

If I were sitting down with you for a cup of coffee, this is what I'd tell you about East Agile, what we can do, and what it is like working with us. It is thirteen minutes long, but I think you will find it very enlightening and really help you get to know us.

Cheers,

-Lawrence Sinclair, CEO 

East Agile Intro Video <-- FULL 13 MINUTE VIDEO

(Download includes introduction, as well as discussions of our approach to analytics and software development)  

 

 

 

Or jump to the stream discussing our approach to agile development:

 

 

Learn about our approach to big data analytics: