A little over a week ago an excellent tip was published regarding software requirements – “Approaches to defining requirements within Agile teams“. While this tip directs itself to the needs of an Agile team, it serves as an excellent read for the software developer who is dealing with custom applications, and I believe applies as much to the custom development arena as Agile.
Early on in this tip there is a simple but effective chart to help when considering the level of detail one needs for appropriate requirements definition of a given project. When dealing with the smaller businesses as I do there generally isn’t a “tight” specification created regarding excpected functionality of an application. The article also points out that requirements for a “new” system are generally different than those of an application “add on”.
I also liked this articles views regarding the verbalization of requirements. Yes, as the article points out there are potential pitfalls with defining verbally – such as not necessarily “…ensuring all stakeholders are in the loop…”. However, there are very definitely times when verbal is better than written.
The article closes with a summarization of three points, is well-written throughout, and a recommended read.