Nima
Member
|
# Posted: 13 Jan 2007 19:18 - Edited by: Nima
Reply
In their book, 37 Signals claim that it is completely useless , yes even counterproductive to write functional requirements specifications. (http://gettingreal.37signals.com/ch11_Theres_Noth ing_Functional_about_a_Functional_Spec.php)
Now this may very well be true if you are an entrepreneur developing a web based software to sell on the web.
However, if you are a contractor who has to develop multiple custom applications for different companies, and who has to deal with all issues that ensue (billing, add-ons, scope) accurate functional requirements are an indispensable tool.
Their merit is manyfold:
- they ensure that you don't commit to something that you can't deliver
- they force your client to be precise and think everything through
- they clarify what you have to do but more importantly what you don't have to do
- hence, they enable you to charge the client for additional features he requests and ensure that you company or you don't get burned
We started developing custom software without functional requirements and slowly progressed toward a process where we require software requirements specifications (SRS) for every project.
Suffice it to say that we went from chaos, poor financial performcance, liability projects, burned resources, frustrated clients, frustrated project managers and a high degree of uncertainty (also called risk) to order, sound cash flow, clearly structured projects, fully billable resources, happy clients, motivated project managers and low risk.
Using standard software requirements specifications (SRS) has turned our business around. They can't be that bad after all.
|
