I am not looking at an project level governance, I am looking from an application perspective, who owns the system, how are enhancement requests made, who follows up with those requests etc. What is done in case the same application is used in different regions that has different requirements. Saving Changes...
Michael WoodProject Manager / Business Analyst / Business Process Improvement Guru| Independent ContractorGig Harbor, Wa, United States
These questions span a number of areas from process maturity to change management.. Certainly issues related to varied requirements across regions poses an alignment problem it satisfying one regions needs means not meeting another's.
From an application perspective I offer the following food for thought.
Who Owns the System -- From keeping it up, running and accessible, IT owns it. From being the right system for the business... the stakeholders own it, thus ownership is joint amongst the business units that benefit from its use.
Enhancement Requests - should be formal and should be prioritized in a quantitative and qualitative perspective. The stakeholders impacted need to be looped into the request vetting process to ensure it is appropriate for the business.... IT, through an application analyst, usually follows up on requests and also facilitates the impact analysis (value, implication of the change, level of effort estimates, etc.). The business case needs to be made by the requesting party.
When different regions have differing requirements yet must use the same application, the best outcome is to provide within the application options and parameters that allow each region or business unit to tailor the application to their specific needs (usually workflow, features, etc.), while keeping the data base uniform. Most of the better OFF-THE-SHELF packages provide for such tailoring. If yours is custom developed then hopefully the data structure is designed such that the application is parameter driven and thus easily tailorable,
