IT项目开发项目计划(英文)

1、 可修改 欢迎下载 精品 Word 可修改 欢迎下载 精品 Word 可修改 欢迎下载 精品 WordProject Plan ForContent Management System Document Revision #1.3Date of Issue: 2021-10-13Project Manager: SweeperApproval SignaturesApproved by: Business Project LeaderApproved by: IM/IT Project Leader SweeperPrepared by: Business Project ManagerPre

2、pared by: IM/IT Project ManagerJaneEmmaReviewed by: Quality Assurance ManagerTable of Contents TOC o 1-3 h z u HYPERLINK l _Toc211435657 Document Change Control PAGEREF _Toc211435657 h 3 HYPERLINK l _Toc211435658 1.Project Overview PAGEREF _Toc211435658 h 4 HYPERLINK l _Toc211435659 1.1.Purpose, Sco

3、pe, and Objectives PAGEREF _Toc211435659 h 4 HYPERLINK l _Toc211435660 1.2.Assumptions, Constraints and Risks PAGEREF _Toc211435660 h 4 HYPERLINK l _Toc211435661 Assumptions PAGEREF _Toc211435661 h 4 HYPERLINK l _Toc211435662 Constraints PAGEREF _Toc211435662 h 4 HYPERLINK l _Toc211435663 Risk Asses

4、sment PAGEREF _Toc211435663 h 5 HYPERLINK l _Toc211435664 1.3.Project Deliverables PAGEREF _Toc211435664 h 5 HYPERLINK l _Toc211435665 1.4.Schedule and Budget Summary PAGEREF _Toc211435665 h 6 HYPERLINK l _Toc211435666 Schedule and Milestone PAGEREF _Toc211435666 h 6 HYPERLINK l _Toc211435667 Budget

5、 PAGEREF _Toc211435667 h 7 HYPERLINK l _Toc211435668 1.5.Evolution of the Plan PAGEREF _Toc211435668 h 8 HYPERLINK l _Toc211435669 1.6.References PAGEREF _Toc211435669 h 8 HYPERLINK l _Toc211435670 1.7.Definitions and Acronyms PAGEREF _Toc211435670 h 8 HYPERLINK l _Toc211435671 2.Project Organizatio

6、n PAGEREF _Toc211435671 h 9 HYPERLINK l _Toc211435672 2.1.External Interfaces PAGEREF _Toc211435672 h 9 HYPERLINK l _Toc211435673 2.2.Internal Structure PAGEREF _Toc211435673 h 9 HYPERLINK l _Toc211435674 2.3.Roles and Responsibilities PAGEREF _Toc211435674 h 9 HYPERLINK l _Toc211435675 3.Managerial

7、 Process Plans PAGEREF _Toc211435675 h 10 HYPERLINK l _Toc211435676 3.1.Startup Plan PAGEREF _Toc211435676 h 10 HYPERLINK l _Toc211435677 Estimates PAGEREF _Toc211435677 h 10 HYPERLINK l _Toc211435678 Staffing PAGEREF _Toc211435678 h 10 HYPERLINK l _Toc211435679 Resource Acquisition PAGEREF _Toc2114

8、35679 h 11 HYPERLINK l _Toc211435680 Project Staff Training PAGEREF _Toc211435680 h 11 HYPERLINK l _Toc211435681 3.2.Work Plan PAGEREF _Toc211435681 h 12 HYPERLINK l _Toc211435682 Work Breakdown Structure PAGEREF _Toc211435682 h 12 HYPERLINK l _Toc211435683 Schedule Allocation PAGEREF _Toc211435683

9、h 13 HYPERLINK l _Toc211435684 Resource Allocation PAGEREF _Toc211435684 h 13 HYPERLINK l _Toc211435685 Budget Allocation PAGEREF _Toc211435685 h 13 HYPERLINK l _Toc211435686 3.3.Project Tracking Plan PAGEREF _Toc211435686 h 13 HYPERLINK l _Toc211435687 Issues Management PAGEREF _Toc211435687 h 13 H

10、YPERLINK l _Toc211435688 Schedule Control PAGEREF _Toc211435688 h 14 HYPERLINK l _Toc211435689 Budget Control PAGEREF _Toc211435689 h 14 HYPERLINK l _Toc211435690 Quality Control PAGEREF _Toc211435690 h 14 HYPERLINK l _Toc211435691 Reporting PAGEREF _Toc211435691 h 14 HYPERLINK l _Toc211435692 Proje

11、ct Metrics PAGEREF _Toc211435692 h 14 HYPERLINK l _Toc211435693 3.4.Risk Management Plan PAGEREF _Toc211435693 h 15 HYPERLINK l _Toc211435694 3.5.Project Closeout Plan PAGEREF _Toc211435694 h 15 HYPERLINK l _Toc211435695 3.6.Project Review Meeting Plan PAGEREF _Toc211435695 h 15 HYPERLINK l _Toc2114

12、35696 4.Technical Process Plans PAGEREF _Toc211435696 h 16 HYPERLINK l _Toc211435697 4.1.Process Model PAGEREF _Toc211435697 h 16 HYPERLINK l _Toc211435698 4.2.Infrastructure PAGEREF _Toc211435698 h 16 HYPERLINK l _Toc211435699 4.3.Product Acceptance PAGEREF _Toc211435699 h 16 HYPERLINK l _Toc211435

13、700 5.Supporting Process Plans PAGEREF _Toc211435700 h 16 HYPERLINK l _Toc211435701 5.1.Configuration Management PAGEREF _Toc211435701 h 16 HYPERLINK l _Toc211435702 5.2.Verification and Validation PAGEREF _Toc211435702 h 17 HYPERLINK l _Toc211435703 5.3.Documentation PAGEREF _Toc211435703 h 17 HYPE

14、RLINK l _Toc211435704 5.4.Quality Assurance PAGEREF _Toc211435704 h 18 HYPERLINK l _Toc211435705 5.5.Reviews and Audits PAGEREF _Toc211435705 h 18 HYPERLINK l _Toc211435706 5.6.Problem Resolution PAGEREF _Toc211435706 h 18 HYPERLINK l _Toc211435707 5.7.Subcontractor Management PAGEREF _Toc211435707

15、h 18 HYPERLINK l _Toc211435708 5.8.Process Improvement PAGEREF _Toc211435708 h 18 HYPERLINK l _Toc211435709 6.Additional Plans PAGEREF _Toc211435709 h 19 HYPERLINK l _Toc211435710 Annex A - Bi-weekly progress report PAGEREF _Toc211435710 h 19 HYPERLINK l _Toc211435711 Annex B - Project Risk Checklis

16、t PAGEREF _Toc211435711 h 19Document 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 th

17、e 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

18、/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 IssueAuthorsBrief Description of Change0.12021-09-09SweeperBuild Doc0.22021-09-19JaneRevision0.32021-09-20JaneRevision0.52021-09-23SweeperRevisio

19、n0.62021-09-23JaneRevision0.72021-09-25EmmaLiliJackRevision and Review0.82021-09-26JaneCheck English0.92021-09-27Sweeper Revision1.02021-09-26Project TeamRelease One1.12021-10-06SweeperAdd Review Meetings Plan1.22021-10-10JaneRelease Two1.32021-10-12SweeperUpdate Plan Sync Update1Project OverviewThe

20、 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

21、 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 ObjectivesThe project is developed for a large Manufacturing Trade Association MTA with ove

22、r 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 m

23、aking 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-

24、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 i

25、n 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, analy

26、sis, design, development, test, deploy and finally deliverable.Assumptions, Constraints and RisksAssumptionsThe 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 MT

27、A, 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

28、 who receive announcement on important events of MTA. 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

29、 the project start date of September 1.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 Manag

30、er 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,

31、 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 decisi

32、on. 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.

33、 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. Project DeliverablesDeliverableDue dateQuantities RequiredDelivery LocationProject plan Week

34、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, staff

35、ing 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 functionali

36、ty 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 planWee

37、k 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 standar

38、dized 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 pl

39、anWeek 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

40、 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 in

41、dication 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

42、 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, et

43、c.PMCMSWeek 15Deploy a real environment to ensure normal running.PMSchedule and Budget SummarySchedule 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

44、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.2Chan

45、ge 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

46、Tester/PM11/17/0812/01/08C3Finish deployPM12/02/0812/17/08C3project reportPM12/02/0812/19/08BudgetProject Cost & Time EstimatesAll project costs and dates are estimates. Projects are charged only for actual time spent. Design Phaseestimated costsKickoff meeting; requirements and preferences1daysDeve

47、lop 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 alteration

48、s 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 ti

49、me30daysProgrammer time30daysProject management15daysDocumentation10daysTraining sessions10daysQuality Assurance testing15daysQA fixes and launch preparation30daysPost-launch monitoring and support2daysFactor of safety 10%1daysBuild phase total hours143daysProject ResourceProject Role%TimeDates Need

50、ed RangeName of ManagerProject Manager15Week1-week15SweeperDesigner15Week2-week4JackProgrammer30Week6-week15LiliTester15Week10-week15JaneQA30Week5-week15Emmadocumentation5Week1-week15SweeperSystems support5Week10-week15SweeperEvolution of the PlanThe structure of this Project Plan is in compliance w

51、ith the IEEESTD10581998.After project members review the plan, the release version will be placed under configuration management.References1 WebCT - COMP5231 Project Practice and Case Studies, Hareton Leung2 DonewsBlog - Developing the Project Plan :/blog.donews /juven/archive/20*/03/03/750787.aspx,

52、 Juven3 Project Manager Union :/ 4 Capability Maturity Model* Integration CMMI, Version1.1 CMMI for Software Engineering CMMI-SW, VI. 1 Staged Representation CMU/SEI-20*-TR-029 ESC-TR-20*-029 August 20*5 A Business case for CMMI based Process Improvement, Dave Walden, General Dynamics Advance Inform

53、ation Systems, and PSM Conference July 20*.6 Simplifying development through activity-based change management, Allan Tate & Karen Wade, IBM Software Group, October 20*.7 Capability Maturity Model Integration CMMI, Version 1.lCMMI for Software Engineering CMMI-SW, VI. 1 Continuous Representation CMU/

54、SEI-20*-TR-028ESC-TR-20*-028 August 20*.8 A spiral model of software development and enhancement, Boehm, B. W. 1988, IEEE Computer, 215, 61-72.9 The six sigma project planner, Tomas Pyzdek 20*Definitions and AcronymsMTAManufacturing Trade AssociationCMSContent Management SystemSQASoftware Quality As

55、surancePMProject ManagerRUPRational Unified ProcessProject OrganizationExternal 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: Ex

56、ecutive 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

57、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.Internal Structure Project ManagerProject ManagerSQADesignersProgrammersTestersProject Tea

58、m Organizational Structure Roles and ResponsibilitiesRoleResponsibilitiesParticipantsProject SponsorUltimate decision-maker and tie-breakerProvide project oversight and guidanceReview/approve some project elementsHareton LeungCoordinate the activities of team membersOrganize team meetings Prepare Te

59、am 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 presentation

60、sSweeperContribute 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 presentatio