The Art of Agile Training - Day 1

October 11, 2010 · 1 min read

I'm currently taking by James Shore and Diana Larsen offered by the. 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.

!(/images/jkhines/the-art-of-agile-training---day-1/317e6289-art-of-agile-development.jpg)

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:

This article is part of the GWB Archives. Original Author: John

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.