IT项目开发项目计划英文Word文档下载推荐.docx

IT项目开发项目计划英文Word文档下载推荐.docx

《IT项目开发项目计划英文Word文档下载推荐.docx》由会员分享，可在线阅读，更多相关《IT项目开发项目计划英文Word文档下载推荐.docx（27页珍藏版）》请在冰豆网上搜索。

Sweeper

Preparedby:

BusinessProjectManager

IM/ITProjectManager

Jane

Emma

Reviewedby:

QualityAssuranceManager

TableofContents

DocumentChangeControl3

1.ProjectOverview4

1.1.Purpose,Scope,andObjectives4

1.2.Assumptions,ConstraintsandRisks4

1.2.1.Assumptions4

1.2.2.Constraints4

1.2.3.RiskAssessment5

1.3.ProjectDeliverables5

1.4.ScheduleandBudgetSummary6

1.4.1.ScheduleandMilestone6

1.4.2.Budget7

1.5.EvolutionofthePlan8

1.6.References8

1.7.DefinitionsandAcronyms8

2.ProjectOrganization9

2.1.ExternalInterfaces9

2.2.InternalStructure9

2.3.RolesandResponsibilities9

3.ManagerialProcessPlans10

3.1.StartupPlan10

3.1.1.Estimates10

3.1.2.Staffing10

3.1.3.ResourceAcquisition11

3.1.4.ProjectStaffTraining11

3.2.WorkPlan12

3.2.1.WorkBreakdownStructure12

3.2.2.ScheduleAllocation13

3.2.3.ResourceAllocation13

3.2.4.BudgetAllocation13

3.3.ProjectTrackingPlan13

3.3.1.IssuesManagement13

3.3.2.ScheduleControl14

3.3.3.BudgetControl14

3.3.4.QualityControl14

3.3.5.Reporting14

3.3.6.ProjectMetrics14

3.4.RiskManagementPlan15

3.5.ProjectCloseoutPlan15

3.6.ProjectReviewMeetingPlan15

4.TechnicalProcessPlans16

4.1.ProcessModel16

4.2.Infrastructure16

4.3.ProductAcceptance16

5.SupportingProcessPlans16

5.1.ConfigurationManagement16

5.2.VerificationandValidation17

5.3.Documentation17

5.4.QualityAssurance18

5.5.ReviewsandAudits18

5.6.ProblemResolution18

5.7.SubcontractorManagement18

5.8.ProcessImprovement18

6.AdditionalPlans19

AnnexA-Bi-weeklyprogressreport19

AnnexB-ProjectRiskChecklist19

DocumentChangeControl

ThissectionprovidescontrolforthedevelopmentanddistributionofrevisionstotheProjectCharteruptothepointofapproval.TheProjectCharterdoesnotchangethroughouttheprojectlifecycle,butratherisdevelopedatthebeginningoftheproject（immediatelyfollowingprojectinitiationapproval,andintheearlieststagesofprojectplanning）.TheProjectCharterprovidesanongoingreferenceforallprojectstakeholders.Thetablebelowincludestherevisionnumber（definedwithinyourDocumentationPlanOutline）,thedateofupdate/issue,theauthorresponsibleforthechanges,andabriefdescriptionofthecontextand/orscopeofthechangesinthatrevision.

RevisionNumber

DateofIssue

Author（s）

BriefDescriptionofChange

0.1

2008-09-09

BuildDoc

0.2

2008-09-19

Revision

0.3

2008-09-20

0.5

2008-09-23

0.6

0.7

2008-09-25

Lili

Jack

RevisionandReview

0.8

2008-09-26

CheckEnglish

0.9

2008-09-27

Sweeper

1.0

ProjectTeam

ReleaseOne

1.1

2008-10-06

AddReviewMeetingsPlan

1.2

2008-10-10

ReleaseTwo

1.3

2008-10-12

UpdatePlanSyncUpdate1

1.

ProjectOverview

TheprojectplanforContentManagementSystem（CMS）ofManufacturingTradeAssociation（MTA）iswrittenbyFinalFantasyCompanyaccordingtotheoriginalrequirementsoftheproject.Itwillprovideadefinitionoftheproject,includingtheproject’sgoalsandobjectives,etc.Additionally,thePlanwillserveasanagreementbetweenthefollowingparties:

ProjectSponsor,SteeringCommittee,ProjectManager,ProjectTeam,andotherpersonnelassociatedwithand/oraffectedbytheproject.

1.1.Purpose,Scope,andObjectives

TheprojectisdevelopedforalargeManufacturingTradeAssociation（MTA）withover2000members.ThepurposeforthisprojectisthatMTAworkscloselywithenterprisesofallsizestohelpthemunlockthevalueoftheirunstructuredcontent.

TheobjectiveofdeployingtheCMSistofacilitatethecreationandmanipulationofcontentonawebsiteandtoenhancecollaborationbymakingitpossibletocollectinformationgeneratedwithintheorganizationandfacilitateitsdistribution.

ThepreliminaryscopeoftheCMSdefinedbyMTAincludes:

Ø

Toolsformanagingusersandworkflow.Theseparationofcontentandthevisualdisplaymakesiteasiertomaintainaconsistentlook-and-feelacrosstheentirewebsite.

Supportcollaborationtoolssuchasdiscussionforumsanddocumentmanagement.

Supportcustomizedinformationretrieval-sophisticatedsearchtoolscanallowuserstolocatejusttheinformationtheyarelookingfor.

Web-basedinterfacestoselectedinformationinthedatabasescanfacilitatedatasharingbetweentheorganizationanditsstakeholders.

Makeiteasierfornon-technical