【正文】 ........... 15 . Project Review Meeting Plan .......................................................................... 15 4. Technical Process Plans .................................................................................16 . Process Model............................................................................................... 16 . Infrastructure ................................................................................................. 16 . Product Acceptance ....................................................................................... 16 5. Supporting Process Plans...............................................................................16 . Configuration Management ............................................................................ 16 . Verification and Validation .............................................................................. 17 . Documentation .............................................................................................. 17 . Quality Assurance.......................................................................................... 18 . Reviews and Audits ....................................................................................... 18 . Problem Resolution........................................................................................ 18 . Subcontractor Management ........................................................................... 18 . Process Improvement .................................................................................... 18 6. Additional Plans ...............................................................................................19 Annex A Biweekly progress report ......................................................................20 Annex B Project Risk Checklist .............................................................................21 Project Plan for Content Management System Of MTA Organization： Final Fantasy Project Plan Number： Page 3 Owner: sweeper Approved by ： jane Date： 10/16/20 Version Document Change Control This section provides control for the development and distribution of revisions to the Project Charter up to the point of approval. The Project Charter does not change throughout the project life cycle, but rather is developed at the beginning of the project (immediately following project initiation approval, and in the earliest stages of project planning). The Project Charter provides an ongoing reference for all project stakeholders. The table below includes the revision number (defined within your Documentation Plan Outline), the date of update/issue, the author responsible for the changes, and a brief description of the context and/or scope of the changes in that revision. Revision Number Date of Issue Author(s) Brief Description of Change 20200909 Sweeper Build Doc 20200919 Jane Revision 20200920 Jane Revision 20200923 Sweeper Revision 20200923 Jane Revision 20200925 Emma Lili Jack Revision and Review 20200926 Jane Check English 20200927 Sweeper Revision 20200926 Project Team Release One 20201006 Sweeper Add Review Meetings Plan 20201010 Jane Release Two 20201012 Sweeper Update Plan Sync Update1 Project Plan for Content Management System Of MTA Organization： Final Fantasy Project Plan Number： Page 4 Owner: sweeper Approved by ： jane Date： 10/16/20 Version 1. Project Overview The project plan for Content Management System (CMS) of Manufacturing Trade Association (MTA) is written by Final Fantasy Company according to the original requirements of the project. It will provide a definition of the project, including the project’s goals and objectives, etc. Additionally, the Plan will serve as an agreement between the following parties: Project Sponsor, Steering Committee, Project Manager, Project Team, and other personnel associated with and/or affected by the project. . Purpose, Scope, and Objectives The project is developed for a large Manufacturing Trade Association (MTA) with over 2020 members. The purpose for this project is that MTA works closely with enterprises of all sizes to help them unlock the value of their unstructured content. The objective of deploying the CMS is to facilitate the creation and manipulation of content on a website and to enhance collaboration by making it possible to collect information generated within the anization and facilitate its distribution. The preliminary scope of the CMS defined by MTA includes: ? Tools for managing users and workflow. The separation of content and the visual display makes it easier to maintain a consistent lookandfeel across the entire website. ? Support collaboration tools such as discussion forums and document management. ? Support customized information retrieval sophisticated search tools can allow users to locate just the information they are looking for. ? Webbased interfaces to selected information in the databases can facilitate data sharing between the anization and its stakeholders. ? Make it easier for nontechnical staff to add and edit content, thus streamline the process of maintaining a website. Developing the CMS will be about 4 months. It will plete the requirement research, analysis, design, development, test, deploy and finally deliverable. . Assumptions, Constraints and Risks . Assumptions The stakeholders of MTA include: ? Executive Council of MTA, consisting of 15 executive members who made decision on running MTA ? Office staffs of MTA who carry out the daytoday operation of MTA, under the direction of the Executive Council ? MTA Members who receive newsletters and event announcements ? Universities which support some of MTA39。 Karen Wade, IBM Software Group, October 2020. [7] Capability Maturity Model) Integra