Dears, we all know that requirements should be signed by the busniess user to ensure accountability. however, what if we make the BA himself signs the requirements? what problems you can think of can arise from such a practice especially when there is an auditing team that checks the documentation and deliverables
Awaiting your thoughts
Yazid:
If the BA signs off in addition to the subjuect matter experts, I guess that could be ok, although I do not see any benefit doing to such. What benefit do you see?
However, if you mean having the BA signoff instead of the SME, then that is not a good idea. This would be like having a programmer do systems-level testing on his own work. It does not work as the person who developed the code (or the requirements spec) is largely blind to his/her own omissions / mistakes.
Tony
Thanks for your reply ajmarkos
If you mean by SME the user (i.e. the owner of the project) then, yes the BA is replacing him in the sign-off activity. the reason for this is when one of the business users rejects to sign the requirements document, so a possible change in the process is to make the BA himself do the sign-off instead of the users to guarantee owning a sign-off document for every single project
Yikes, don't do that. Requirements belong to the Business, not the BA. If the business doesn't agree with the requirements, they will reject wahtever solution is delivered, so don't proceed without business approval.
Sign-off is not a desired thing, business approval is. A sign-off is just a means of recording approval.
I agree with what David said. Having a BA be "the" signoff on the requirements doc is kind of like the car salesman being the deal-cementing signoff on a car sales order. (If such was the case, I would immediately switch careers!)
brought to you by enabling practitioners & organizations to achieve their goals using: