I’m a huge proponent of Agile methodologies, but I have to admit, one thing I never really understood is why some people prefer story boards over tools to track projects. It always seemed to me that it would be much better to have everything in a tool in which you could run reports and more easily share data.
I asked Janet Gregory about this during a session she led at STAREAST 2011: Seven Key Factors for Agile Testing Success. Gregory explains in this video clip how the visual and physical presence of a story board provides more visibility to the team and organization.
I’ve talked to others about this who agree that a story board often can really highlight status and areas of concern that are often not so easily identified in tools. However, most people agree that in certain circumstances such as distributed teams or large teams, the use of a tool is required. In some cases, smaller teams use the story board and then someone will have the task of updating a tool appropriately so that the data can be captured electronically.
A common message amongst industry experts at the STAREAST conference is there is no single right answer. Each team must assess what works best for them, given their project and team culture.
In STAREAST: Agile testing success with Janet Gregory, you’ll find out more about Gregory’s thoughts as she talks to Lisa Crispin. Gregory and Crispin are co-authors of, “Agile Testing – A Practical Guide for Testers and Agile Teams.”
Check out our SSQ STAREAST page for more videos, tips and interviews with industry experts.