(项目管理)IT项目开发
项目计划(英文)
ProjectPlan
For
ContentManagementSystem
DocumentRevision#
DateofIssue:2008-10-13
ProjectManager:Sweeper
ApprovalSignatures
Approvedby:BusinessProjectLeader,,Approvedby:IM/ITProjectLeader
Sweeper,,
,,
,,
Preparedby:BusinessProjectManager,,Preparedby:IM/ITProjectManager
Jane,,
,,Emma
,,
,,Reviewedby:QualityAssuranceManager
,,
TableofContents
Document Change Control3
Overview4
, Scope, and Objectives4
, Constraints and Risks4
Assessment5
Deliverables5
and Budget Summary6
and Milestone6
of the Plan8
and Acronyms8
Organization9
Interfaces9
Structure9
and Responsibilities9
Process Plans10
-up Plan10
Acquisition11
Staff Training11
Plan12
Breakdown Structure12
Allocation13
Allocation13
Allocation13
Tracking Plan13
Management13
Control14
Control14
Control14
Metrics14
Management Plan15
Closeout Plan15
Review Meeting Plan15
Process Plans16
Model16
Acceptance16
Process Plans16
Management16
and Validation17
Assurance18
and Audits18
Resolution18
Management18
Improvement18
Plans19
Annex A - Bi-weekly progress report19
Annex B - Project Risk Checklist19
DocumentChangeControl
ThissectionprovidescontrolforthedevelopmentanddistributionofrevisionstotheP
projectlifecycle,butratherisdevelopedatthebeginningoftheproject(immediatelyfoll
owingprojectinitiationapproval,andintheearlieststagesofprojectplanning).TheProj
udestherevisionnumber(definedwithinyourDocumentationPlanOutline),thedateofupdat
e/issue,theauthorresponsibleforthechanges,andabriefdescriptionofthecontextand/o
rscopeofthechangesinthatrevision.
RevisionNumber,DateofIssue,Author(s),BriefDescriptionofChange
,2008-09-09,Sweeper,BuildDoc
,2008-09-19,Jane,Revision
,2008-09-20,Jane,Revision
,2008-09-23,Sweeper,Revision
,2008-09-23,Jane,Revision
,2008-09-25,Emma
Lili
Jack,RevisionandReview
,2008-09-26,Jane,CheckEnglish
,2008-09-27,Sweeper,Revision
,2008-09-26,ProjectTeam,ReleaseOne
,2008-10-06,Sweeper,AddReviewMeetingsPlan
,2008-10-10,Jane,ReleaseTwo
,2008-10-12,Sweeper,UpdatePlanSyncUpdate1
1. ProjectOverview
TheprojectplanforContentManagementSystem(CMS)ofManufacturingTradeAssociatio
n(MTA)iswrittenbyFinalFantasyCompanyaccordingtotheoriginalrequirementsoftheproj
,includingtheproject’sgoalsandobjectiv
es,,thePlanwillserveasanagreementbetweenthefollowingparties:Pro
jectSponsor,SteeringCommittee,ProjectManager,ProjectTeam,andotherpersonnelassoc
iatedwithand/oraffectedbytheproject.
. Purpose,Scope,andObjectives
TheprojectisdevelopedforalargeManufacturingTradeAssociation(MTA)withover200
tohelpthemunlockthevalueoftheirunstructuredcontent.
TheobjectiveofdeployingtheCMSistofacilitatethecreationandmanipulationofcont
entonawebsiteandtoenhancecollaborationbymakingitpossibletocollectinformationgen
eratedwithintheorganizationandfacilitateitsdistribution.
ThepreliminaryscopeoftheCMSdefinedbyMTAincludes:
aymakesiteasiertomaintainaconsistentlook-and-feelacrosstheentirewebsite.
Supportcollaborationtoolssuchasdiscussionforumsanddocumentmanagement.
Supportcustomizedinformationretrieval-
sophisticatedsearchtoolscanallowuserstolocatejusttheinformationtheyarelo
okingfor.
Web-
basedinterfacestoselectedinformationinthedatabasescanfacilitatedatashari
ngbetweentheorganizationanditsstakeholders.
Makeiteasierfornon-
technicalstafftoaddandeditcontent,thusstreamlinetheprocessofmaintaininga
website.
,ana
lysis,design,development,test,deployandfinallydeliverable.
. Assumptions,ConstraintsandRisks
. Assumptions
ThestakeholdersofMTAinclude:
ExecutiveCouncilofMTA,consistingof15executivememberswhomadedecisiononrun
ningMTA
OfficestaffsofMTAwhocarryouttheday-to-
dayoperationofMTA,underthedirectionoftheExecutiveCouncil
MTAMemberswhoreceivenewslettersandeventannouncements
UniversitieswhichsupportsomeofMTA'sevents
OthertradeassociationswhichsupportsomeofMTA'sevents
GovernmentandITvendorswhosometimessponsoreventsorganizedbyMTA
GeneralpublicwhoreceiveannouncementonimportanteventsofMTA.
. Constraints
,th
eysuggestusingLinuxoperatingsystem;Apachewebserver,MySQLdatabase,etc.
,about4monthsfromtheprojectstartdateofS
eptember1.
. RiskAssessment
RiskArea,Assessment,Impact,Mitigation
CommunicationandCollaboration,High,
ofcooperatingandcommunicatingbetweenteammembers.,Haveaweeklymeetingandabiweekly
report.
UseGOOGLECodeManagertocontrolCodevisionandissues
StaffingResources,Medium,
eexperienceinthetechnicalareas.
(primarilys
chedule)couldoverrun,,experienceandinformationineachmembe
rinordertoimprovepersonalability.
.
Cost,Medium,Potentialrequirementchangecostandmaintenancecost.,Developatotallife
shachangecontrolprocess.
Schedule,Medium,
berspent,itisdifficulttomanageschedule.,Strictly,eachmembermustspendnotlessthan
.
Scope,Low,Successfulcompletionofconceptvalidationwillresultinaclient-
wideimplementation.,
Quality,Unknown,Thisriskfactorwilldependontheresultsofconceptvalidation.,Strict
lySQAprocesscontrol.
. ProjectDeliverables
Deliverable,Duedate,QuantitiesRequired,DeliveryLocation
Projectplan,Week4,Projectplanningincludesdevelopmentoftheoverallprojectteamstru
cture,thevariousactivities,effortandworkplanthatwillformthebasisoftheprojectman
agementthroughouttheprojectlifecycle.
ItwillprovideanintegratedplanningforCMSproject,suchastimelineandmilestone,staff
ingresourcedistributed,riskestimationandmitigation.,PM
Systemrequirementsspecification,Week4,Thesystemrequirementspecificationshouldde
,itidenti
fiestheentities(components,sections,andareasoffunctionality)thatmakeupthesystem
andcharacterizestheproperties,states,functions,andinterrelationshipsofeachentit
y.
AccordingtotherequirementofMTAandindustryinformation,thedocumentwilldescribeabu
sinesscasestudyandscope,functionalandnonfunctionalrequirement.,Designer
SQAplan,Week6,TheSoftwareQualityAssurancePlan(SQAP)definesthetechniques,procedu
res,andmethodologiesthatwillbeusedtoassuretimelydeliveryofthesoftwarethatmeetss
performedanddefinesasetofstandardizedtechniquesforperformingthoseactivities.,SQ
A
Designdocument,Week6,Itformstheinterfacebetweentherequirementsdocumentandthecod
,d
atabasestructure,anduserinterfaceandsoon.,Designer
Testplan,Week7,ATestPlanisadocumentthatdescribestheobjectives,scope,approach,an
dfocusofasoftwaretestingeffort.,Tester
Mid-
termprogressreviewandpresentation,Week8,Reviewthecompleteddeliverables,sumupiss
ues,andshareexperience.,PM
Sourcecode,Week9,Deliverthecompiledsourcecodeforthefirsttime,includingwhollyorp
artlyfunction.,Programmer
Testresultsreport,Week11,ATestResultReportisadocumentthatformallysummarizesther
esultsofalltesting.,Tester
Defectlog,Week11,TheDefectLogrecordsalldefects/issuesreportedbyteammembersandcu
isticscanbegeneratedfromthedefectlog,suchasthenumberofOpendefect,numberofFixedd
efect,etc.,Tester
Programmer
Postprojectreport,Week14,ThePostProjectReviewconsistsofactivitiesperformedbyapr
ojectteamattheendoftheproject'slifecycle(orattheendofsignificantphasesofwork)to
gatherinformationonwhatworkedwellandwhatdidnot,sothatfutureprojectscanbenefitfr
omthatlearning.,PM
Presentationontheproject,Week15,Showoverallprojectforclient,includingissues,exp
erience,evaluation,etc.,PM
CMS,Week15,Deployarealenvironmenttoensurenormalrunning.,PM
. ScheduleandBudgetSummary
. ScheduleandMilestone
Thisprojectwillbedividedintothreephasestocomplete,
efollowingrepresentkeyprojectmilestones,withestimatedcompletiondates:
A1,InitialTeamFormationMeeting,PM,09/01/08,09/01/08
A2,Teamformationnotice,PM,09/02/08,09/07/08
A3,BuildProjectPlan,PM,09/08/08,09/27/08
A4,FinishRequirementAnalysis,Designer,09/08/08,09/27/08
B1,BuildSQAPlan,SQA,09/28/08,10/12/08
B2,FinishDesign,Designer,09/28/08,10/12/08
,ChangePlanSyncUpdate1,PM,10/13/08,10/13/08
,ChangeSRSSyncUpdate1,Designer,10/14/08,10/14/08
,ChangeDesignDocSyncUpdate1,Designer,10/15/08,10/15/08
B3,BuildTestPlan,Tester,10/13/08,10/19/08
B4,FinishCoding,Coder,10/13/08,11/02/08
B5,Mid-termprogressreviewandpresentation,PM,10/20/08,10/26/08
C1,TestandFixDefect,Coder/Tester,11/03/08,11/16/08
C2,FinishTest,Tester/PM,11/17/08,12/01/08
C3,Finishdeploy,PM,12/02/08,12/17/08
C3,projectreport,PM,12/02/08,12/19/08
. Budget
ProjectCost&TimeEstimates
.
DesignPhase,estimatedcosts
Kickoffmeeting;requirementsandpreferences,1days
Developdesignalternatives(2)-homeandsecondarypages,3days
Presentdesignalternatives,3days
Basicdesignchosen,alterationsidentified,2days
Incorporatealternatives,developfurtherpagedesigns,5days
Postdesignupdatesforreviewandfeedback,3days
Receiveclientfeedback,2days
Incorporatefinalalterationsandpost,5days
Sign-offondesign,1days
Designphaseprojectmanagement,5days
Designphasetotal,30days
DesignPhaseCost-ReductionOption:
Ifclientscanchooseadesignandcompleteallalterationsonitin2reviewsinsteadof3,cost
ofdesignphasecanbereduced.
Buildphase,estimatedcosts
Designertime,30days
Programmertime,30days
Projectmanagement,15days
Documentation,10days
Trainingsessions,10days
QualityAssurancetesting,15days
QAfixesandlaunchpreparation,30days
Post-launchmonitoringandsupport,2days
Factorofsafety@10%,1days
Buildphasetotalhours,143days
ProjectResource
ProjectRole,%Time,DatesNeeded(Range),NameofManager
ProjectManager,15,Week1-week15,Sweeper
Designer,15,Week2-week4,Jack
Programmer,30,Week6-week15,Lili
Tester,15,Week10-week15,Jane
QA,30,Week5-week15,Emma
documentation,5,Week1-week15,Sweeper
Systemssupport,5,Week10-week15,Sweeper
. EvolutionofthePlan
ThestructureofthisProjectPlanisincompliancewiththeIEEESTD1058-1998.
Afterprojectmembersreviewtheplan,thereleaseversionwillbeplacedunderconfi
gurationmanagement.
. References
[1]WebCT-COMP5231ProjectPracticeandCaseStudies,HaretonLeung
[2]DonewsBlog-DevelopingtheProjectPlan
[3]ProjectManagerUnionhttp:///p/finalfantasycms/issues/list.
,theissuewi
llbecloseout.
Thedocumentsandprogramsintheprojectprocesswillbecarriedouttheconfigurationm
anagement,,theywillbeplaced
,thechangecontrolprocesswi
llbeadopted.
. VerificationandValidation
,theteacherwillverifytheproduct–CMSofMTA.
ammersusedinthephaseofcodinginordertoqualityassurance.
. Documentation
Deliverable,Responsiblestaff
Teamformationnotice,PM
Projectplan,PM
Systemrequirementsspecification,PM
SQAplan,QA
Designdocument,Designer
Testplan,Tester
Mid-termprogressreviewandpresentation,Allmembers
Sourcecode,Programmer
Testresultsreport,Tester
Defectlog,Tester
Postprojectreport,PM
Presentationontheproject,Allmembers
Progressreport(submitbi-weekly),PM
Successfulproject,Allmembers
Checklist,Allmembers
. QualityAssurance
Wewillhavethefollowingsimplearrangeforqualityassurance.
SQAwillprovideaSQAplanandestablishanimplementprocessaccordingtotheSQApla
n.
Testerswillprovideatestplanandestablishatestprocessaccordingtothetestpla
n.
. ReviewsandAudits
,teammemberscanimp
wprocess.
First,
lbeanassistantforthemember.
Then,thedeliverablewillbepeerreviewedbyteammembers.
Next,teamleader(PM)willholdameetingtodiscusstheissuesandsharetheexperien
ce.
Finally,delivertothecustomer(teacher).
. ProblemResolution
Whenthereareissuesintheproject,teamwilladoptthenetworkdiscussionthroughthei
nternet,suchasQQ,MSN,BBS,,thisissuewil
record.
. SubcontractorManagement
Ourprojecthasnosubcontractor.
. ProcessImprovement
Whensomeproblemshappenintheprocessofprojectdevelopment,wemustlookupthereaso
.
Wewillimprovedevelopmentprocessintheprojectaccordingtothedescriptionsasabov
e.
2. AdditionalPlans
Whenthecustomerhasanyrequirementforourproduct,
theteamdiscussedandconfirmed,therequirementwillbechangedinthephaseofdesigna
.
Whenthephaseofcodeiscompleted,theprogramwillbeconfiguredonthecomputersoftea
mmembers.
Theteammustensurethesynchronousandquickdataupdating.
PMandtesterswillprovideservicesupportfortheproduct.
PM,designersandprogrammerswillberesponsibilityforproductmaintenance.
AnnexA-Bi-weeklyprogressreport
ProjectName:,
ProjectPhase:,
ReportingPeriod:,
ReportingTeam:,
ReportingDate:,
Specificaims
Pastactivities:
Currentactivities:
Currentproblems:
Futureactivities:
AnnexB-ProjectRiskChecklist
Stakeholders
*Haveyouidentifiedallstakeholders?
*Haveyouidentifiedfromallgroupstheleaderorspokesman?
*Haveyouevermetthestakeholders?
*Doyouhaveinformationonthebackgroundofthestakeholders(history)?
Stakes–Fears
*Doyouknowwhatthefearsaregenerallyforthetypeofstakeholdersyouhave(
rs)?
*Doyouknowwhatthefearsareofthestakeholderspergroup?
*Doyouknowwhatthefearsareforeachindividual?
*Doyouknowhowthisprojectaffectsthefearsofthestakeholders?
Wishes
*Doyouknowwhatthewishesaregenerallyforthetypeofstakeholdersyouhave(
ers)?
*Doyouknowwhatthewishesareofthestakeholderspergroup?
*Doyouknowwhatthewishesareforeachindividual?
*Doyouknowhowthisprojectaffectsthewishesofthestakeholders?
RequirementsProduct
*Arethecauseandgoaloftheprojectcleartoyou?
*Istheprojectscopeidentifiedanddoesitincludewhatyoucanchange,whatyoumustchange,
andwhatyoucan'tchange?
Process
*Aretheconstraintsidentified(money,time,people)?
*Doyouhaveanyideahowmuchroomthereistonegotiatetheseconstraints?
*Iftherearealreadyestimations,doyouknowhowmuchyoucantrustthem?
*Istheprojectstrategyclearandeasy?
*Istheprojectorganizationidentified?Doeseverymemberhaveaddedvaluetotheproject?
Projectmanagement
*Areyouabletonegotiate?
*Areyouabletothinkinwin-winsituations?
*Areyouriskaverse?
*Doyouincludeyourownstakesintotheprocess?
*Areyouabletogivetheprojectbackincaseitsmellslikeatrap?
Feedback
*Iseveryoneawarefortheneedanduseofgivingfeedback?
*Haveyouanyideahowtoprovidefeedback?
*Notreallyunderstandthetechniquesyouwanttouse.
*Didyouschedule(time,money,people)activitiestoprovidethefeedback?