Approvals

Getting formal approval for various project stages.

Also Known As

Authorization
Quality Gate
Review and Sign Off (in Waterfall Development)
Sign Off
Sprint Review (in Scrum)
Validation

Addresses / Mitigates

Implementation Risk: Ensures that work meets the required standards and specifications before progressing.
Communication Risk: Provides formal communication of acceptance and readiness.
Conceptual Integrity Risk: Conceptual issues can be avoided by reviews and approvals

Attendant Risks

Schedule Risk: Waiting for approvals can introduce delays in the project timeline.
Coordination Risk: Requires coordination among stakeholders to provide timely sign-off.
Process Risk: Approval processes may lack required flexibility

Used By

Extreme Programming: XP involves customer approval during frequent releases and continuous customer involvement.
Scrum: Scrum requires approval during sprint reviews and at the end of each sprint.
Waterfall Development: Waterfall emphasizes formal reviews and sign-offs at the end of each phase to ensure that all stakeholders agree on the work completed and the plans for the next phase.

Description

"Approval is the action of officially agreeing to something or accepting something as satisfactory." - Approval, Wikipedia

Approval / Sign Off in software development involves getting formal approval from stakeholders at various stages of the project. This practice ensures that the work meets the required standards and specifications before progressing to the next phase, providing a formal communication of acceptance and readiness.

See: