subject: ERP Project Governance [print this page] ERP Project Governance Building suitable ERP Project Governance is essential to make certain that your ERP project is completed and also that it goes live without having a problem. It really is also one of the most commonly botched elements associated with ERP project management. And this causes it to be critical to your ERP Project Manager - a key 'get right' indeed. Though the project governance model may possibly seem obvious on the start, it's commonly adjusted by the finish of the venture - for any variety of reasons. But this really is the character of prolonged enterprise projects. It really is well worth taking a look into a procedure for figuring out the governance, and assessing individual's appropriateness in the governance scheme. The steps could possibly be: 1. Perform Stakeholders Analysis 2. Determine the Governance Organization Chart 3. Outline Individual Roles and Responsibilities 4. Get Agreement from the parties 5. Determine Critical Success Factors for the project and also the governance group and clarify how they are measured 6. Determine Risks, Outline Issues and Dependencies 7. Define The Communication Framework Choice criteria may perhaps contain: 1. Visible leadership 2. Representation of major clients 3. Representation of important support services (IT, Help desks etc.) 4. Enthusiasm for your project, and willingness to provide sponsorship 5. Availability to be engaged with supporting the project 6. Representation of Location - since ERP projects are generally multi-site, multi-region, multi-national and multi-lingual. 7. Closeness to your project team You might additionally wish to adjust the ERP Project Governance framework for diverse phases with the project: Consider who might be finest for project initiation, system selection, SI contracting, design, development, testing, acceptance, implementation, and completion stages. The governance of a solid, strong, successful ERP project will typically reduce in to a number of tiers. Just like national government, you have a type of a pyramid of people who must perform together to be able to govern the project. Leadership On the top of the pyramid may be the project leader, usually the individual who initiated the ERP project in the first place. Now, this just isn't a job of "supreme leader", but more like a president or perhaps a chairman. Any new action taken in governing the ERP project will rarely be done without their acceptance, but any and all major decisions made by the people developing the application will ought to go through them. The Design Authority Usually, the leadership team lacks time to get invovled with detailed design choices, and delegates this work to a responsible group that are accountable to them. The Design Authority participates in the design process, however the design process needs to be performed by a broad group of people representing all significant dimensions of the company. The DA reports straight to the Leadership. Project Assurance Through the entire project, and at numerous 'stage-gates' (which occur between project stages), an independent project assurance role should be included. Their function needs to be both pro-active, assisting project management in receiving engagement and inclusion, and re-active - evaluating the readiness to advance between stages. The Stakeholders Stakeholders have a major stake in the failure or success of the enterprise and ought to be brought into all key aspects of preparing the enterprise, from what sort of project, the decisions that go into designing and maintaining the enterprise resource planning system. Oftentimes, the entirety of an ERP governing system will comprise of a project manager of sorts, the stakeholders, as well as the people who actually put in the footwork of constructing the system itself. Other occasions, however, you might have... Developers Anyone who is really contributing towards the hands on construction of the ERP system should certainly get a say in it's governance. In the end, it's your computer guys who will tell you whether or not some thing can be done in the first place, who will inform you how much you can anticipate to invest on a project, how much time you can anticipate to invest in it etc. This level will inform you of what you actually ought to know from the practical, pragmatic, and smart viewpoint: Not whether or not this can work as a financial plan, but whether or not it's a smart endeavor to pursue in the first place. Typically an excess in ambition can all but ruin the best of intentions. Management Not just the management at the head office where this ERP program is being created, but the management in various places as well, as these are the individuals who will probably be affected most strongly by a new ERP system. If it merely will not perform for them, then it won't work, and that's the bottom line. You may have one or two offices that have trouble getting it together and conforming to a coherent, sensible ERP plan, but a lot more frequently , you truly shouldn't try to govern how an office runs things with out listening to the people from that workplace prior to making any decisions. Now, organizing all of these people into a cohesive governing body just isn't always simple. When you possess a certain degree of synergy, when you may have people who all have the same end purpose in mind, when they actually trust one another and personal conflict isn't really getting in the way, this could be incredibly uncomplicated, but much more typically than not, a chain of command needs to be in place, as well as a voting method, so as to ensure that you are, actually, building an ERP from collective sense and experience in the business, and not private bias or petty differences. This is why we include the ultimate member of the governing body... The Software The selection of ERP software program is fundamental; it'll constrain how your solution performs, just what processes will be possible and whether you achieve your strategic aims. ERP software tries to be comprehensive. It is intricate and involved, and while it is usually extremely configurable, most ERP Projects would want to stay clear of customisation - and sometimes they will not achieve this objective. It is a noiseless voice on the governance team, and perhaps the most powerful. Choose your ERP solution with care!
