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

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

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

TableofContents

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

EmmaLiliJack

RevisionandReview

0.8

2008-09-26

CheckEnglish

0.9

2008-09-27

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-technicalstafftoaddandeditcontent,thusstreamlinetheprocessofmaintainingawebsite.

DevelopingtheCMSwillbeabout4months.Itwillcompletetherequirementresearch,analysis,design,development,test,deployandfinallydeliverable.

1.2.Assumptions,ConstraintsandRisks

1.2.1.Assumptions

ThestakeholdersofMTAinclude:

ExecutiveCouncilofMTA,consistingof15executivememberswhomadedecisiononrunningMTA

OfficestaffsofMTAwhocarryouttheday-to-dayoperationofMTA,underthedirectionoftheExecutiveCouncil

MTAMemberswhoreceivenewslettersandeventannouncements

UniversitieswhichsupportsomeofMTA'

sevents

OthertradeassociationswhichsupportsomeofMTA'

GovernmentandITvendorswhosometimessponsoreventsorganizedbyMTA

GeneralpublicwhoreceiveannouncementonimportanteventsofMTA.

1.2.2.Constraints

MTAhasrequestedthatopensourcesoftwarebeusedwheneverpossible.Inparticular,theysuggestusingLinuxoperatingsystem;

Apachewebserver,MySQLdatabase,etc.

TheCMSmustbedeployedbyDec.31thisyear,about4monthsfromtheprojectstartdateofSeptember1.

1.2.3.RiskAssessment

RiskArea

Assessment

Impact

Mitigation

CommunicationandCollaboration

High

Thisisatemporaryteam.Itwillbelackofpracticesofcooperatingandcommunicatingbetweenteammembers.

Haveaweeklymeetingandabiweeklyreport.

UseGOOGLECodeManagertocontrolCodevisionandissues

StaffingResources

Medium

1.Successofprojectdependsonabilitytomemberswithcredibleexperienceinthetechnicalareas.

2.Resourceconflictsorshortageswillcausethattheprojectcostandschedule（primarilyschedule）couldoverrun

1.Sharetechnicalissues,experienceandinformationineachmemberinordertoimprovepersonalability.

2.Createanalternateresourceplanforcriticaltasks.

Cost

Potentialrequirementchangecostandmaintenancecost.

Developatotallifecyclecostestimateduringconceptvalidationaspartofthemilestonedecision.Andestablishachangecontrolprocess.

Schedule

Thisprojectwillbedevelopedabout4months.Duetothesparetimeeachmemberspent,itisdifficulttomanageschedule.

Strictly,eachmembermustspendnotlessthan7hoursineachweek.Andeachmembermustensurethetimelydeliverable.

Scope

Low

Successfulcompletionofconceptvalidationwillresultinaclient-wideimplementation.

Quality

Unknown

Thisriskfactorwilldependontheresultsofconceptvalidation.

StrictlySQAprocesscontrol.

1.3.ProjectDeliverables

Deliverable

Duedate

QuantitiesRequired

DeliveryLocation

Projectplan

Week4

Projectplanningincludesdevelopmentoftheoverallprojectteamstructure,thevariousactivities,effortandworkplanthatwillformthebasisoftheprojectmanagementthroughouttheprojectlifecycle.

ItwillprovideanintegratedplanningforCMSproject,suchastimelineandmilestone,staffingresourcedistributed,riskestimationandmitigation.

PM

Systemrequirementsspecification

Thesystemrequirementspecificationshoulddescribethefunctionalrequirementsofthesysteminprecisedetail.Whenpossible,itidentifiestheentities（components,sections,andareasoffunctionality）thatmakeupthesystemandcharacterizestheproperties,states,functions,andinterrelationshipsofeachentity.

AccordingtotherequirementofMTAandindustryinformation,thedocumentwilldescribeabusinesscasestudyandscope,functionalandnonfunctionalrequirement.

Designer

SQAplan

Week6

TheSoftwareQualityAssurancePlan（SQAP）definesthetechniques,procedures,andmethodologiesthatwillbeusedtoassuretimelydeliveryofthesoftwarethatmeetsspecifiedrequirementswithinprojectresources.TheSQAPdescribestheSQAactivitiestobeperformedanddefinesasetofstandardizedtechniquesforperformingthoseactivities.

SQA

Designdocument

Itformstheinterfacebetweentherequirementsdocumentandthecodeitselfanddescribeshowthesoftwarewillbeconstructed.Itwillincludesystemusecase,databasestructure,anduserinterfaceandsoon.

Testplan

Week7

ATestPlanisadocumentthatdescribestheobjectives,scope,approach,andfocusofasoftwaretestingeffort.

Tester

Mid-termprogressreviewandpresentation

Week8

Reviewthecompleteddeliverables,sumupissues,andshareexperience.

Sourcecode

Week9

Deliverthecompiledsourcecodeforthefirsttime,includingwhollyorpartlyfunction.

Programmer

Testresultsreport

Week11

ATestResultReportisadocumentthatformallysummarizestheresultsofalltesting.

Defectlog

TheDefectLogrecordsalldefects/issuesreportedbyteammembersandcustomersand

TesterProgram

givesaclearindicationofthequalityofthesoftwareapplication.Variousstatisticscanbegeneratedfromthedefectlog,suchasthenumberofOpendefect,numberofFixeddefect,etc.

mer

Postprojectreport

Week14

ThePostProjectReviewconsistsofactivitiesperformedbyaprojectteamattheendoftheproject'

slifecycle（orattheendofsignificantphasesofwork）togatherinformationonwhatworkedwellandwhatdidnot,sothatfutureprojectscanbenefitfromthatlearning.

Presentationontheproject

Week15

Showoverallprojectforclient,includingissues,experience,evaluation,etc.

CMS

Deployarealenvironmenttoensurenormalrunning.

1.4.ScheduleandBudgetSummary

1.4.1.ScheduleandMilestone

Thisprojectwillbedividedintothreephasestocomplete,andtotaltimeisabout4months.Thefollowingrepresentkeyprojectmilestones,withestimatedcompletiondates:

A1

InitialTeamFormationMeeting

09/01/08

A2

Teamformationnotice

09/02/08

09/07/08

A3

BuildProjectPlan

09/08/08

09/27/08

A4

FinishRequirementAnalysis

B1

BuildSQAPlan

09/28/08

10/12/08

B2

FinishDesign

B2.1

ChangePlanSyncUpdate1

10/13/08

B2.2

ChangeSRSSyncUpdate1

10/14/08

B2.3

ChangeDesignDocSyncUpdate1

10/15/08

B3

BuildTestPlan

10/19/08

B4

FinishCoding

Coder

11/02/08

B5