Laserfiche WebLink
The overall project team <br />structure suggested for <br />the proposed Munis <br />Implementation, <br />�~~ <br />�� ~~ ��"�m <br />�� � <br />m"�m <br />0 <br />�~�'� �"� <br />°�X��' ^ <br />The purpose of project <br />governance is to define the resources required to adequately establish the business needs, <br />objectives, and priorities forthe project; communicate the goals kzother project participants; and <br />provide support and guidance toaccomplish these goals. Project governance also defines the <br />structure for issue escalation and resolution, Change Control rev�ew and authority, and <br />Organizational Change Management activities. <br />The preliminary governance structure estaNishes a clear escalation path when issues and risks <br />require escalation above the Project Ma;nager level, Further refinement of the governance structure, <br />related processes, and specific roles and responsibilities occurs during the Initiate & Plan Stage. <br />The path illustrates anoverall team perspective whureTyle,andyourrenourrecoUaborateto/esoive <br />project challenges according to defined escalation paths. |nthe event Project Managers do not <br />poSsessauthority to determine a soAudon, resolve an issue, or mitigate a 6sk, Tyler Implementation <br />Management and your Steering Committee become the escalation points to triage responses prior to <br />escalation to your and Tyler Executive Sponsors. As part of the escalation process, each Project <br />Governance tier presents recommendations and supporting information to facilitate knowledge <br />transfer and issue nesmUutiom. All Executive Sponsors serve asthe final escalation point, <br />(G)inciudea statement that key personnel will be on -site for go -live and available to the extent <br />proposed for the duration ofthe project plus ninety dayoafterxo-live acknowledging that noperson <br />desigmatedas°key°tutheprojertshaNberenmovednrrep|oredwithoutthepriorvvrittem <br />concurrence nfthe City. <br />Tyler believes that a smooth transition from implementation to the production environment is critical <br />tuthe success mfour project and our clients. Tnensure that your team isuxsupported aspossible <br />during this critical time in the project, resources from the Tyler Project Team will be on -site to <br />provide guidance and ass�stamce as needed. To assist with identified c6dca| processing that occurs <br />during the first 30 days of production, Tyler Project Team resources will be on -site for the first go -live <br />week to manage issues and actions as needed, and after this period, the work is scheduled <br />remote|y. During the pUanning stage of the project, a decision will be made about the number of <br />project days that will he net aside for Go Live and Post Live Support, We are committed tm ensuring <br />48 <br />("�������), IN <br />