Tag Archives: Agile

Agile Process

Cutcaster photo 100202812 Frustrated woman with incompetent mechanic in backgroundI was out at Agile Prague earlier this week. There were many great presentations on building up better processes and a particularly interesting one by Linda Rising on the introduction of agile into organizations. However in talking with many of the people during breaks and dinners etc especially attendees I noticed different problems that people were having in real life.

They had the wrong people

No amount of process will fix this problem. If I take a bunch of people that don’t know how to actually produce decent code that works my process won’t fix it. They can’t actually build the wrong thing let alone the right thing if they can figure it out. I might be able to get away with teaching them to actually produce but now I have bigger issues. Can you imagine if you had to teach your mechanic how to change your oil so that he could actually change yours?

Its feasible to train such a team but it will be very expensive and time consuming, this should only be done in the worst case where other options are politically unavailable for some reasons (yes government sector I’m looking at you)

If a team is unable to produce instead of attempting to introduce small incremental changes. Consider making really big changes (like getting rid of a large portion of the team).

I think we should really at conferences be spending more time talking about big changes and how to know when to use them. We should also spend more time talking about how to build a team of the right people. I know this is not as interesting of a topic but it seems there are many more people with this issue than those in cases where they have a well executing team that they want to improve.

Pair Programming Harmful?

There was an interesting article over on tech crunch today. It discussed Harvard and Professor and surgeon Atul Gawande’s recent TED talk.

It also goes into arguments on whether pairing is better or worse for creativity. Very interesting article overall.

I find however that they miss one key aspect of pair programming. Its fun. I like pair programming because its far more fun than coding by myself. I learn things and I teach things during the sessions. Its especially great when you have to work with some terrible API like the VS integration API as you have someone who is sharing the burden experience with.

Did you know that there are FactoryFactorys all over the place in the VS API? Someone seems to have known that was bad, so they renamed them FactoryProviders

This fun factor is also a recruiting tool towards getting the best developers. Hell if the best developers want to all work hung upside down from the ceiling because more blood goes to their brains and only work at night… umm ok we can work around this.

As to whether Solitude is good or bad for creativity I think its very situational. I think both can aid in the creative process or be a detriment to it. Too many variables and no one size fits all answer.