《5934418733IBM全套项目管理文档模板.doc》由会员分享，可在线阅读，更多相关《5934418733IBM全套项目管理文档模板.doc（210页珍藏版）》请在三一办公上搜索。
1、Action log templatePROJECT / SUB-PROJECTPROJECT / SUB-PROJECT MANAGERPROJECT PHASEPROJECT ORGANIZATIONAL UNITIDShort descriptionPOwnerDate assignedTarget dateDate launchedDateperformed/ completedStAssociated action IDsID: Action identifierP: Priority - High/Medium/LowSt : Status - Open/Assigned/Clos
2、edAssociated actions IDS - Record the identifiers of any actions associated with this action, e.g. an effectiveness review actionAsset inventory templatePROJECT / SUB-PROJECTPROJECT / SUB-PROJECT MANAGERPROJECT PHASEPROJECT ORGANIZATIONAL UNITAssetOwnerAllocationNameStartEndRetdd/mmm/yydd/mmm/yyRet
3、- Returned indicator - * = returnedAsset inventory reviewDate of last reviewCommentsChange log templatePROJECT / SUB-PROJECTPROJECT / SUB-PROJECT MANAGERPROJECT PHASEPROJECT ORGANIZATIONAL UNITIDShort descriptionRaised by /Stakeholder Change IDPDate raisedOwnerTarget dateStStatus dateID: Change iden
4、tifierP: Priority - High/Medium/LowSt: Status - Open/Approved for Analysis/Approved for implementation/Implemented/Rejected/Deferred/ClosedChange request templatePROJECT / SUB-PROJECTPROJECT / SUB-PROJECT MANAGERPROJECT PHASEPROJECT ORGANIZATIONAL UNITChange request identificationChange IDShort desc
5、riptionPriority Date raisedStatusRaised by /Stakeholder change IDChange request assessmentDetailed descriptionTimescale for analysisSmall changeYes / NoAccepted for analysis byAccepted for analysis onAssigned toAssigned dateChange request analysisImpact analysisSolutions consideredEffort estimateCos
6、t estimatePotential start date forimplementationPotential target dateImpact levelResourcesEstimates validated onEstimates validated byAnalyzed byChange request implementationImplementation decision Approved/Rejected/DeferredDecision dateBy whomApproved effortApproved costApproved start date for impl
7、ementationTarget date for implementationApproved onApproved byImpact on plans and/or agreementsIncorporated into plans onIncorporated into plans byPlans changedIncorporated into agreements onIncorporated into agreements byAgreements amendedCompletion criteriaChange order ID(s)Date closedDate complet
8、edCommentsPriority: Critical/High/Medium/LowStatus: Open / Approved for Analysis / Approved for implementation/ Rejected / Deferred/ ClosedCompliance incident document templatePROJECT / SUB-PROJECTPROJECT / SUB-PROJECT MANAGERPROJECT PHASEPROJECT ORGANIZATIONAL UNITIDShort descriptionSeverityHigh/Me
9、dium/LowIncident dateStatusNot notified/Accepted/Rejected/ClosedCompliance Incident descriptionSponsor or Supplier involvedType (1)OwnerCompliance Incident consequencesNumber of People involved DurationImpactNumber of People involved x durationIncident damage Compliance Incident resolutionNo.OwnerTa
10、rget dateCommentsResolution damageClaimed damage (2)Accepted damageAccepted byAccepted onCompliance Incident historyDateComments(1) Type: Delay in Delivery/Delay in Validation/Missing a Meeting/project technical Environment Failure/.(2) Claimed damage = Incident damage + Resolution damagesCompliance
11、 incident log templatePROJECT / SUB-PROJECTPROJECT / SUB-PROJECT MANAGERPROJECT PHASEPROJECT ORGANIZATIONAL UNITIDShort descriptionSIncident dateSponsor orSupplier involvedTPeopleinvolvedDurationClaimeddamageAccepted damageStStatusdateAssociated events IDsID: Compliance incident identifierT: Type -
12、Delay in Delivery/Delay in Validation/Missing a Meeting/project technical Environment Failure/.S: Severity - Critical/High/Medium/LowDuration - length of incident in days / hoursClaimed/Accepted damage - monetary cost of the incident (incident + resolution)St: Status - Not notified/Accepted/Rejected
13、/ClosedAssociated event IDs - Record the identifiers of any event associated with this compliance, e.g. a Change request or an IssueCommunications management plan templateforPROJECT / SUB-PROJECTPROJECT / SUB-PROJECT MANAGERVersion numberN.NDraft/Final as ofdd/mmm/yyPrinted ondd/mmm/yyAuthorAuthors
14、nameAuthors address Authors e-mailAuthors telephone numberOwnerOwners nameDocument informationDocument sourceThis document is maintained as an online document. Contact the author for the latest version.Revision historyVersion numberDateSummary of changesRevision marksn.ndd/mmm/yyFirst versionNoAppro
15、valsThis document has been approved by the following people. The signed approval forms are filed in the Project Control Book.NameFunctionDate of approvalSignatureDistributionThis document has been distributed to:NameFunction1 PrefaceThe Communications management plan defines the regular meetings and
16、 reporting, and the other communications activities that take place during the project. Its purpose is to help ensure that all the project stakeholders and team members receive all the information they need in a timely manner.2 OverviewSummarize the principles and key aspects of the plan under the f
17、ollowing subheadings.2.1 Communications with the sponsor2.2 Communications with functional management2.3 Communications with subcontractors2.4 Communications within the team3 MediaDescribe any important aspects of the communications media and technology that is used.4 Scheduled meetingsComplete one
18、block of the following table for each type of regular meeting, e.g. Sub-project, Subcontractor, Project, Change board, Project steering committee, Executive steering committee.MEETINGProvide a short, meaningful title for the meeting.PurposeBriefly define the objectives of the meeting LocationSpecify
19、 where the meeting is heldFrequencySpecify how often the meeting is held, the day and start time, and the planned duration.ChairpersonName the person who runs the meeting.Minutes byName the person who takes the minutes.AttendeesName all the other regular attendees.AgendaList the standard agenda item
20、s Distribution listName anyone other than the attendees who receives a copy of the minutesMediaSpecify how the minutes are produced and distributed5 ReportingComplete one block of the following table for each type of regular report, e.g. Individual, Sub-project/team, Subcontractor and Project status
21、 reports.REPORTName the reportPurposeBriefly define the objectives of the reportFrequencySpecify how often and when the report is producedAuthorName the person who writes the reportDistributed toName the people to whom the report is distributedMediaSpecify how the report is produced and distributedR
22、eference toIndicate if any specific procedure has been defined for reporting6 Other communicationsComplete one block of the following table for each type of other regular communication Name of the communicationShort name of the other type of communicationDescriptionDescribe other planned communicati
23、ons such as news bulletins, senior presentations or periodic information flow meetings.AudienceThe audience for whom the information is intended, such as the project team, IBM management, etc.FrequencyTiming of information delivery.MediaDescription of media to be used, such as face-to-face meeting,
24、conference call, e-mail, team room, or written report.7 ScheduleAttach a Gantt chart, prepared with a suitable project planning tools, showing the activities and timescales to implement the plan.8 Assumptions, dependencies and risks8.1 AssumptionsList any important assumptions upon which the plan is
25、 based.8.2 DependenciesList any important factors upon which the plan depends.8.3 RisksList any important risks inherent in the plan.9 CostsItemize any costs, not accounted for in any other plan, that must be incurred to implement the communications management plan.Contact list templatePROJECT / SUB
26、-PROJECTPROJECT / SUB-PROJECT MANAGERPROJECT PHASEPROJECT ORGANIZATIONAL UNITNameLocationTelephoneE-mailSiteOfficeOfficeMobileHomeInternalInternetCorrespondence log templatePROJECT / SUB-PROJECTPROJECT / SUB-PROJECT MANAGERPROJECT PHASEPROJECT ORGANIZATIONAL UNITIDCorresp. name Correspondence descri
27、ptionCategoryStakeholder IDReceived fromSent toDate ofcorresp.Date loggedArchival locationID: Correspondence identifier or Transmission IDCategory - Notification, Approval, Information, Controversial, OthersDeliverable definition templatePROJECT / SUB-PROJECTPROJECT / SUB-PROJECT MANAGERPROJECT PHAS
28、EPROJECT ORGANIZATIONAL UNIT Deliverable IDDeliverable name Deliverable descriptionDeliverable contentsDeliverable properties (1)Ownership properties (2)Unique features (3)Reference to agreementAcceptance criteria / Level of service measuresDelivery planDeliverable version or components description
29、(4)Target delivery dateRelease authorityRelated milestonesReceipt authorityDateDeliverable history ReferenceDocumentsDocument the different status, indicate all the reviews, the Delivery ID(s), acting as evidences.Deliverable revisionRevisionComments(1) Deliverables properties: Specify the scope (In
30、clusions or Exclusions), the number of items, the volume, the languages used, the physical medium, the delivery conditions.(2) Ownership properties : Specify the copyright implication, the license restrictions, the application of royalties.(3) Unique features : Briefly describe what makes that deliv
31、erable unique.(4) Deliverable version or components description : Describe the content of the delivery, partial delivery, and/or version. At the component or version level, identify such properties as the scope, structure, physical properties (number of items, physical medium), and ownership (copyri
32、ght, license restrictions).Event log templatePROJECT / SUB-PROJECTPROJECT / SUB-PROJECT MANAGERPROJECT PHASEPROJECT ORGANIZATIONAL UNITIDDate and TimeDetailsTypeRefRelated documentsDetails - Briefly, but clearly, describe the eventType - Type of event - For example: incident, phone call, decision, p
33、erformance improvement directive, organizational changeRef - Event reference - ID(s) of related events in Event logExpenditure log templatePROJECT / SUB-PROJECTPROJECT / SUB-PROJECT MANAGERPROJECT PHASEPROJECT ORGANIZATIONAL UNITDateExpenditure typeAmountOriginatorReferencedd mmm yyMmm = month with
34、3 alphabetic charactersFinancial plan templateforPROJECT / SUB-PROJECTPROJECT / SUB-PROJECT MANAGERVersion numberN.NDraft/Final as ofdd/mmm/yyPrinted ondd/mmm/yyAuthorAuthors nameAuthors addressAuthors e-mailAuthors telephone numberOwnerOwners nameDocument informationDocument sourceThis document is
35、maintained as an online document. Contact the author for the latest version.Revision historyVersion numberDateSummary of changesRevision marksn.ndd mmm yyFirst versionNoApprovalsThis document has been approved by the following people. The signed approval forms are filed in the Project Control Book.NameFunctionDate of approvalSignatureDistributionThis document has been distributed to:NameFunction1 PrefaceThe Financial plan is a set of one or more tables that show the different types of cost and revenues that are pla
