John Hines' Software Process Blog

A blog on Agile software development and Scrum

  Home  |   Contact  |   Syndication    |   Login
  39 Posts | 6 Stories | 43 Comments | 0 Trackbacks


The information in this weblog is provided “AS IS” with no warranties, and confers no rights.

This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.

To err is human, to forgive is divine.

Tag Cloud



I'm currently taking The Art of Agile Training by James Shore and Diana Larsen offered by the Oregon Training Network. Rob Myers is helping out, too.  I'm suffering from a bit of information overload and mild exhaustion.

Day one discussed how to use predictable, repeatable iterations as a method for completing work. We had a stand-up meeting comprised of 20 people that lasted only 7 minutes. There were plenty of collaborative exercises, and interestingly these generated a large number of unanticipated questions, many of which were addressed later in the day. I've really taken far too many notes to summarize and recount here at the moment.

The primary class-generated topic was on making geographically-dispersed teams work in an Agile environment. Agile strongly, emphatically recommends co-located teams. So for development teams with resources around the world, we heard advice such as focusing each co-located team on a functional area. And James has an essay entitled "Large Scale Agile" posted on his blog to help coordinate those teams.  There's also a link to a book covering this topic at the end of this post.

While I treasure the information that I'm getting, I'm realizing is that it can be a challenge to put it into practice.  Especially for those working in companies or teams that have been very successful following the Waterfall model of product development.

I'll end with a quietly reflective book round-up:

"Let's make this organization work in a way that works." -James Shore

Technorati tags: Agile Scrum

posted on Monday, October 11, 2010 5:34 PM