PDF Print E-mail
Written by Ed Willis   
Saturday, 09 October 2010 09:41

Just published this on Mike Cohn's new site, Scrumpedia.† Here's an excerpt to get you started:

This article is about developing requirements. Iíve used a number of different techniques and have come to appreciate their varying characteristics and how they can be used to advantage for different project needs.

The Illuminati Approach

Likely the most common method for developing requirements Iíve seen is what Iíd call the ďIlluminatiĒ approach. In an Illuminati approach, a small cadre of senior people writes a requirements document and sends it off to the rest of the team. This can be fast and effective, providing all those senior people are actually able to speak to the complete scope of the project and find the time to do so. In practice though, my experience has been that this approach is neither particularly effective nor fast - partly because neither of those provisos tends to pan out. Beyond that, because so few people have been involved in the requirements development process, the eventual review and acceptance of the requirements will take quite a while. Similarly, this approach does a pretty poor job of informing everyone who needs to understand the requirements because most of them will only get the document - they wonít have the deep understanding of those who actually participated in developing the requirements development.

At this stage in my career, Iíd be hard-pressed to use this approach.

You can read the rest of the article on the Scrumpedia site itself,

Last Updated on Saturday, 09 October 2010 09:48