IT项目开发项目计划.docx

《IT项目开发项目计划.docx》由会员分享，可在线阅读，更多相关《IT项目开发项目计划.docx（24页珍藏版）》请在淘文阁 - 分享文档赚钱的网站上搜索。

1、IT项目开发项目计划ForContent Management SystemDocument Revision #1.3Date of Issue: 2008-10-13Project Manager: SweeperProject ResourceProject Role%TimeDates Needed( Range)Name of ManagerProject Manager15Week1-week15SweeperDesigner15Week2-week4JackProgrammer30Week6-week15UliTester15Week10-week15JaneQA30Week5-

2、week15Emmadocumentation5Week1-week15SweeperSystems support5Week10-week15Sweeper1.5. Evolution of the Plan The structure of this Project Plan is in compliance with the IEEE STD 1058-1998. After project members review the plan, the release version will be placed under configuration management.1.6. Ref

3、erences1 WebCT - COMP5231 Project Practice and Case Studies, Hareton Leung2 DonewsBlog - Developing the Project Plan4 Capability Maturity Model* Integration (CMMI), Version 1.1 CMMI for Software Engineering (CMMI- SW, VI. 1) Staged Representation CMU/SEI-2002-TR-029 ESC-TR-2002-029 August 20025 A Bu

4、siness 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) Integrati

5、on (CMMI), Version 1.ICMMI 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

6、)Definitions and AcronymsMTAManufacturing Trade AssociationCMSContent Management SystemSQASoftware Quality AssurancePMProject ManagerRUPRational Unified ProcessProject Organization2.1. External InterfacesPM will be responsibility for the communication bridge between the project and external entities

7、.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 MTAOffice staffs of MTA who carry out the day-to-day operation of MTA, under the direction of th

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

9、 important events of MTA.2.2. Internal StructureDesignProgrammerTestProject Team Organizational Structure2.3. Roles and ResponsibilitiesRoleResponsibilitiesParticipant(s)Project SponsorUltimate decision-maker and tie-breaker Provide project oversight and guidance Review/approve some project elements

10、Hareton LeungProject ManagerCoordinate the activities of team membersOrganize team meetingsPrepare Team Formation NoticeWrites project plansWrites system requirements documentUpdate the project plan if neededPrepare Post Project reportPrepare progress reports to client and senior managementPrepare m

11、id-term progress review and presentationPrepare final project presentationDeliver all presentationsSweeperDesignerContribute to the system requirements document Prepare design documentSweeperLiliRoleResponsibilitiesParticipant(s)Project SponsorUltimate decision-maker and tie-breaker Provide project

12、oversight and guidance Review/approve some project elementsHareton LeungWrite drafts of the user manual and installation guideProvide User TrainingReport progress to PM on a weekly basisAssist PM to prepare mid-term progress review and presentationAssist PM to prepare final project presentationJackP

13、rogrammerCode all software featuresPerform unit testingReport progress to PM on a weekly basisAssist PM to prepare mid-term progress review and presentationAssist PM to prepare final project presentationLili Jack JaneTesterPrepare test planPerform system testingPrepare Test Result reportLog all defe

14、cts 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 presentationEmma JaneQA AnalystPrepare SQA planMonitor QA activitiesReport progre

15、ss to PM on a weekly basisAssist PM to prepare mid-term progress review and presentationEmmaManagerial Process PlansThis section of the Project Management Plan specifies the project management processes for the project. This section defines the plans for project start-up, risk management, project wo

16、rk, project tracking and project close-out.2.3. Start-up PlanEstimatesThis 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 d

17、atabase, etc.So according to the above factors, we will adopt JAVA and MySQL to develop CMS project. There is not purchase cost because of free open source tools. We will use GOOGLE free code manger service to manage code and Issues, and we will post wiki on it.2.3.1. StaffingThis project team has o

18、nly five members. Each member will try their best and unleashed potential to develop this project. The following is the simple introduction of members.Sweeper: There is development experience more than ten years and rich management experience. So he will undertake PM role in the team.Lili: There is

19、rich development experience and strong coding ability. So she will undertake primary programmer role in the team. At the same time, she will analyze requirement as an assistant of primary analyst.Jack: Because of rich experience of requirement analysis, he will undertake primary analyst role. At the

20、 same time, he will also be responsibility for coding.Jane: There is rich experience of software development and comprehensive ability in the phase of software life cycle. So she will take partin each phase, such as project plan, testing, etc.Emma: there is rich experience of SQA. SQA and tester rol

21、e will suit her best.CISFnl Faalwty Sc 2007Project %： CMS4.g: 10/12/08 SunflMM： 08/29/08.04/17/09PagelDtlivryID Aetiv*LoettiMi Bacaa o4MsA1A2A3NB1B2B2.1B2.2B2.3XB4B5C1C2C3J cF8n3 Vt*9 1m- wee E.v f esPb Frsh Requreme-rt Arysa % 3X /酬：es歹k 5广C 80加 Cnar SRS Sync Jponf-XC Sy% vpomir oy09U108 12 2408 11

22、421A-L PVSGAPM tvy(XH，08 ObtJS CN2,08 C网728 0务0&/08。务2加8 098D8 盹2708 C务2&08 1208 W/28D8 1312A)8 1C“加 8 10/13/08 lCt108 1M4U8 13旧。8 13154)814201618100%100%100%93% 93%”31908 131908Coor 10114)6 11/02/06PV 22308 132628CooerTw* 11内，08 1V1&08Tew ?v 11/1W8 1geB8PV 12?0708 1222/08PV 12/0 力。8 12/2 匐082.3.2.

23、Resource AcquisitionOne Team, One Goal. The team formation is voluntary. We own the same goal - Develop a CMS product for MTA successfully.The team doesnt need to buy any hardware resource, because team members will solve the hardware resource by themselves.For software resource, the team will adopt

24、 the way of share through the internet. So software resource also has no need to be bought.2.3.3. _ Project Staff TrainingMost of members have the programming experiences with JAVA and MySQL. So members will study technique knowledge by themselves. But members are not familiar with CMS business know

25、ledge. So it is necessary for CMS business training.Because this is a temporary team, it is difficult to work together. So finally we will adopt a network meeting for a knowledge share and discussion on the internet to instead traditional face to face training.This network meeting will be holding in

26、 the phase one. In the share and discussion, team will refer to some mature CMS products in the market, and compare with the requirement of MTA in order to improve the knowledge of CMS business process.2.4. Work Plan3.2.1. Work Breakdown StructureContentTimelineContentTimeline0. Establish teamWeekl3

27、. Showing FirstWeek 140.1 Contact with members3.1 Iconically Show Product0.2 Deliver team formation.3.1.1 Widely Publicity1. Prior to coding (Research and analysis)Week 43.1.3 Milestone Mark1.1 Grope experience3.2 Control Process of Project1.1.1 Learn requirement3.2.1 Coordinate Environment Change1.

28、1.2 Milestone Mark3.2.2 Test Product System1.2 indicate blueprint and increase confidence3.2.3 Track Issues1.2.1 Define Product3.2.4 Milestone Mark1.2.2 Analyze Requirement3.3 Adjust at team best1.2.3 Establish Project Plan3.3.1 Union is strength1.2.4 Deliver Project Plan and System Requirement Spec

29、ification3.3.2 Entered into the spirit of team1.2.5 Milestone Mark3.3.3 Milestone Mark1.3 Kick off the first work4. Released (Operation and Maintenance)Week 151.3.2 Training4.1 Track and Feedback1.3.4 Milestone Mark4.1.1 Monitor Product in the market2. Development Phase (Design and Structure)Week 94

30、.1.2 Milestone Mark2.1 Comprehensive Viewpoint4.2 Summary Experience2.1.1 Consult questions with professor4.2.1 Maintenance Plan for product2.1.2 lookup CMS information4.2.2 Collect Statistical Data2.1.3 Milestone Mark4.2.3 Evaluate and Improve2.2 Control and legislators: to act as different roles4.

31、2.4 Update and Complete User Manual2.2.1 Establish Test Plan4.3 Ready for next project2.2.2 Work on the test plan4.3.1 Commendation2.2.3 Track program change4.3.2 Evaluate Members2.2.4 Preview deployment2.2.5 Deliver Test Plan, SQA Plan, Design Document2.2.6 Milestone Mark2.3 Establish a good work e

32、nvironment2.3.1 Establish work standard.2.3.2 Share Information2.3.3 Solve Conflict2.3.4 Deliver Test results report and Source Code2.3.5 Milestone MarkSchedule AllocationThe detailed timetable has been described by “CMS_GanttChart.xls”.323. Resource AllocationThe detailed HR resource has been descr

33、ibed by CMS_GanttChart.xls”. The team has no need of the other resource expect human resource and software resource.3.2.4. Budget AllocationMostly, the team will comminute through the internet and telephone. There are few meetings on the free time of weekend lessons. Team has no need to travel and g

34、o on errands. So project budget only has the workload budget.3.3. Project Tracking PlanThe free tool - Google Code will be used for the project tracking.ManageMonitor Project gainstMonitor Project PlamingMonitor ProjectMonitor Stakeholder InvolvementMilestoneAnalyzeMonitor Data ManagementMonitor rmn

35、itmentsActionsManageActionslllJssues ManagementThe following issues management procedures will be used:Major issues (any that will significantly affect the scope, schedule, or budget for the project) will be registered in the project Major Issues log.The Project Manager and Client Project Manager wi

36、ll determine how to address the issue and identify how it will affect the scope, schedule and budget for the project.On the Project Status Report, the project manager will report the issues currently being worked on, their status, and the projected date of resolution. Any critical unresolved issues

37、that are impacting the scope, time, cost, or quality of the project will be highlighted in the status report.When an issue is resolved, merged with another issue, or withdrawn, the issue log will be updated.When an issue is closed the resolution is logged and it is moved to a closed status.Minor iss

38、ues will be logged and managed using the Google Code issue tracking program, which all project participants and the Client PM will have access to.Requirements ManagementThe information contained within the Project Plan will likely change as the project progresses. While change is both certain and re

39、quired, it is important to note that any changes to the Project Plan will impact at least one of three critical success factors: Available Time, Available Resources (Financial, Personnel), or Project Quality. The decision by which to make modifications to the Project Plan (including project scope an

40、d resources) should be coordinated using the following process:Step 1: As soon as a change which impacts project scope, schedule, staffing or spending is identified, the Project Manager will document the issue.Step 2: The Project Manager will review the change and determine the associated impact to

41、the project and will forward the issue, along with a recommendation, to the Steering Committee for review and decision.Step 3: Upon receipt, the Steering Committee should reach a consensus opinion on whether to approve, reject or modify the request based upon the information contained within the pro

42、ject website, the Project Managers recommendation and their own judgment. Should the Steering Committee be unable to reach consensus on the approval or denial of a change, the issue will be forwarded to the Project Sponsor, with a written summation of the issue, for ultimate resolution.Step 4: If re

43、quired under the decision matrix or due to a lack of consensus, the Project Sponsor shall review the issue(s) and render a final decision on the approval or denial of a change.Step 5: Following an approval or denial (by the Steering Committee or Project Sponsor), the Project Manager will notify the

44、original requestor of the action taken. There is no appeal process.3.3.1. In this project, team members will act as the Steering Committer role. And the teacher will act as the Project Sponsor.3.3.2. Schedule ControlThe weekly schedule will be shown intuitively in the CMS Gantt chart, and then be sh

45、ared to team members. And the PM will release Bi-weekly Report Week half month. So for the delay tasks, PM will try to adjust resources to bring down influence.*Tags: refer to the document CMS_GanttChart.xls”.3.3.3. _ Budget ControlThis project doesnt need to control the budget, and only need to con

46、trol the plan.3.3.4. _ Quality ControlThere is a professional SQA role to control quality in this project. SQA staff will provide a SQA plan and test plan for quality control. PM and SQA staff will follow the plans to control quality.See SQA Plan, please.3.3.5. ReportingA Bi weekly report will deliv

47、er to teacher by PM. It will report current status and issues for this project.*Tags: the template of Bi weekly report refers to the Annex A.3.3.6. _ Project MetricsSome project status will be tracked and collected, including workload process status, work deviation case, defects, etc. The workload process status and work deviation ca