Hi
I have a change request form that is a bit long.
TABLE OF CONTENTS
DESCRIPTION AND REASON FOR CHANGE
IMPACT OF NOT MAKING THE CHANGE
SUPPORTING INFORMATION
FUNCTIONAL AND TECHNICAL ANALYSIS (CONSULTANT)
REVIEW OF PROJECT IMPACT (PROJECT MANAGER)
RECOMMENDATION (PROJECT MANAGER)
DECISION (CHANGE CONTROL BOARD OR STEERING TEAM)
It uses about 5 pages.
Is it ok for me to create a much more simplified version of the form for very minor changes such as when someone wants to re-label a field on a web app form Saving Changes...
There goes my anonymity!! - Doh!
Now everyone knows who's asking the stupid questions:O) Saving Changes...
Taralyn Frasqueri-MolinaSenior Project Manager| Independent ContractorPasadena, Ca, United States
While I'm all for elaboration, I think my fellow PMs tend to complicate processes more than what's necessary. Since not every project is the same, then not every process will be the same on the "robustness" scale either.
My smaller projects don't need a 5 page change request form. The few simple questions are - who wants the change, why they want the change, how will the change impact the schedule and budget, was the change approved.
If I need something more robust for larger projects, I still use the basic change request form from the small projects first.
So IMHO, it is okay for you to create a much more simplified version of your form. You have my permission :)
Thanks again for your words of wisdom Taralyn. Saving Changes...
Sylvie EdwardsProfessor/Program coordinator| Durham College (DC)Whitby, Ontario, Canada
In most cases I find that for it to be used a Change request form should about fit in a ONE PAGE space. It should also be tracked in some database where is will get boiled down to the specifics of the approval process (i.e. originator, stops along the way and final approval or deferral).
Most people have a problem with change requests being done, making them too long will stop them from doing them altogether. I have seen on large, more complex projects where the content brings the total to about 2 or 3 pages but that is the most that you should aim for. Saving Changes...
Mick GavinPMO Co-Ordinator| NHS PensionsFleetwood, United Kingdom
A change request is basically a mini business case i.e. the justification for making the necessary change - key elements such as who, what, why etc should be easily captured within a single page/form - additional detailed information such as requirements documents or other technical documents can be included as attachments when necessary - there are plenty of templates along these lines freely available on the web Saving Changes...
Thanks for these great nuggets.
I really appreciate you all taking time out to help Saving Changes...
Elizabeth HarrinDirector| RebelsGuideToPM.comLondon, England, United Kingdom
Hi Iain, if you have the authority to create a new form, just create one. Use it for a bit and see what happens. If you don't have enough info for the change board, add a bit more in until it meets everyone's needs. Five pages for a change to a web form is excessive, and you'll soon annoy users and the project managers. I say streamline as much as possible! See if you can get your new 'small change' form on one page. Ours is just over a page and yet it includes all of the elements you described, except Table of Contents, Recommendation (it assumes that if the change form has been completed we do actually want to do the change, as the change analysis is done separately) and (bizarrely) Decision. I will have to look into that last one! Saving Changes...
