1 / 29

Integration

Project Charter = Project Brief. Integration. IT Project Management. Content. Project Brief Test. Initiating Develop Project Brief/Charter Identify Stakeholders Planning Develop Project Management Plan* Executing Monitoring/Controlling Closing. From Communications KA. PMP Assignment.

cargan
Download Presentation

Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Charter = Project Brief Integration IT Project Management

  2. Content Project Brief Test • Initiating • Develop Project Brief/Charter • Identify Stakeholders • Planning • Develop Project Management Plan* • Executing • Monitoring/Controlling • Closing From Communications KA PMP Assignment

  3. Learning Outcomes • Describe the purpose of a Project Brief/Charter • Explain the parts of a Project Brief • Describe who stakeholders are • Develop and use a stakeholder grid • Describe the purpose of a Project Management Plan • Explain the parts of a Project Management Plan • Describe the difference between a Project Brief and a Project Management Plan

  4. Project Brief/Charter (In theory) Where a project begins

  5. Project Brief/Charter • PMBOK Guide Definition: • A document issued by the project initiator or sponsor that formally authorises the existence of a project, and provides the project manager with the authority to apply organisational resources to project activities • Wikipedia: • A statement of the scope, objectives and participants in a project. It provides a preliminary delineation of roles and responsibilities, outlines the project objectives, identifies the main stakeholders, and defines the authority of the project manager.

  6. Project Brief/Charter • Rita Mulcahy PMP • Project Charters • http://www.youtube.com/watch?v=y4x6uQzP2o0 • http://www.youtube.com/watch?v=GypDcmASXTY • You Tube channel • http://www.youtube.com/user/rmcpro99 • Tim Carpenter • http://www.youtube.com/watch?v=DSn7bzCuCq4

  7. Project Brief/Charter Inputs • Project initiator/sponsor • Contracts • Statement of Work • Business Case • Enterprise/Organisation • Organisational Processes • Enterprise Environmental Factors Project Brief/Charter

  8. Project Brief/Charter HR • Predefined resources (HR)+ • Procurement contracts • Sections: • Project Name • Project Manager • Project Sponsor • Project Purpose • Background • Problem/Need • Scope (Project Description) • Objectives • Deliverables • Success criteria • Exclusions (What the project will not cover) • Restrictions • High level Milestone Schedule • High level Budget • Stakeholders • Assumptions Scope Procurement Quality/Risk Time Cost Communications

  9. Scope Time Cost Quality HR Communications Risk Procurement

  10. Project Brief/Charter • Project Name: ShareMyBrain • Project Manger: <your name> • Project Sponsor: Aaron Steele • Project Purpose • Background: • Numerous tertiary institutes around New Zealand offer 1st year programming courses. Each institute utilises various tools and techniques for teaching 1st year programming. At a recent conference Lecturers involved in these courses agreed that being able to easily share these tools and techniques would be beneficial for both educators and students alike.

  11. Project Brief/Charter • Problem/Need: • There is currently no system in place that allows the lectures of these courses to share the tools and techniques they have developed or use. • Scope (Project Description) • Objectives • Project ShareMyBrain has a number of key objectives, they include: • To identify the most suitable system for sharing programming teaching resources • To implement a system that allows for the sharing of programming teaching resources • To provide self training resources for the system to be used by 1st year programming lecturers • To unify the community of 1st year programming lecturers

  12. Project Brief/Charter • Deliverables • Project ShareMyBrain will produce the following deliverables: • An educational resource sharing system for 1st year programming lecturers • User documentation • Instructional Videos • Success Criteria: • The project will be deemed a success if: • A suitable system is identified and implemented that allows 1st year programming lecturers to easily share teaching resources. • 1st year programming lecturers are supportive and use the system and the associated documentation and videos.

  13. Project Brief/Charter Objectives/Deliverables that you won’t do in this project • Exclusions: • The project will not include: • Online resource editing capabilities • Resource version control functionality • Restrictions • The selected system must be free to implement and use (excluding web hosting costs) • The selected system must include the source code • High level Milestone Schedule • August 15th – Project Starts • September 1st – System Identified • November 1st – System Implemented • November 14th – User documentation distributed to users • November 15th – Project Completed Boundaries you have to work within

  14. Project Brief/Charter • High level Budget • There is a zero dollar budget associated with this project • Stakeholders* • <your name> • Aaron Steele (Sponsor) • Programming Lecturers • Tertiary Institutes • Tertiary Students • Assumptions • It is assumed an existing, free, open source system will be utilised

  15. Project Brief/Charter • Previous five slides provide a very basic example of a Project Brief/Charter • Assignment 1 will require you to be familiar with all possible project brief sections • This will be explained in greater detail next week

  16. Stakeholder Identification • Stakeholder (PMBOK Definition) • Person or organisation that is actively involved in the project, or whose interests may be positively or negatively affected by the execution or completion of the project. A stakeholder may also exert influence over the project and its deliverables

  17. Stakeholder Grids • Grids • Power/Interest, grouping stakeholders based on their level of authority (“power”) and their level of concern (“interest”) regarding the project outcomes. • Power/Influence, grouping stakeholders based on their level of authority (“power”) and their active involvement (“influence”) in the project. • Influence/Impact.. • Power/Impact… • (Can even make your own)

  18. Stakeholder Grids • Power/Interest Grid Sponsor Project Team Programming Lecturers Tertiary Institutes Students High 1 Keep Satisfied Manage Closely 2 POWER 3 Monitor (Minimum Effort) Keep Informed 4 5 Low Low High INTEREST

  19. Stakeholder Register • The main output from the Identify Stakeholders process is the stakeholder register. • Identification info: Name, organisational position, location, role in project, contact info… • Assessment info: Major requirements, main expectations, potential influence in the project, phase with the most interest… • Classification: internal/external, supporter/neutral/resistor, etc…

  20. Stakeholder Register • Stakeholder Register

  21. Initiating Process • Once the Project Brief/Charter has been completed and the Stakeholders have been identified the initiating process is complete • The next step is to move into the planning process and develop a Project Management Plan

  22. Project Management Plan

  23. Project Management Plan • PMBOK Definition: • A formal, approved document that defines how the project is executed, monitored and controlled. It may be summary or detailed and may be composed of one or more subsidiary management plans and other planning documents.

  24. Project Management Plan • UCOL Note: • The Project Management Plan is part of your final industry project. It is created by you, and needs to be agreed to, and signed off by your academic supervisor and your sponsor (client). • The Project Management Plan is a document that details how you are going to manage the project

  25. Project Mgmt Plan Inputs Plan Quality Develop Schedule Develop HR Plan Determine Budget Plan Communications Define Scope Plan Risk Management Enterprise/ Organisation Plan Procurements Project Management Plan

  26. Project Management Plan • Introduction • Scope baseline (definition, WBS) • Schedule baseline(Milestones) • Cost baseline • Scope MP • Schedule MP • Cost MP • Quality MP • HR MP • Communication MP • Risk MP • Procurement MP

  27. Project Management Plan • <Section> Management Plan • Defines how that specific aspect of the project will be managed, e.g. • How changes to Scope, Schedule or Cost will be managed • Explain how Quality will be ensured, Risk managed, Communication achieved, etc. • How Scope, Schedule, Cost etc. will be monitored • UCOL example (more detail given in subsequent weeks) • Any changes to the project scope must be signed off by the project manager, sponsor and academic supervisor • Any minor changes to the schedule (less than 1 week) must be agreed to by the project manager and sponsor • Etc…

  28. Review • Can you: • Describe the purpose of a Project Brief/Charter? • Explain the parts of a Project Brief/Charter? • Describe who stakeholders are? • Develop and use a stakeholder grid? • Describe the purpose of a Project Management Plan? • Explain the parts of a Project Management Plan? • Describe the difference between a Project Brief/Charter and a Project Management Plan?

More Related