Archive for the ‘Sustainabile Pace’ Category

What is a team ground rule or team working agreement

Friday, January 2nd, 2009

The Agile FAQ has provided some information on what team working agreements and ground rules are in this article.

Some Things l Need to Know about Programming I Learned In Music College

Friday, January 2nd, 2009

Steve Freeman provides this article on how playing music relates to programming.

Tester-Developer Ratios on Agile Teams

Monday, December 22nd, 2008

Lisa Crispin provides a couple of good stories about her experience on teams and the ratio of testers to developers in this blog entry.

Velocity

Wednesday, December 10th, 2008

Dhaval Panchal defines and provides usage scenarios for capturing, using, and misusing velocity in this article.

Agile Development Practices 2008: Brian Marick’s “Seven Years Later: What the Agile Manifesto Left Out”

Tuesday, December 9th, 2008

Here is the video of Brian Marick’s keynote talk at Agile Development Practices 2008.

Beware the Hero

Monday, December 8th, 2008

Elisabeth Hendrickson describes a classroom situation that shows pitfalls of the “hero” attempting to do too much in this article.

The WordCount Simulation

Thursday, November 27th, 2008

In her Agile Testing class, Elisabeth Hendrickson conducts an exercise called the WordCount Simulation that is described in detail with this blog post.

Agile Development Practices Keynote by Brian Marick (Text)

Tuesday, November 18th, 2008

Brian again provides an essential work to the Agile community. Find out how to “work with ease” reading the text of his keynote from the Agile Development Practices conference here.

Tasty Cupcakes: Experiential Learning Games

Wednesday, October 29th, 2008

The “Tasty Cupcakes” site has a plethora of experiential learning games that may be of interest to teams, coaches, and trainers.

Agile: Anatomy of a failed project

Wednesday, October 29th, 2008

This article describes a presentation from Mitch Lacey on “When Working Software is Not Enough: A Story of Project Failure” with significant details about what lead to the failure.