Example project management plan - Title Page

《Example project management plan - Title Page》由会员分享，可在线阅读，更多相关《Example project management plan - Title Page（45页珍藏版）》请在装配图网上搜索。

1、Software Project Management Plan(SPMP)forROCITRegistration On-line for Canadian ITProfessionals for the InstitutePrepared by Nerds-R-USThis page intentionally left blank. Registration On-line for Canadian ITProfessionals for the InstituteROCKITSignature PagePositionNameSignature DateDirector, The In

2、stitute for Government Informantion ProfessionalsFram EngineerROCIT Project ManagerMartin MaloRegistration On-line for Canadian IT Professionals for the Institute ROCITFinal Assignment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 1 of 45T10EProject Management for IT ProjectsSpr

3、ing 2001Change History99-VI-27 Initial Creation99-VI-28 First Revision99-VI-30 Second RevisionRegistration On-line for Canadian IT Professionals for the Institute ROCITFinal Assignment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 2 of 45T10EProject Management for IT ProjectsSpr

4、ing 2001PrefaceScopeThis is the Software Project Management Plan (SPMP) for the Registration On-line for Canadian IT Professionals for the Institute (ROCIT).FormatThis Plan is content compliant with the IEEE standard for Software Project Management Plans.AudienceThe target audience for this document

5、 includes; project team members, project sponsors, project oversight staff and project stakeholders. Registration On-line for Canadian IT Professionals for the Institute ROCITFinal Assignment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 3 of 45T10EProject Management for IT Proj

6、ectsSpring 2001This page intentionally left blank.Registration On-line for Canadian IT Professionals for the Institute ROCITFinal Assignment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 4 of 45T10EProject Management for IT ProjectsSpring 2001Table of ContentsPREFACE .2SCOPE.2FO

7、RMAT.2AUDIENCE.21OVERVIEW.81.1PROJECT SUMMARY.81.1.1Purpose, scope and objectives.81.1.2Assumptions and Constraints .81.1.3Project Deliverables.91.2EVOLUTION OF THE PLAN.91.3PROJECT CHARTER.91.3.1Responsibility.101.3.2Authority.102REFERENCES.103DEFINITIONS.114PROJECT ORGANISATION.114.1EXTERNAL INTER

8、FACES.114.2INTERNAL STRUCTURE.114.3ROLES AND RESPONSIBILITIES.124.3.1Project Team: Roles and Responsibilities.124.3.1.1Project Steering Committee:.124.3.1.2System Manager:.124.3.1.3Project Manager:.124.3.2Development Team: Roles and Responsibilities.134.3.2.1Architecture Group:.134.3.2.2Database Adm

9、inistration Group:.134.3.2.3Computer Operations Group: .134.3.2.4Management Support Services:.144.3.2.5Administrative Support Group:.144.3.2.6Control and Organisation Support Group:.144.3.2.7Development Group: .144.3.3Roles and Responsibilities by Type of Human Resource.154.3.3.1Functional Analyst:.

10、154.3.3.2Systems Analyst: .154.3.3.3Programmer:.164.3.3.4Procedures and Methods Analyst:.164.3.3.5User:.165MANAGERIAL PROCESS PLANS.165.1START-UP PLAN.165.1.1Estimation Plan .165.1.2Staffing Plan .165.1.3Resource Allocation Plan.17Registration On-line for Canadian IT Professionals for the Institute

11、ROCITFinal Assignment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 5 of 45T10EProject Management for IT ProjectsSpring 20015.1.4Project Staff Training Plan.175.2WORK PLAN.175.2.1Work Activities.18ROCIT WBS LIFE CYCLE SECTION.185.2.2Schedule Allocation.195.2.3Resource Allocation

12、.215.2.4Budget Allocation .225.3CONTROL PLAN.225.3.1Requirements Control Plan .225.3.1.1Overview .225.3.1.2Objectives.225.3.1.3Roles and Responsibilities.225.3.1.4Processes and Procedures.235.3.1.5Requirements Management Tools.245.3.2Schedule Control Plan.245.3.3Budget Control Plan.245.3.4Quality Co

13、ntrol Plan .245.3.5Reporting Plan.255.3.6Metrics Collection Plan.265.4RISK MANAGEMENT PLAN.265.4.1Risk Identification.265.4.2Risk Analysis.265.4.3Risk Planning.265.4.4Risk Tracking.275.4.5Risk Control.275.5PROJECT CLOSEOUT PLAN.276TECHNICAL PROCESS PLANS.286.1PROCESS MODEL.286.2METHODS, TOOLS AND TE

14、CHNIQUES.286.2.1Development Environment.286.2.2Target Environment.286.2.3Development and Documentation Standards .286.2.4Testing Standards .286.2.5Team Structure.296.2.6Programming languages .296.3INFRASTRUCTURE PLAN.296.4PRODUCT ACCEPTANCE PLAN.297SUPPORTING PROCESS PLANS.307.1CONFIGURATION MANAGEM

15、ENT PLAN.307.1.1Overview.307.1.2Objectives .307.1.3Scope.307.1.3.1Controlled Items.307.1.3.2CM Activities .30Registration On-line for Canadian IT Professionals for the Institute ROCITFinal Assignment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 6 of 45T10EProject Management for

16、 IT ProjectsSpring 20017.1.4Roles and Responsibilities.317.1.4.1Configuration Manager.317.1.4.2Team members .317.1.4.3Project Document Authors .317.1.5Processes and Procedures.317.1.5.1Baselining Project Documents.317.1.5.2Baseline Repository.317.1.5.3Access to Baselined Documents.327.1.5.4ROCIT App

17、lication .327.1.5.5Verification of ROCIT Application.327.2VERIFICATION & VALIDATION PLAN.327.2.1Overview.327.2.2Objectives .327.2.3Scope.327.2.3.1Controlled Items.327.2.3.2Verification & Validation Activities .337.2.4Roles and Responsibilities.337.2.4.1Verification & Validation Manager.337.2.4.2Team

18、 Members.337.2.5Processes and Procedures.337.2.5.1Verification & Validation.337.3DOCUMENTATION PLAN.337.3.1Overview.337.3.2Objectives .347.3.3Scope.347.3.3.1Controlled Items.347.3.3.2Documentation Activities.347.3.4Roles and Responsibilities.347.3.4.1Documentation Manager .347.3.4.2Team Members.347.

19、3.5Processes and Procedures.357.4QUALITY ASSURANCE PLAN.357.4.1Overview.357.4.2Objectives .357.4.3Scope.357.4.3.1Controlled Items.357.4.3.2Quality Assurance Activities.357.4.4Roles and Responsibilities.367.4.4.1Quality Assurance Manager .367.4.4.2Team Members.367.4.5Processes and Procedures.367.5REV

20、IEWS AND AUDITS.367.5.1Overview.367.5.2Objectives .367.5.3Scope.367.5.3.1Controlled Items.367.5.3.2Reviews and Audit Activities.377.5.4Roles and Responsibilities.377.5.5Project Manager.377.5.5.1Team Members.377.5.6Processes and Procedures.37Registration On-line for Canadian IT Professionals for the

21、Institute ROCITFinal Assignment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 7 of 45T10EProject Management for IT ProjectsSpring 20017.6PROBLEMS RESOLUTION PLAN.377.6.1Overview.377.6.2Objectives .387.6.3Scope.387.6.3.1Controlled Items.387.6.3.2Defect Resolution Activities.387.6

22、.4Roles and Responsibilities.387.6.4.1Defect Resolution Manager.387.6.4.2Team Members.387.6.5Processes and Procedures.397.7SUBCONTRACTOR MANAGEMENT PLAN.397.8PROCESS IMPROVEMENT PLAN.398ADDITIONAL PLANS.39ANNEXES.40Registration On-line for Canadian IT Professionals for the Institute ROCITFinal Assig

23、nment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 8 of 45T10EProject Management for IT ProjectsSpring 20011OverviewThe University of Ottawa has long been plagued with slow and archaic registration procedures. The Department of Redundancy Department (DRD) has been asked to draw

24、 up a project plan to expedite the registration of all Institute students. Currently, the Institute does this by setting up tables on registration day. Students each fill out a form, which is then submitted, to the Institute personnel. These paper forms are then sent physically to Ottawa University

25、where the information on the form is then keyed into a legacy registration system where the individual is tracked as a regular part-time student. The proposed system that will expedite registration is web based using Visual Basic 6 controller program to interact with an Access database. Users will a

26、ccess the system via the web and within the system both Institute personnel and Professors will have Intranet accessibility.1.1Project Summary1.1.1 Purpose, scope and objectivesThe objective of the project is to streamline registration processes for students registering for Institute courses and all

27、ow ease of access to information for Institute personnel and Professors. The final product to be delivered to the client is a web-based application written in visual basic with a back end MS Access database.Ease of access to information Workflow capability between Ottawa University and The Institute

28、Interface between Ottawa University legacy system and ROCITWeb based ROCIT applicationWeb based reporting capabilityFunctional and Technical DocumentationTraining1.1.2 Assumptions and ConstraintsAssumptions and Constraints upon which the ROCIT project is based are as follows:All necessary funding wi

29、ll be made available for the entire life of the projectAll resources both internally and externally which are identified up front and through out the entire project will be dedicated 100% for the life of the project on an as and when required basis.Interfaces to other systems and/or products will be

30、 established at the beginning of the project and access to resources who are subject matter experts for those interfaces Registration On-line for Canadian IT Professionals for the Institute ROCITFinal Assignment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 9 of 45T10EProject Ma

31、nagement for IT ProjectsSpring 2001will be identified and dedicated on an as and when required basis for the life of the projectAll necessary hardware/software will be purchased through a master standing offer to expedite purchasing for the purposes of this project and implementation of this hardwar

32、e and software will be done in conjunction with technical experts for both external and internal interfaces where necessary.1.1.3 Project DeliverablesROCIT Registration SystemSource CodeSoftware/HardwareTechnical / Functional SpecificationsDocumentation:TechnicalFunctionalTrainingStatus BudgetSchedu

33、les1.2Evolution of the PlanAll scheduled and unscheduled changes to the SPMP will be tracked through DocsOpen Document organisation and control system. All changes must go through the Project Manager of ROCIT and access to create/update the SPMP will be given to a specified resource within the PM te

34、am. The resource responsible for change management will be the first person to create the document in DocsOpen. Once the SPMP is created a user profile will be set up to allow for various access profiles for all individual involved in the ROCIT project. DocsOpen will create a new version for every s

35、ave done by the CM resource starting with revision 1 and going up incrementally from that point on.Dissemination of information relative to the project and including things such as status reports, SPMP updates, etc will be distributed via e-mail once weekly and a shared directory will be made availa

36、ble for all ROCIT resources for the life of the project. There will also be weekly status meetings at various levels within the project team.1.3Project CharterDepartment of Redundancy DepartmentAny StreetOttawa, OntarioRegistration On-line for Canadian IT Professionals for the Institute ROCITFinal A

37、ssignment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 10 of 45T10EProject Management for IT ProjectsSpring 2001To:DistributionFrom:Mr. DG, Department of Redundancy DepartmentSubject:Project Charter for the ROCIT ProjectMr. Martin Malo has been assigned as the Project Manager f

38、or the ROCIT Project1.3.1 ResponsibilityMr. Malo will be responsible for ensuring that all key deliverables are met within time, cost and performance constraints of the project and that she will adhere to proper quality control mechanisms and standards. The project manager must work closely with the

39、 line managers to ensure that all assigned resources are effectively and efficiently utilised and that the project is properly resourcd with both internal and external resources.In addition, the project manager is responsible for:1. All formal communication between the functional and technical areas

40、.2. Preparation of the project plan with sign-off between the functional and technical areas.3. Preparation of all project data items4. Regular status reports and updates to executives5. Ensure that all employees and functional managers are kept informed and up-to-date as to what their responsibilit

41、ies are in relation to the project6. Budget tracking actual against estimated.7. Maintenance of the project plan that dynamically shows the projects time, cost and performance and resource commitment. 1.3.2 AuthorityTo ensure that this project meets its objectives, Mr. Malo is authorised t manage th

42、e project and issue directives in accordance with the policies and procedures of the Department of Redundancy Department. Any additional directives may be issued through the office of the DG of the Department of Redundancy Department.The project managers authority also includes:1. Direct access to t

43、he client on all matters pertaining to the ROCIT Project2. Direct access to the executive of the Department of Redundancy Department and the Institute on all matters relating to the ROCIT Project.3. Control and distribution of all funding associated with the ROCIT Project including procurement as th

44、e project authority.4. To revise the project plan as needed and with client approval5. To monitor the time, cost and performance activities and ensure that all problems are promptly identified, reported and solved.2ReferencesRegistration On-line for Canadian IT Professionals for the Institute ROCITF

45、inal Assignment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 11 of 45T10EProject Management for IT ProjectsSpring 2001A Guide to the Project Management Body of Knowledge (PMBOK Guide) 2000 edition - Project Management Institute Project Management - A Systems Approach to Plannin

46、g, Scheduling, and Controlling - Seventh Edition, Harold Kerzner, PhDDMR Productivity Plus - Information Systems Delivery Series - Project Management Guide - Third EditionProject Management for IT Projects - University of Ottawa and University of Western Ontario, Dr. J.M. Bennett 3DefinitionsThe IEE

47、E Standard Glossary (Std. 610.12-1990) is to be used for defining terms and acronyms contained herein.4Project OrganisationThis structure applies throughout development. Titles and relationships will vary with the organisation, but the roles will remain the same. In particular, leadership and accoun

48、tability must lie with the project manager, working in close collaboration with the System Manager. A successful project is always managed by an individual, not a committee.4.1External InterfacesExternal interface to Ottawa University Legacy Systems group. A representative from the University will s

49、it on the Project Steering committee and will have the authority to make decisions that impact the project from a technical and functional perspective and will have the authority assign resources from Ottawa University as and when required.Registration On-line for Canadian IT Professionals for the I

50、nstitute ROCITFinal Assignment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 12 of 45T10EProject Management for IT ProjectsSpring 20014.2Internal Structure4.3Roles and Responsibilities4.3.1 Project Team: Roles and Responsibilities4.3.1.1 Project Steering Committee: Made up of th

51、e IS manager and representatives of users affected by the project (middle management or higher)Membership is about 5 peopleApproves the preliminary analysis report, architecture report, implementation report and all other project deliverablesApproves the project plan and the release planMonitors pro

52、ject evolution through regular project reviewsApproves major changes (in content, schedules, etc.) requested by the project manager and approved by the system managerROCIT Project Team: General StructureROCIT Project Steering Committee CommitteeProject ManagerSystem ManagerDevelopment TeamSystem Man

53、agement & Implementation TeamTable 4-1 ROCIT Team StructureRegistration On-line for Canadian IT Professionals for the Institute ROCITFinal Assignment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 13 of 45T10EProject Management for IT ProjectsSpring 20014.3.1.2 System Manager: Th

54、e management level user most directly concerned with the system being developedReports to the project steering committeeHeads the system management and implementation teamChooses the user members of the system management and implementation teamAssigns the user personnel needed to support the develop

55、ment team in the preparation of functional specifications and other workReviews the preliminary analysis report, the architecture report and the implementation report.Approves the functional specifications and the definition of data elementsApproves user guidesApproves the project plan and the relea

56、se plansSettles differences that may arise between users and analysts working on the projectApproves any change of plan with regard to system contentsSets priorities for change requests affecting the schedule and may refer this to the project steering committeeCo-ordinates the activities connected w

57、ith system management and implementation i.e. training, conversion site preparation, etc.4.3.1.3 Project Manager: A very experienced systems analyst with good management skillsReports to the project steering committeeHeads the development teamBuilds the development teamCo-ordinates the development,

58、activities, and may participate in some of them i.e. preliminary analysisPrepares the project plan and release plans and submits them to the project steering committee for approvalApproves the group plansPrepares the project reviews and presents them to the project steering committeeConducts progres

59、s reviews with the group leadersConducts change management meetingsConducts meetings dealing with outstanding issuesNotifies the system manager of variances from plan and submits recommendations for corrective actionRegistration On-line for Canadian IT Professionals for the Institute ROCITFinal Assi

60、gnment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 14 of 45T10EProject Management for IT ProjectsSpring 20014.3.2 Development Team: Roles and Responsibilities4.3.2.1 Architecture Group: Responsible for developing the preliminary analysis deliverablesResponsible for developing

61、and updating all system architecture deliverablesMust define the mandate and initiate the work of each development groupProvides all support needed by the development groupResponsible for reviewing several development deliverables including:unit process functional specificationsoptimisation of facet

62、sprogramming unitsfunctional test plansHas overall responsibility for the coherence and efficiency of the deliverables produced by all development groupsThe group leader, and other group members as needed, participate in meetings dealing with change management 4.3.2.2 Database Administration Group:

63、Administrative unit responsible for corporate level database administrationAssigns database administrators to the projectResponsible for physical data modelling dictionary entries, to ensure integrity of all data4.3.2.3 Computer Operations Group: Administrative unit responsible for operating the org

64、anisations computer systemsParticipates in production architecture (final phases)Co-ordinates the use of data processing resources for production and developmentAssists the users in system testingTakes over releases at production cut-over4.3.2.4 Management Support Services: Is assisted by two suppor

65、t groups: the administrative support group and the control and organisation support groupAssists the project manager in preparing the release plansAssists the development group leaders in preparing group plansParticipates in progress review and in meetings relating to change management outstanding i

66、ssuesAssists the project manager in identifying the project teams organisational needsRegistration On-line for Canadian IT Professionals for the Institute ROCITFinal Assignment: Jacqueline Klein, Yvan Desjardins, Martin Malo, Dean PengellyPage 15 of 45T10EProject Management for IT ProjectsSpring 2001Participates as needed in implementing solutions to project team needs i.e. writing procedures, work methods, etc.4.3.2.5 Administrative Support Group: Responsible for providing the development team