【文章內(nèi)容簡介】 31 this year, about 4 months from the project start date of September 1. . Risk Assessment Risk Area Assessment Impact Mitigation Communication and Collaboration High This is a temporary team. It will be lack of practices of cooperating and municating between team members. Have a weekly meeting and a bi weekly report. Use GOOGLE Code Manager to control Code vision and issues Staffing Resources Medium 1. Success of project depends on ability to members with credible experience in the technical areas. 2. Resource conflicts or shortages will cause that the project cost and schedule (primarily schedule) could overrun 1. Share technical issues, experience and information in each member in order to improve personal ability. 2. Create an alternate resource plan for critical tasks. Cost Medium Potential requirement change cost and maintenance cost. Develop a total life cycle cost estimate during concept validation as part of the milestone decision. And establish a change control process. Schedule Medium This project will be developed about 4 months. Due to the spare time each member spent, it is difficult to manage schedule. Strictly, each member must spend not less than 7 hours in each week. And each member must ensure the timely deliverable. Scope Low Successful pletion of concept validation will result in a clientwide implementation. Quality Unknown This risk factor will depend on the results of concept validation. Strictly SQA process control. . Project Deliverables Deliverable Due date Quantities Required Delivery Location Project plan Week 4 Project planning includes development of the overall project team structure, the various activities, effort and work plan that will form the basis of the project management throughout the project lifecycle. It will provide an integrated planning for CMS project, such as timeline and milestone, staffing resource distributed, risk estimation and mitigation. PM System requirements specification Week 4 The system requirement specification should describe the functional requirements of the system in precise detail. When possible, it identifies the entities (ponents, sections, and areas of functionality) that make up the Designer Project Plan for Content Management System Of MTA Organization： Final Fantasy Project Plan Number： Page 6 Owner: sweeper Approved by ： jane Date： 10/16/20 Version system and characterizes the properties, states, functions, and interrelationships of each entity. According to the requirement of MTA and industry information, the document will describe a business case study and scope, functional and nonfunctional requirement. SQA plan Week 6 The Software Quality Assurance Plan (SQAP) defines the techniques, procedures, and methodologies that will be used to assure timely delivery of the software that meets specified requirements within project resources. The SQAP describes the SQA activities to be performed and defines a set of standardized techniques for performing those activities. SQA Design document Week 6 It forms the interface between the requirements document and the code itself and describes how the software will be constructed. It will include system use case, database structure, and user interface and so on. Designer Test plan Week 7 A Test Plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. Tester Midterm progress review and presentation Week 8 Review the pleted deliverables, sum up issues, and share experience. PM Source code Week 9 Deliver the piled source code for the first time, including wholly or partly function. Programmer Test results report Week 11 A Test Result Report is a document that formally summarizes the results of all testing. Tester Defect log Week 11 The Defect Log records all defects/issues reported by team members and customers and gives a clear indication of the quality of the software application. Various statistics can be generated from the defect log, such as the number of Open defect, number of Fixed defect, etc. Tester Programmer Post project report Week 14 The Post Project Review consists of activities performed by a project team at the end of the project39。s life cycle (or at the end of significant phases of work) to gather information on what worked well and what did not, so that future projects can benefit from that learning. PM Presentation on the project Week 15 Show overall project for client, including issues, experience, evaluation, etc. PM CMS Week 15 Deploy a real environment to ensure normal running. PM . Schedule and Budget Summary . Schedule and Milestone This project will be divided into three phases to plete, and total time is about 4 months. The following represent key project milestones, with estimated pletion dates: A1 Initial Team Formation Meeting PM 09/01/08 09/01/08 Project Plan for Content Management System Of MTA Organization： Final Fantasy Project Plan Number： Page 7 Owner: sweeper Approved by ： jane Date： 10/16/20 Version A2 Team formation notice PM 09/02/08 09/07/08 A3 Build Project Plan PM 09/08/08 09/27/08 A4 Finish Requirement Analysis Designer 09/08/08 09/27/08 B1 Build SQA Plan SQA 09/28/08 10/12/08 B2 Finish Design Designer 09/28/08 10/12/08 Change Plan Sync Update1 PM 10/13/08 10/13/08 Change SRS Sync Update1 Designer 10/14/08 10/14/08 Change Design Doc Sync Update1 Designer 10/15/08 10/15/08 B3 Build Test Plan Tester 10/13/08 10/19/08 B4 Finish Coding Coder 10/13/08 11/02/08 B5 Midterm progress review and presentation PM 10/20/08 10/26/08 C1 Test and Fix Defect Coder/Tester 11/03/08 11/16/08 C2 Finish Test Tester/PM 11/17/08 12/01/08 C3 Finish deploy PM 12/02/08 12/17/