Requirement sign off is one of the key milestone on the Software Development Life Cycle and often considered as a dreaded milestone by the approvers or the signing authority.
Before we move on see why this is considered that way, and how do we approach this, let’s understand, why an approval is required on the requirement package.
Why sign-off is required?
When a requirement is presented for the sign-off, the requirement is basically the business analyst’s understanding of the scope, business requirements etc. Obtaining a sign-off ensures that the stakeholders goes through the understanding that the Business analyst have and fill up the gaps if any; that way, ensures that the solution requirements are captured and will be delivered in the right direction (this is the first step towards building the right product). This also helps in resolving any conflict that may arise in future where the stakeholder may change their mind on the requirement and the construction has already begun.
Why this is considered a dreaded milestone?