IT项目开发项目计划.doc

Project Plan ForContent Management System Document Revision #1.3Date of Issue: 2008-10-13Project Manager: Sweeper22 / 24Approval SignaturesApproved by: Business Project LeaderApproved by: IM/IT Project Leader SweeperPrepared by: Business Project ManagerPrepared by: IM/IT Project ManagerJaneEmmaReviewed by: Quality Assurance ManagerTable of ContentsDocument Change Control31.Project Overview41.1.Purpose, Scope, and Objectives41.2.Assumptions, Constraints and Risks41.2.1.Assumptions41.2.2.Constraints41.2.3.Risk Assessment51.3.Project Deliverables51.4.Schedule and Budget Summary61.4.1.Schedule and Milestone61.4.2.Budget71.5.Evolution of the Plan81.6.References81.7.Definitions and Acronyms82.Project Organization92.1.External Interfaces92.2.Internal Structure92.3.Roles and Responsibilities93.Managerial Process Plans103.1.Startup Plan103.1.1.Estimates103.1.2.Staffing103.1.3.Resource Acquisition113.1.4.Project Staff Training113.2.Work Plan123.2.1.Work Breakdown Structure123.2.2.Schedule Allocation133.2.3.Resource Allocation133.2.4.Budget Allocation133.3.Project Tracking Plan133.3.1.Issues Management133.3.2.Schedule Control143.3.3.Budget Control143.3.4.Quality Control143.3.5.Reporting143.3.6.Project Metrics143.4.Risk Management Plan153.5.Project Closeout Plan153.6.Project Review Meeting Plan154.Technical Process Plans164.1.Process Model164.2.Infrastructure164.3.Product Acceptance165.Supporting Process Plans165.1.Configuration Management165.2.Verification and Validation175.3.Documentation175.4.Quality Assurance185.5.Reviews and Audits185.6.Problem Resolution185.7.Subcontractor Management185.8.Process Improvement186.Additional Plans19Annex A - Bi-weekly progress report19Annex B - Project Risk Checklist19Document Change ControlThis 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 NumberDate of IssueAuthor(s)Brief Description of Change0.12008-09-09SweeperBuild Doc0.22008-09-19JaneRevision0.32008-09-20JaneRevision0.52008-09-23SweeperRevision0.62008-09-23JaneRevision0.72008-09-25EmmaLiliJackRevision and Review0.82008-09-26JaneCheck English0.92008-09-27Sweeper Revision1.02008-09-26Project TeamRelease One1.12008-10-06SweeperAdd Review Meetings Plan1.22008-10-10JaneRelease Two1.32008-10-12SweeperUpdate Plan Sync Update11. Project OverviewThe 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 projects 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.1.1. Purpose, Scope, and ObjectivesThe project is developed for a large Manufacturing Trade Association (MTA) with over 2000 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 organization 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 look-and-feel 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. Web-based interfaces to selected information in the databases can facilitate data sharing between the organization and its stakeholders. Make it easier for non-technical staff to add and edit content, thus streamline the process of maintaining a website. Developing the CMS will be about 4 months. It will complete the requirement research, analysis, design, development, test, deploy and finally deliverable.1.2. Assumptions, Constraints and Risks1.2.1. AssumptionsThe 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 day-to-day operation of MTA, under the direction of the Executive Council MTA Members who receive newsletters and event announcements Universities which support some of MTAs events Other trade associations which support some of MTAs events Government and IT vendors who sometimes sponsor events organized by MTA General public who receive announcement on important events of MTA. 1.2.2. ConstraintsMTA has requested that open source software be used whenever possible. In particular, they suggest using Linux operating system; Apache web server, MySQL database, etc. The CMS must be deployed by Dec. 31 this year, about 4 months from the project start date of September . Risk AssessmentRisk AreaAssessmentImpactMitigationCommunication and CollaborationHighThis is a temporary team. It will be lack of practices of cooperating and communicating between team members.Have a weekly meeting and a bi weekly report. Use GOOGLE Code Manager to control Code vision and issuesStaffing ResourcesMedium1. 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 overrun1. Share technical issues, experience and information in each member in order to improve personal ability. 2. Create an alternate resource plan for critical tasks.CostMediumPotential 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.ScheduleMediumThis 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. ScopeLowSuccessful completion of concept validation will result in a client-wide implementation.QualityUnknownThis risk factor will depend on the results of concept validation.Strictly SQA process control. 1.3. Project DeliverablesDeliverableDue dateQuantities RequiredDelivery LocationProject plan Week 4Project 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.PMSystem requirements specificationWeek 4The system requirement specification should describe the functional requirements of the system in precise detail. When possible, it identifies the entities (components, sections, and areas of functionality) that make up the 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.DesignerSQA planWeek 6The 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.SQADesign document Week 6It 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.DesignerTest planWeek 7A Test Plan is a document that describes the objectives, scope, approach, and focus of a software testing effort.TesterMid-term progress review and presentationWeek 8Review the completed deliverables, sum up issues, and share experience.PMSource codeWeek 9Deliver the compiled source code for the first time, including wholly or partly function.ProgrammerTest results reportWeek 11A Test Result Report is a document that formally summarizes the results of all testing.TesterDefect logWeek 11The 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.TesterProgrammerPost project reportWeek 14The Post Project Review consists of activities performed by a project team at the end of the projects 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.PMPresentation on the projectWeek 15Show overall project for client, including issues, experience, evaluation, etc.PMCMSWeek 15Deploy a real environment to ensure normal running.PM1.4. Schedule and Budget Summary1.4.1. Schedule and MilestoneThis project will be divided into three phases to complete, and total time is about 4 months. The following represent key project milestones, with estimated completion dates:A1Initial Team Formation MeetingPM09/01/0809/01/08A2Team formation noticePM09/02/0809/07/08A3Build Project PlanPM09/08/0809/27/08A4Finish Requirement AnalysisDesigner09/08/0809/27/08B1Build SQA PlanSQA09/28/0810/12/08B2Finish DesignDesigner09/28/0810/12/08B2.1Change Plan Sync Update1PM10/13/0810/13/08B2.2Change SRS Sync Update1Designer10/14/0810/14/08B2.3Change Design Doc Sync Update1Designer10/15/0810/15/08B3Build Test PlanTester10/13/0810/19/08B4Finish CodingCoder10/13/0811/02/08B5Mid-term progress review and presentationPM10/20/0810/26/08C1Test and Fix DefectCoder/Tester11/03/0811/16/08C2Finish Test Tester/PM11/17/0812/01/08C3Finish deployPM12/02/0812/17/08C3project reportPM12/02/0812/19/081.4.2. BudgetProject Cost & Time EstimatesAll project costs and dates are estimates. Projects are charged only for actual time spent. Design Phaseestimated costsKickoff meeting; requirements and preferences1daysDevelop design alternatives (2) - home and secondary pages3daysPresent design alternatives3daysBasic design chosen, alterations identified2daysIncorporate alternatives, develop further page designs5daysPost design updates for review and feedback3daysReceive client feedback2daysIncorporate final alterations and post5daysSign-off on design1daysDesign phase project management5daysDesign phase total30daysDesign Phase Cost-Reduction Option:If clients can choose a design and complete all alterations on it in 2 reviews instead of 3, cost of design phase can be reduced.Build phase estimated costsDesigner time30daysProgrammer time30daysProject management15daysDocumentation10daysTraining sessions10daysQuality Assurance testing15daysQA fixes and launch preparation30daysPost-launch monitoring and support2daysFactor of safety 10%1daysBuild phase total hours143daysProject ResourceProject Role%TimeDates Needed( Range)Name of ManagerProject Manager15Week1-week15SweeperDesigner15Week2-week4JackProgrammer30Week6-week15LiliTester15Week10-week15JaneQA30Week5-week15Emmadocumentation5Week1-week15SweeperSystems support5Week10-week15Sweeper1.5. Evolution of the Plan The structure of this Project Plan is in compliance with the IEEESTD10581998. After project members review the plan, the release version will be placed under configuration management.1.6. References1 WebCT - COMP5231 Project Practice and Case Studies, Hareton Leung2 DonewsBlog - Developing the Project Plan /juven/archive/2006/03/03/750787.aspx, Juven3 Project Manager Union 4 Capability Maturity Model* Integration (CMMI), Version1.1 CMMI for Software Engineering (CMMI-SW, VI. 1) Staged Representation CMU/SEI-2002-TR-029 ESC-TR-2002-029 August 20025 A Business case for CMMI based Process Improvement, Dave Walden, General Dynamics Advance Information Systems, and PSM Conference July 2002.6 Simplifying development through activity-based change management, Allan Tate & Karen Wade, IBM Software Group, October 2004.7 Capability Maturity Model) Integration (CMMI), Version 1.lCMMI for Software Engineering (CMMI-SW, VI. 1) Continuous Representation CMU/SEI-2002-TR-028ESC-TR-2002-028 August 2002.8 A spiral model of software development and enhancement, Boehm, B. W. (1988), IEEE Computer, 21(5), 61-72.9 The six sigma project planner, Tomas Pyzdek (2003)1.7. Definitions and AcronymsMTAManufacturing Trade AssociationCMSContent Management SystemSQASoftware Quality AssurancePMProject ManagerRUPRational Unified Process2. Project Organization2.1. External InterfacesPM will be responsibility for the communication bridge between the project and external entities.Customer - A large Manufacturing Trade Association (MTA) with over 2000 members.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 day-to-day operation of MTA, under the direction of the Executive Council MTA Members who receive newsletters and event announcements Universities which support some of MTAs events Other trade associations which support some of MTAs events Government and IT vendors who sometimes sponsor events organized by MTA General public who receive announcement on important events of MTA.2.2. Internal Structure Project ManagerSQADesignersProgrammersTestersProject Team Organizational Structure 2.3. Roles and ResponsibilitiesRoleResponsibilitiesParticipant(s)Project SponsorUltimate decision-maker and tie-breakerProvide project oversight and guidanceReview/approve some project elementsHareton LeungProject ManagerCoordinate the activities of team membersOrganize team meetings Prepare Team Formation NoticeWrites project plans Writes system requirements document Update the project plan if neededPrepare Post Project reportPrepare progress reports to client and senior managementPrepare mid-term progress review and presentationPrepare final project presentation Deliver all presentationsSweeperDesignerContribute to the system requirements documentPrepare design documentWrite drafts of the user manual and installation guideProvide User TrainingReport progress to PM on a weekly basis Assist PM to prepare mid-term progress review and presentationAssist PM to prepare final project presentationSweeperLiliJackProgrammerCode all software featuresPerform unit testingReport progress to PM on a weekly basisAssist PM to prepare mid-term progress review and presentation Assist PM to prepare final project presentationLiliJackJaneTesterPrepare test planPerform system testingPrepare Test Result reportLog all defects foundAssist Designer to write drafts of the user manual and installation guideReport progress to PM on a weekly basisAssist PM to prepare mid-term progress review and presentation- Assist PM to prepare final project presentationEmmaJaneQA AnalystPrepare SQA planMonitor QA activitiesReport progress to PM on a weekly basisAssist PM to prepare mid-term progress review and presentationEmma3. Managerial Process PlansThis section of the Project Management Plan specifies the project management processes for the project. This section defines the plans for project startup, risk management, project work, project tracking and project closeout.3.1. Startup Plan3.1.1. EstimatesThis project is a timer plan, so it must be completed in the official hour. MTA has requested that open source software be used whenever possible. In particular, they suggest using Linux operating system, Apache web serve, MySQL database, etc. So according to the above factors, we will adopt JAVA and MySQL t