Bjørn Stabell 白熊

The final practice Arlo described was team-owned tasks. Avoiding assigning tasks to people is very important to encourage team responsibility, which leads to team accountability, which is a necessary requisite to building strong self-organizing teams.

I’m sure you’ve seen all kinds of code. In fact, just by reading the code you can very often tell who wrote it. The code base reflects who wrote it. The same applies to code bases written by teams. If you have two teams you’ll have two completely different code bases. If you have one team managing two products, you’ll probably end up with one product that can be configured into two.

Again, this is nothing new, but the way they do it in conjunction with promiscuous pairing is a bit new: Arlo’s teams would assign tasks to computers. You’d have the “red box” and the “blue box”, and tasks would stay with the computer while developers would cycle through.

• Part 1: The agile experiment
  • Safe is for weenies
  • Metrics
  • “Meta process”
  • What did they learn?
• Part 2: Practice: Promiscuous pairing
• Part 3: Practice: Least-qualified implementor
• Part 4: Practice: Team-owned tasks
• Part 5: Arlo’s agile experiment summary

This entry was posted on Friday, July 13th, 2007 at 04:08 and is filed under Exoweb, Python, FOSS, Django, Programming. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.