Example: Project Change Request
Ref: Control Project/Scenario 1
Project Name / Software Development Project nameProject Manager / Person A / Organization / Organization name-1
Requested by / Person B / Organization / Organization name-2
Submitted by / Person B / Date Requested / Date1
Evaluated by / Developer,
Subject Matter Expert
Person C/Interface Designer / Date Evaluated / Date2
Decided by / Person B / Date Decided / Date3
Change Request Identification(Provided by the project manager)
Change Request # / 123
Change Title / Change behavior of dialog 53
Change Request Details(Provided by the requestor)
Description / Make dialog 53 a three page wizard rather than a single form
Justification / The most important information should be collected first. We want to highlight this on a separate wizard page.
Note the preliminary estimate comes to 4 additional hours of work to make this change. Because the cost is minimal, the improvement is worth it.
Cause / N/A
Priority / High
Evaluation (Provided by the evaluation team) Include as appropriate:
Scope / This is one of 20 very similar dialogs in the application. We have tested paper prototypes of the wizard with users in comparison with the other dialogs that gather similar information. Users find the inconsistency between the use of form-based dialogs and this wizard confusing. Consistency of user experience was identified as a crucial requirement for this application.
Schedule / To change all dialogs to wizards would involve:
- Reworking 10 completed dialogs at an estimated 20 hours per dialogue.
- For the 10 dialogs to be built, we add 4 hours per dialogue.
We have one developer working on dialogs and this work is on the critical path. Allowing 30 hours of billable time per week, the impact on schedule is 8 week.s
Cost / 240 hours x $75/hours = $18,000
Quality / Quality would be reduced if stand-alone request implemented, but would be OK if retrofit to other similar dialogs.
Risk / Minimal, but takes time.
Project management / None
Evaluator’s priority / Low
Alternatives and recommendation / Not recommended.
Recommend instead a small tweak to the design on this dialog to highlight the critical field and to provide a clear explanation of the importance of this field in the data validation error message. This change has no impact on the schedule or cost.
Implementation Options (Provided by the project manager)
Quality, in particular, user experience is a driving constraint. Our only option if we accept the change is to expand the scope of the change to include all dialogs or don’t implement this change. If we do this, we can shorten the schedule by one week if we pay overtime.
Decision/Rationale: (Sponsor and/or customer)
Approved
Denied
Place on Hold
The wizard doesn’t buy us enough to make it general through out the application. The evaluator team’s alternative is a very good. Implement with their recommended alternative.
Change RequestDecision Signatures
Project Manager
______
(Signature) (Date)
Name
Position
Organization
Decision Maker
______
(Signature) (Date)
Name
Position
Organization
Example—Change Request Form v2.0Page 1 of 3