|
Lord Of Texas posted:Functional specs can be a humongous trap. Don't prescribe solutions, describe the user's need, and develop the criteria must be met for the users to accept a particular solution. I'm currently "working" on a project as a domain architect where to "save time" the steering committee endorsed a view to write a requirements/functional spec frankenstein that completely missed the mark (set field 'A" to this, use technology "B" that we only know about to do that). My practice formally withdrew me from the project telling them we would just do an "as built" design - if they ever went live. About two years down the track nothing has been delivered, downstream teams are screaming about the crappy requirements and complete lack of architecture. Long story short. Functional specs might have a place on your project - once the requirements are done correctly and there is a solid design signed off.
|
#
¿
Dec 25, 2014 12:49
|
|
|
|
| # ¿ Apr 27, 2024 19:35 |
|