IBM全套项目管理文档模板.doc

ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 1 of 211 action log template project / sub-projectproject / sub-project manager project phaseproject organizational unit idshort descriptionp ownerdate assigned target date date launched date performed/ completed stassociated action ids ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 2 of 211 id: action identifier p: priority - high/medium/low st : status - open/assigned/closed associated actions ids - record the identifiers of any actions associated with this action, e.g. an effectiveness review action ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 3 of 211 asset inventory template project / sub-project project / sub-project manager project phase project organizational unit assetownerallocation namestartendret dd/mmm/yy dd/mmm/yy ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 4 of 211 ret - returned indicator - * = returned ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 5 of 211 asset inventory review date of last reviewcomments ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 6 of 211 change log template project / sub-projectproject / sub-project manager project phaseproject organizational unit idshort descriptionraised by / stakeholder change id p date raised ownertarget date st status date ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 7 of 211 id: change identifier p: priority - high/medium/low st: status - open/approved for analysis/approved for implementation/implemented/rejected/deferred/closed ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 8 of 211 change request template project / sub-project project / sub-project manager project phase project organizational unit change request identification change idshort description priority date raisedstatus raised by / stakeholder change id change request assessment detailed description timescale for analysissmall changeyes / no accepted for analysis byaccepted for analysis on assigned toassigned date ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 9 of 211 change request analysis impact analysis solutions considered effort estimatecost estimate potential start date for implementation potential target date impact levelresources estimates validated onestimates validated by analyzed by ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 10 of 211 change request implementation implementation decision approved/rejected/deferred decision dateby whom approved effortapproved cost approved start date for implementation target date for implementation approved onapproved by impact on plans and/or agreements incorporated into plans on incorporated into plans by plans changed incorporated into agreements on incorporated into agreements by agreements amended completion criteria change order id(s) ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 11 of 211 date closeddate completed comments priority: critical/high/medium/low status: open / approved for analysis / approved for implementation/ rejected / deferred/ closed ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 12 of 211 compliance incident document template project / sub-project project / sub-project manager project phase project organizational unit idshort description severityhigh/medium/ low incident datestatusnot notified/accepted/ rejected/closed compliance incident description sponsor or supplier involved type (1) ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 13 of 211 owner compliance incident consequences number of people involved durationimpactnumber of people involved x duration incident damage compliance incident resolution no.ownertarget date commentsresolution damage ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 14 of 211 claimed damage (2)accepted damage accepted byaccepted on compliance incident history datecomments (1) type: delay in delivery/delay in validation/missing a meeting/project technical environment failure/. (2) claimed damage = incident damage + resolution damages ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 15 of 211 compliance incident log template project / sub-projectproject / sub-project manager project phaseproject organizational unit idshort descriptionsincident date sponsor or supplier involved tpeople involved durationclaimed damage accepted damage ststatus date associated events ids ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 16 of 211 id: compliance incident identifier t: type - delay in delivery/delay in validation/missing a meeting/project technical environment failure/. s: severity - critical/high/medium/low duration - length of incident in days / hours claimed/accepted damage - monetary cost of the incident (incident + resolution) st: status - not notified/accepted/rejected/closed associated event ids - record the identifiers of any event associated with this compliance, e.g. a change request or an issue ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 17 of 211 communications management plan template for project / sub-project project / sub-project manager version numbern.n draft/final as ofdd/mmm/yy printed ondd/mmm/yy authorauthors name authors address authors e-mail authors telephone number ownerowners name ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 18 of 211 document information document source this document is maintained as an online document. contact the author for the latest version. revision history version number datesummary of changesrevision marks n.ndd/mmm/yy first versionno approvals this document has been approved by the following people. the signed approval forms are filed in the project control book. namefunctiondate of approval signature distribution this document has been distributed to: namefunction ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 19 of 211 1preface the communications management plan defines the regular meetings and 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. 2overview summarize the principles and key aspects of the plan under the following subheadings. 2.1communications with the sponsor 2.2communications with functional management 2.3communications with subcontractors 2.4communications within the team 3media describe any important aspects of the communications media and technology that is used. 4scheduled meetings complete one 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. ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 20 of 211 meetingprovide a short, meaningful title for the meeting. purposebriefly define the objectives of the meeting locationspecify where the meeting is held frequencyspecify 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 items distribution listname anyone other than the attendees who receives a copy of the minutes mediaspecify how the minutes are produced and distributed 5reporting complete one block of the following table for each type of regular report, e.g. individual, sub-project/team, subcontractor and project status reports. reportname the report purposebriefly define the objectives of the report frequencyspecify how often and when the report is produced authorname the person who writes the report distributed toname the people to whom the report is distributed mediaspecify how the report is produced and distributed reference toindicate if any specific procedure has been defined for reporting 6other communications ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 21 of 211 complete one block of the following table for each type of other regular communication name of the communication short name of the other type of communication descriptiondescribe other planned communications 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, conference call, e-mail, team room, or written report. 7schedule attach a gantt chart, prepared with a suitable project planning tools, showing the activities and timescales to implement the plan. 8assumptions, dependencies and risks 8.1assumptions list any important assumptions upon which the plan is based. 8.2dependencies list any important factors upon which the plan depends. 8.3risks list any important risks inherent in the plan. ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 22 of 211 9costs itemize any costs, not accounted for in any other plan, that must be incurred to implement the communications management plan. ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 23 of 211 contact list template project / sub-projectproject / sub-project manager project phaseproject organizational unit namelocationtelephonee-mail siteofficeofficemobilehomeinternalinternet ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 24 of 211 ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 25 of 211 correspondence log template project / sub-projectproject / sub-project manager project phaseproject organizational unit idcorresp. name correspondence descriptioncategorystakeholder id received from sent todate of corresp. date logged archival location ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 26 of 211 id: correspondence identifier or transmission id category - notification, approval, information, controversial, others ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 27 of 211 deliverable definition template project / sub-project project / sub-project manager project phase project organizational unit deliverable iddeliverable name deliverable description deliverable contents deliverable properties (1) ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 28 of 211 ownership properties (2) unique features (3) reference to agreement acceptance criteria / level of service measures ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 29 of 211 delivery plan deliverable version or components description (4) target delivery daterelease authority related milestonesreceipt authority datedeliverable history reference documents document the different status, indicate all the reviews, the delivery id(s), acting as evidences. deliverable revision ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 30 of 211 revisioncomments (1) deliverables properties: specify the scope (inclusions 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 deliverable 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 (copyright, license restrictions). ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 31 of 211 event log template project / sub-projectproject / sub-project manager project phaseproject organizational unit iddate and timedetailstyperefrelated documents ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 32 of 211 details - briefly, but clearly, describe the event type - type of event - for example: incident, phone call, decision, performance improvement directive, organizational change ref - event reference - id(s) of related events in event log ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 33 of 211 expenditure log template project / sub-project project / sub-project manager project phase project organizational unit dateexpenditure typeamountoriginatorreference dd mmm yy ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 34 of 211 mmm = month with 3 alphabetic characters ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 35 of 211 financial plan template for project / sub-project project / sub-project manager version numbern.n draft/final as ofdd/mmm/yy printed ondd/mmm/yy ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 36 of 211 authorauthors name authors address authors e-mail authors telephone number ownerowners name ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 37 of 211 document information document source this document is maintained as an online document. contact the author for the latest version. revision history version number datesummary of changesrevision marks n.ndd mmm yy first versionno approvals this document has been approved by the following people. the signed approval forms are filed in the project control book. namefunctiondate of approval signature distribution this document has been distributed to: namefunction ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 38 of 211 1preface the financial plan is a set of one or more tables that show the different types of cost and revenues that are planned over a period of time. these tables are structured at the lowest level necessary to provide for accurate estimates and to provide for appropriate cost budgeting. the examples provided in this template are at the phase and project level. the following financial plan contains: the estimates upon which the pricing and budget have been determined. the budget that has been approved by on . the estimates and budget are presented at the phase level (for each phase) and then consolidated at the project level. the phase level is the lowest level of detail that is required for the financial measurement baseline (fmb) for this project. ibm worldwide project management methodwt520/3action log copyright ibm corp. 1999, 2002. all rights reserved. project namepage 39 of 211 2estimates itemize the expenses for the project at each project phase level, then summarize the expenses at the project level. 2.1itemized estimates by project phase and by expenditure type provide itemized estimates for each phase of the project. for example, types of expenditure might be: permanent staff, capital, depreciation, travel, supplier expe