I would describe a functional spec as a contract between the product team and the development team that defines all the modules that needs to be implemented in the product so that the dev team can figure out the technical requirements. This is NOT applicable for a truly agile model, is somewhat useful for a semi-agile environment and is quite essential for older traditional models. But I think the origin of a functional spec is from older models. In semi-agile environments it is created in tandem with design documentation and updated as the design iterates. In older models it is created after the design phase is done. (obviously this is very inefficient).

Sent from my iPhone
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help

Reply via email to