User:Kenlohwh/Sticky Signoff
A project or a deliverable signoff perpetually failed to be completed.
Description
[edit]A customer may delay penning her signature on a signoff for various reasons unknown to the project manager of the seller. Each signoff session is met with a reason that the deliverable has not met one or more requirements.
Related Risks
[edit]{{help needed}}
Relevant In
[edit]- Project Management
- Business Analysis
- Process Improvement
Discussion
[edit]A customer may be reluctant to pen his signature on a signoff document fearing that there may be some incomplete features or parts that he has overlooked.
As his fear is not justifiable, he resorted to using various excuses to delay the signoff, much to the confusion and frustration of the seller. It often lead to schedule and budget overrun.
Prevention, Amelioration and Cure
[edit]Concise Signoff Checklist
[edit]To prevent a customer to come up with unending new excuses for not signing off, the seller with the buyer can come up with a signoff checklist. It should contain Test Cases which can only be checked as either passed or failed.
At the planning stage, the seller and the buyer should agree on whether a signoff is deemed if all the items are checked as passed, or a certain percentage is so, e.g. 80% of the items are checked as passed.
--Kenneth Loh (talk) 16:01, 21 August 2010 (UTC)