The DevHuddle

December 30, 2008 · 1 min read

thehuddle The DevHuddle. This is a term I started using to identify what my team does to plan development work for an iteration.  Basically this is where we sync up and get everyone on  an even playing field for consistency, map out our plans and design and coordinate who is going to do what. Why a huddle? In football the team gets the orders (prioritized stories) from the coach (project manager) and then the quarterback (team lead) explains the plan and how the players (the developers) are going to carry it out.  And to illustrate the quarterback draws the plans out sometimes on the ground or in his/her hands (the whiteboard). That's why we call it the DevHuddle.

(/images/robz/the-devhuddle/ffbde964-thehuddle_2.jpg)

Photo courtesy of Jonathan Starr.

This article is part of the GWB Archives. Original Author: Robz / Fervent Coder

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.