Learn to friggin' write functional specs!!!!11
-
Just usual rant. I got a functional spec. I implemented it. The app was deployed on the server, I marked the item done. The manager (who wrote the spec) went in, claimed she did not see any changes and moved the item back to me. I went to the server and confirmed the changes are live and working as per the spec... Except that I found out that she's looking for different results than what she described in the document. Again. FUUU!! :mad: I lost track of how many times the spec has been changed after I pointed out such issues. Because somebody is going to bring it up - no, it's not the scenario where a developer misunderstood the spec. Trust me. :cool: I'm 100% sure of that, because the requirements are explicit in that place.
-
Just usual rant. I got a functional spec. I implemented it. The app was deployed on the server, I marked the item done. The manager (who wrote the spec) went in, claimed she did not see any changes and moved the item back to me. I went to the server and confirmed the changes are live and working as per the spec... Except that I found out that she's looking for different results than what she described in the document. Again. FUUU!! :mad: I lost track of how many times the spec has been changed after I pointed out such issues. Because somebody is going to bring it up - no, it's not the scenario where a developer misunderstood the spec. Trust me. :cool: I'm 100% sure of that, because the requirements are explicit in that place.
"It's just what I asked for but not what I want" comes to mind.
-
Just usual rant. I got a functional spec. I implemented it. The app was deployed on the server, I marked the item done. The manager (who wrote the spec) went in, claimed she did not see any changes and moved the item back to me. I went to the server and confirmed the changes are live and working as per the spec... Except that I found out that she's looking for different results than what she described in the document. Again. FUUU!! :mad: I lost track of how many times the spec has been changed after I pointed out such issues. Because somebody is going to bring it up - no, it's not the scenario where a developer misunderstood the spec. Trust me. :cool: I'm 100% sure of that, because the requirements are explicit in that place.
And that is why specifications should be under source control, just like your code.
Software Zen:
delete this; -
And that is why specifications should be under source control, just like your code.
Software Zen:
delete this;:thumbsup:
**_Once you lose your pride the rest is easy.
I would agree with you but then we both would be wrong._**
The report of my death was an exaggeration - Mark Twain Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am. JimmyRopes