Does anyone have a list of common reasons for IT project change requests?
Thanks. Saving Changes...
Sort By:
Mark Price PerryBusiness Driven PMO Evangelist| BOT InternationalOrlando, Fl, United States
Dear Andrew, different kinds of IT projects can have different kinds of project change requests - driven by scope, schedule, cost, quality, and risk. It seems many IT project change requests are driven by scope creep, resource constraints, and vendor/external factors. What kinds of reasons are you seeing? I look forward and hope to find other responses to your post. Thanks! -- Mark Perry, VP of Customer Care, BOT International Saving Changes...
We see many in the areas you described. We are attempting to "force" a standard set of reasons as Project Leaders execute change controls. I was just wondering if anyone had a standard list of reasons that they used in their Change Control forms. I apologize for not being specific enough in my request. Thanks! Saving Changes...
Mark Price PerryBusiness Driven PMO Evangelist| BOT InternationalOrlando, Fl, United States
Hi Andrew, in our change request form that we use for IT Projects we have a standard list of change request reasons that the project leader can tick off. They are 1) Business Change or Need, 2) Scope Change or Need, 3) Error Correction, 4) Regulatory or Compliance Requirement, and 5) other. This is pretty high level, but it serves our purposes well. I look forward to hearing from others. Best regards! Mark Perry, VP of Customer Care, BOT International Saving Changes...
Michael WoodProject Manager / Business Analyst / Business Process Improvement Guru| Independent ContractorGig Harbor, Wa, United States
Andrew, just one word of caution on change request. Within them are the stings of political agendas. Don't discount the emotions behind requests. Make the process as quantifiable and objective as possible and be sure to get the top brasses approval before implementation. Telling your stakeholders NO can have long term relationship ans support implications Saving Changes...
Great point Michael! I would also add that I have found the most effective change processes are simple enough (and consistently enforced)that it will actually be used. However, you want the request process to be such that when you point someone there for a request they think twice about how important it is. My favorite phrase to hear from a stakeholder when pointed to the change request system is "well, it's not that important" Instant change request filter! ~ Lyndsay Letellier, Senior PM, Mindavation Inc. Saving Changes...
Thanks for all of the response. Based on your input, I believe that we are headed in the right direction. The execution/implementation and emotion are the unknowns! Saving Changes...
