1 S E C T I O N II T W O Project Management Topics
2 SECTION II: PROJECT MANAGEMENT TOPICS TABLE OF CONTENTS Introduction 3 1. PROJECT TRIAGE Gather the Data Review and Analyze the Data Prepare Findings and Develop Corrective Action Plan Present Report Revise Project Plan 16 Measurements of Success LEADERSHIP Communication Leading the Change Management Effort Managing Politics and Conflict Leading the Project Team Building Trust PROCUREMENT AND CONTRACTOR MANAGEMENT Procurement Strategies General Contractual Information Contract Terms Utilizing Existing Contracts Establishing New Contracts Contractor Management PERFORMANCE MEASURES The Balanced Scorecard Performance Measures in the Public Sector A Success Story IT PROJECT CAPABILITY (CMM) IT PROJECT TOOLS 61
3 Section II Introduction This section provides in-depth advice and direction on selected topics of importance to New York State Project Managers. It is anticipated that this section of the Guidebook will grow as the state s Project Managers identify and contribute advice on additional topics of common interest. The intent of this section is to provide a repository to share the lessons learned from the experience and expertise of the state s Project Managers. Chapter 1 covers Project Triage, designed to assist Project Managers who have a project that is going south. It outlines a specific process that can be employed to quickly identify project problems and define corrective action plans. Chapter 2 discusses Leadership, one of the most important qualities for a Project Manager to have and to continuously develop and improve. The challenges and the many facets of leadership are explored and specific suggestions are offered. Chapter 3 contains specific information regarding New York State Procurement and Contractor Management. Projects undertaken in New York State are increasingly complex, frequently involving multiple agencies and contractors supplying myriad products and services. This chapter provides references to available New York State Procurement Guidelines and existing state contracts, as well as guidance on when to use specific contracts and whom to contact for procurement advice and direction, and advice on managing contractor performance. Chapter 4 identifies Performance Measures terms and concepts to orient Project Managers to this important aspect of organizational performance. Chapter 5 describes IT Project Capability and provides an objective way to establish and predict performance of an agency s IT effort. It is designed to assist organizations improve the effectiveness of their software and business processes. Chapter 6 provides a brief description of how IT Project Tools support the system development lifecycle. The discussion is focused on the value of tools and how a Project Manager may utilize them during a SDLC project. 3
5 1 PROJECT TRIAGE Purpose Project Triage is a process used to perform a quick evaluation of a project and to prioritize actions or corrective recommendations based on current project status. Triage is performed when a Project Manager is given a project in progress or when a project is determined to be in trouble. Recognition that a project is in trouble may come from a number of different sources, including the Project Manager, the Project Sponsor, a Project Team member, an auditor, a fiscal analyst or others within the Performing Organization. The Project Manager must play a role in the triage, with support for the triage effort from the Project Sponsor. While the emphasis of the triage effort is on a quick evaluation, speed is relative to the project size/scope. A three-year project may require a triage review lasting several weeks, while a project of several months duration may only require a triage review of several hours. It is important to spend adequate time to gather the information needed to analyze the problems and define the actions necessary to get the project back on track. The triage effort may be completed by an individual, or by a team, depending upon the size of the project and the time available. An experienced Project Manager should perform a Project Triage. In some cases it may be more effective to secure a Project Manager from outside the Performing Organization, who is less likely to be influenced by organizational politics, history, or other factors. Inside knowledge can sometimes limit the effectiveness of a triage by prejudicially eliminating ideas without proper consideration. While having the triage performed by another Project Manager within the organization who has not previously been involved in the project may be more objective, it still may be difficult for anyone from within the organization to evaluate the work of a peer. In general, the less background related to the project and the Performing Organization the Project Manager has before taking on the project triage, the more likely it is that the effort will produce objective and effective results. However, the reality is that a Project Manager often triages his or her own project. 5
6 6 Section II:1 Project Triage List of Processes Project Triage consists of the following processes: Gather the Data Review and Analyze the Data Prepare Findings and Develop Corrective Action Plan Present Report Revise Project Plan List of Roles The following roles are involved in carrying out the processes of this phase. The detailed descriptions of these roles can be found in the Section I Introduction. Project Manager Project Sponsor Project Team Member Customer Decision Makers List of Deliverables Figure 6-1 lists all Project Triage processes and their deliverables. Figure 1-1 Processes Gather the Data Review and Analyze the Data Prepare Findings and Develop Corrective Action Plan Present Report Revise the Project Plan Process Deliverables Collection of existing information (project repository) Assessment of current project status (Preliminary Problem Identification List) Findings and Corrective Action Plan Management presentation Revised Project Plan, including remediation activities as required
7 Section II:1 Project Triage GATHER THE DATA The first step in Project Triage is for the Project Manager to gather all available information from the project repository. For example, start with the Project Plan or any existing pieces of the plan, and gather: a Project Schedule the work breakdown structure a task list a list of team members and role descriptions Project Status Reports a product description If any of these items is not available, its creation should become a task in the corrective action plan. The End-of-Phase Checklists can be used for a more comprehensive list of project requirements for the phase the project is in and all preceding phases. In addition to the documentation specific to this project, all existing standards, including templates and forms the organization has in place, must be collected. All written documentation should be reviewed diagrams, electronic documents, blueprints, and other media. For a troubled project, information will also need to be gathered through interviews with team members and stakeholders. The Project Manager must try to get a feel for the attitude and atmosphere surrounding the project by talking to a few key players. The best place to start is with the Project Sponsor. There isn t a Project Sponsor? Why is this project being done? To whom in the Performing Organization is it important? There may be more than one Project Sponsor, but if there are more than two, this is also a caution point. Too many sponsors may lead to conflicting directions. Next, it is important for the Project Manager to talk to the technical or subject matter experts on the Project Team. If the project is a software development effort, this will probably be an experienced computer programmer or similarly skilled individ-
8 8 Section II:1 Project Triage ual. If the project is a new building, this may be an architect or a construction engineer. The Project Manager should next meet with some or all of the Project Team members. These interviews can be conducted in a group setting, or individually, if that might be more productive. The Project Manager should try to sense the mood of the Project Team to determine the proper interview settings. A team meeting, if practical, may allow more information to be gathered faster. Individual interviews can be conducted subsequently if participants were reluctant to contribute in a group setting. ( Starter questions are provided in a sample interview agenda, see Figure 6-2. Any that are relevant to the project being assessed can be used, although additional questions may be needed to elicit the information required.) If the Project Team interviews or the team meeting did not involve Customers or Consumers of the project s product, follow-up with those individuals is also required. Don t forget that Customers or Consumers should be actively represented on the Project Team.
9 Section II:1 Project Triage 9 Sample Triage Interview Agenda Figure 1-2 Interviewee: Role: Project Team: Date & Time: 1. What do you view as the problems with this project? Response: 2. What would you do differently? Response: 3. What was/is your role is on this project? Response: 4. What is your current task? When did it begin? When will it be completed? Do you expect to meet that due date? Response: 5. Do you have a copy of the Project Scope statement? Response: 6. Do you have a copy of the Project Schedule? Do you know specifically which tasks you are assigned? Do you understand how they fit into the total project? Response: 7. Do you provide a Progress Report to your Team Leader or the Project Manager? Do you participate in a status meeting? Do you receive a Project Status Report? Response: 8. Do you have the resources required to complete your tasks? Are you assigned to this project exclusively? Do you have other assignments that are inhibiting your ability to complete the assigned tasks on this project? Has the relative priority of your assignments been clarified to you by your supervisor? Response:
10 10 Section II:1 Project Triage 1.2 REVIEW AND ANALYZE THE DATA The Project Manager should quickly determine where the project is within the phase (Project Planning, Project Execution and Control, etc.) and process level. Major problems must be identified (e.g., behind schedule by 60%, over budget by 30%, lost resources, unstable bleeding edge technology). The End-of- Phase Checklists in this Guidebook can be used for each project phase (Initiation, Planning, Execution and Control, and Closeout) to evaluate whether each project phase is complete and to identify missing elements. The lists of Pitfalls and Measurements of Success for each phase will also assist in evaluating the current state of the project. Analysis of issues begins during information gathering, when new questions may be raised. It is not necessary to wait until all information has been gathered to begin the analysis. Any assumptions developed as part of the triage effort must be documented in a Preliminary Problem Identification List and verified. Answers to the following questions will assist in determining the project s overall health: Is the available documentation an accurate reflection of what has happened? Does documentation exist or are the Cost, Scope, Schedule, and Quality moving or unidentified targets? Which deliverables have been completed? Reviewed? Approved? Which deliverables have been completed on time? Which milestones have been met? Where are the actuals in relation to the baseline? Is there a baseline? What percentage of the total project resources has been expended? What percentage of the total estimated work has been completed? What are the outstanding issues? Is there an issues log? What are the communications vehicles? (status reports, memos, etc.) What evidence exists of their use? The Project Manager must identify causes of problems, not just symptoms. Reacting to symptoms without addressing problems often gets a project into trouble. For example, if there are excessive requests for scope changes and there is a lack of
11 Section II:1 Project Triage 11 understanding of the Project Scope by the Project Team, the cause may be that the Project Scope was not well defined or that no change control process exists. It is important to recognize and acknowledge that some of the issues that could cause a project to run into trouble are external to the control of the organization. Examples of such situations include natural disasters, newly enacted legislation, acts of terrorism or war, etc. Risk plans cannot cover every possible contingency. Also, major successes should be identified (user requirements are clear, planning was complete, status reporting has been accurate, team members are all getting along, etc.). This will help to eliminate causes of problems as well as provide a foundation for the remediation portion of the mission. If at any point the Project Manager identifies an action that should be taken immediately in order to prevent further problems or to correct a problem, it should be documented and presented to the Project Sponsor for immediate implementation.
12 12 Section II:1 Project Triage 1.3 PREPARE FINDINGS AND DEVELOP CORRECTIVE ACTION PLAN The output of a triage is a description of the findings of the triage effort, including the problems identified (symptoms/indicators), the root causes of the problems, and the specific prioritized recommended corrective actions. A prioritized list of action items must be created to get the project back on track as quickly and efficiently as possible. Some actions may need to stop to allow other processes to be completed. Most importantly, the Project Manager must not allow tasks to move ahead which are pulling the project further in the wrong direction. Examples of Problem Indicators, Causes, and Actions Recommended follow. Figure 1-3 Indicator Potential Causes Actions Recommended 1. Behind schedule a. Scope creep. i. Ensure/create baseline scope statement. ii. Implement a change control system. b. Staff assigned does not have i. Assign appropriately experienced the same level of expertise staff (contract or in-house). anticipated when estimates were ii. Adjust schedule to allow for training. made. iii. Additional staff assigned. c. Using not-ready-for-primetime i. Replace with a proven product. software. ii. Adjust schedule to accommodate software maturity. d. Estimates made during Project i. Revise initial high-level estimates in Initiation have not been revised light of additional information throughout Project Planning. gained through the planning process. 2. Over budget a. Poor initial estimates. i. Re-estimate, re-baseline, and gain approval for new plan. b. Technology cost increases. i. Consider alternative implementations. ii. Justify budget increase and re-baseline. c. Project Budget charged with i. Document and report to management. unrelated expenses. Update and maintain budget documentation.
13 Section II:1 Project Triage 13 Indicator Potential Causes Actions Recommended 3. Poor staff a. Poorly defined Project i. Re-plan task breakdown, resource performance Schedule. estimates, and assignments with team involvement. b. Poor communications. i. Evaluate and revise Communications Plan. ii. Implement regularly-scheduled team meetings. c. Poor project management. i. Assess project management competencies and identify weaknesses. Provide training and mentoring to strengthen Project Manager. ii. Assign new Project Manager. iii. Hire an experienced Project Manager. d. Lack of user involvement. i. Cultivate mutually beneficial relationship e. Roles and responsibilities not i. Define and document roles and defined or communicated. responsibilities. Review with team. f. Conflicting priorities. i. Reschedule project consistent with actual priority. g. Lack of executive support. i. Seek support through Project Sponsor. ii. Seek support through Performing Organization management, if appropriate. h. Changed priorities project i. Cancel project. no longer needed. 4. Poor project a. Lots of activities, no definable i. Organize activities into tasks with progress deliverables and/or project defined responsibilities and milestones. dependencies. Define relationship of activities to deliverables, and to key project milestones. b. Unrealistic expectations. i. Manage user expectations. 5. Unexpected a. Unforeseen issues possibly i. Re-evaluate cost/benefit and determine obstacles including external factors that are if project should proceed. out of the organization s control. b. No risk plan. i. Define a risk plan. When prioritizing the recommendations, include any additional resources that will be needed, including who should be responsible for each item, by role if not by name. Provide alternatives along with the pros and cons of each, if possible. For example, hiring additional staff will add to the cost of the project but preserve the schedule as opposed to maintaining the budget by delaying the completion.
14 14 Section II:1 Project Triage Examples of Prioritized Recommendations and Resource Needs follow. Figure 1-4 Priority Action Resources Owner 1. Stop development until None Project Sponsor scope is defined. 2. Document scope. Customer Representative, Project Subject Matter Expert Sponsor, Subject Matter Expert 3. Define change control Subject Matter Experts to develop Project Manager process. a small system 4. Clarify priorities. Performing Organization managers Project Sponsor 5. Formalize schedule. Need to purchase scheduling Project Manager software 6. A narrative report should be developed to explain the process undertaken to identify the problems and causes, identify the reasons for the prioritization, and to define the actions recommended. This will facilitate execution of the corrective action plan.
15 Section II:1 Project Triage PRESENT REPORT The report should provide an honest, accurate assessment of the current state of the project, what went wrong, and how to fix it. Whenever possible, the Project Manager should prepare a presentation of the report, which includes the corrective action recommendations. There may be multiple presentations one at the management level and one for the Project Team members. The tone of the presentation should be positive, focusing on how the Project Plan can be revised. The Project Manager must ensure that management understands the exact current project status. The need for additional resources and changes to the Project Schedule should be made clear. The Project Manager must also maintain a constructive and positive tone with team members, since they are the ones who determine the success or failure of the remediation effort. Participants should be given an opportunity to respond and ask questions so that everyone understands the situation and the corrective action plan. Leadership skills play a vital role at this time. Occasionally, the corrective action recommendation will be to scrap the work that has been done and start over. This may include complete re-planning and securing a new project approval. This should be a rare occurrence, but when it happens, starting over must be justified by a savings of time or money, improvement in quality, or preservation of scope.
16 16 Section II:1 Project Triage 1.5 REVISE PROJECT PLAN The final part of the triage and remediation effort is to revise the Project Plan to include the activities resulting from the recommendations in the report. Optimally, the Project Team will implement the corrective action plan, with additional resources as required. The corrective action plan must be integrated into the Project Plan and managed as part of the ongoing project. The corrective action plan is designed specifically to get the project back on track quickly, not to address long-term organizational needs such as training, cultural changes, or methodology development. Sometimes, project problems may be corrected with no-cost activities such as team building and re-alignment of priorities. More often, the remediation effort will require additional resources, either in time or money, or a decreased product, either in scope or quality. If the decision is made to create a new baseline Project Schedule, the original schedule must be kept for historical purposes. Completing the triage and remediation effort requires ongoing diligence, continuing communications, tracking, reporting and commitment from all Project Team members. It remains the Project Manager s responsibility to coordinate all of these efforts. Often, reporting requirements are increased following triage because some managers want to be informed of more detail than would otherwise be required.
17 Section II:1 Project Triage 17 Measurements of Success Figure 1-5 Process Measurements of Success Yes No Gather the Data Review and Analyze the Data Prepare Findings and Develop Corrective Action Plan Present Report Revise the Project Plan Did team members share information freely? Do you have enough information to do an assessment? Does the data support the obvious problems with the project? If not, you may need to look further. Do stakeholders agree with, or at least understand your findings? Are the action items reasonable and do-able? Does management understand both the problems and the solutions? Have the resources required been allocated? Does the Project Team support the effort?
18 18 Section II:1 Project Triage 1. Triage Questionnaire Gather the Facts Figure 1-6 Question Response Does the Consumer Are the Consumers involved the correct project have: involvement? ones and have you established and maintained a good working relationship? Are you facilitating their involvement and are they actively contributing? Who should be promoting the project and its priority? Do you know who will use the product you are creating and what its impact will be? Executive Is there a Project Sponsor? Management Is the Project Sponsor involved and support? supportive? Does the Project Sponsor have a stake in the outcome of this project? Does the Project Sponsor have the authority needed to address conflicts between projects and commit resources? Does the project support the Performing Organization s strategic plan? a clear Is there a vision? statement of Has the Business Case been defined? requirements? Are the expectations realistic? Are functional requirements defined? Has a risk assessment been done? Are there measurements by which to determine the success or completion of the project? Have the requirements been: - Documented? - Agreed to with signatures from all appropriate parties? - Communicated to the Project Team and all other stakeholders?
19 Section II:1 Project Triage 19 Figure 1-6 (Continued) Question Response Is the Project Manager assigned to this project? Are team members assigned to this project full time? Is project communication adequate? Has planning thus far been adequate? Does the Project Manager have a clear understanding of the priority of this project? Is this consistent with the Project Sponsor s understanding and the priority stated by management? Does the Project Manager have the experience and training necessary to be successful on his or her assigned tasks? Do team members have a clear understanding of the priority of this project? Does this agree with the Project Manager s understanding and the priority stated by management? Do team members have the experience and training necessary to be successful on their assigned tasks? Is everyone aware that the project exists? Is project status clearly, frequently, and widely communicated to all concerned? Do all team members clearly understand what is expected of them? Review the lists of what should be included in the Project Plan at each phase. For example, Develop Initial Project Plan, Section I:2.4, includes a list of what pieces of information should be in the Project Plan by the end of Project Initiation: a. Project Charter b. CSSQ c. List of risks d. Description of stakeholder involvement e. Communications Plan
20 20 Section II:1 Project Triage Figure 1-6 (Continued) Question Response Where do you need to be and what is driving the Project Plan? Time: Do we need to complete the project by a certain time? If so, are additional resources (time, money, technology) available to the project? Cost: Do we need to complete the project under a specified cost? If so, can the dates be moved to allow the project to be completed by less-expensive resources (provide time for a learning curve, use in-house staff rather than consultants, etc.)? Scope: Do we need to deliver every feature defined even if means more time or more cost? Quality: Can a beta version of the product be released and then anomalies fixed and features added later on? (sometimes possible for internal users, where there are no health or safety issues, or loss of assets, etc. involved)
Introduction to the ITS Project Management Methodology In September 1999 the Joint Legislative Committee on Performance Evaluation and Expenditure Review (PEER) produced a report entitled Major Computer
OFFICE OF THE CIO PROCEDURE Informational VERSION: 1.0 Purpose Project Management of Major or Large NDUS Information Technology Projects Project Managers Guide/Checklist This procedural process will ensure
PROJECT MANAGEMENT GUIDELINE SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE Table of Contents Introduction... 3 Project Execution and Control Phase Overview... 3 Activities and Documents in the Execution
Project Management Certificate (IT Professionals) Whether your field is architecture or information technology, successful planning involves a carefully crafted set of steps to planned and measurable goals.
Step by Step Project Planning Contents Introduction The Planning Process 1 Create a Project Plan...1 Create a Resource Plan...1 Create a Financial Plan...1 Create a Quality Plan...2 Create a Risk Plan...2
PROJECT RISK MANAGEMENT DEFINITION OF A RISK OR RISK EVENT: A discrete occurrence that may affect the project for good or bad. DEFINITION OF A PROBLEM OR UNCERTAINTY: An uncommon state of nature, characterized
2.1 Initiation Phase Overview The is the conceptualization of the project. This section describes the basic processes that must be performed to get a project started. Accordingly, the purpose of the is
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME > Date of Issue: < date > Document Revision #: < version # > Project Manager: < name > Project Management Plan < Insert Project Name > Revision History Name
PROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE: Project Name Project Management Plan Document Information Document Title Version Author Owner Project Management Plan Amendment History
In this chapter Learn what comprises a successful project Understand the common characteristics of troubled projects Review the common characteristics of successful projects Learn which tools are indispensable
Process Methodology for Wegmans Deli Kiosk Version 1.0 Prepared by DELI-cious Developers Rochester Institute of Technology September 15, 2013 1 Table of Contents 1. Process... 3 1.1 Choice... 3 1.2 Description...
METHOD 12 3 empowering managers to succeed Project Management Guidebook ISBN 0-473-10445-8 A bout this e-book This e-book was created by Method123 (see www.method123.com) to help provide you with a simple
i This Page Intentionally Left Blank i Table of Contents SECTION 1: INTRODUCTION AND OVERVIEW...1 SECTION 2: PROJECT CLASSIFICATION FOR OVERSIGHT...7 SECTION 3: DEPARTMENT PROJECT MANAGEMENT REQUIREMENTS...11
Retained Fire Fighters Union Introduction to PRINCE2 Project Management PRINCE2 PRINCE stands for: PRojects IN Controlled Environments and is a structured method which can be applied to any size or type
PROJECT : PREPARED BY: DATE (MM/DD/YYYY): Project Name Typically the Project Manager Project Charter Last Modified Date PROJECT CHARTER VERSION HISTORY VERSION DATE (MM/DD/YYYY) COMMENTS (DRAFT, SIGNED,
Project Management for Everyone Contact Information Adam Donaldson, PMP Business Management & Analysis Group Phone: (202) 994-6867 Cell: (240) 472-2171 Email: firstname.lastname@example.org Objectives Basic understanding
WHY DO I NEED A PROGRAM MANAGEMENT OFFICE (AND HOW DO I GET ONE)? Due to the often complex and risky nature of projects, many organizations experience pressure for consistency in strategy, communication,
PROJECT MANAGEMENT PLAN CHECKLIST The project management plan is a comprehensive document that defines each area of your project. The final document will contain all the required plans you need to manage,
Public Record Office Victoria PROS 10/10 Strategic Management Guideline 5 Records Management Strategy Version Number: 1.0 Issue Date: 19/07/2010 Expiry Date: 19/07/2015 State of Victoria 2010 Version 1.0
At the end of this chapter Project Charter Describe what a project charter is and why it is critical to project success. Explain what a project scope statement is and why it is important. List the various
Project Management for Everyone Contact Information Adam Donaldson, PMP Business Management & Analysis Group System, Analytics & Insights Group Phone: (202) 994-6867 Email: email@example.com Objectives Basic
THE UNITED REPUBLIC OF TANZANIA PRESIDENT S OFFICE PUBLIC SERVICE MANAGEMENT ICT Project Management A Step-by-step Guidebook for Managing ICT Projects and Risks Version 1.0 Date Release 04 Jan 2010 Contact
Systems Analysis and Design in a Changing World, Fifth Edition Learning Objectives Explain the elements of project management and the responsibilities of a project manager Explain project initiation and
This document is part of a series that explain the newly released PMBOK 5th edition. These documents provide simple explanation and summary of the book. However they do not replace the necessity of reading
Audit Checklist The following provides a detailed checklist to assist the audit team in reviewing the health of a project. Relevance (at this time) How relevant is this attribute to this project or audit?
The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor
The Manager s Guide to Avoiding 7 Project Portfolio Pitfalls In today s management by projects mindset, portfolio managers and PMO directors are challenged with ensuring successful delivery in addition
Managing Successful Software Development Projects Mike Thibado 12/28/05 Copyright 2006, Ambient Consulting Table of Contents EXECUTIVE OVERVIEW...3 STATEMENT OF WORK DOCUMENT...4 REQUIREMENTS CHANGE PROCEDURE...5
From Houston S: The Project Manager s Guide to Health Information Technology Implementation. Chicago: HIMSS; 2011; pp 27 39. This book is available on the HIMSS online bookstore at www. himss.org/store.
Netstar Strategic Solutions Practice Development Methodology Netstar Corporation Abstract This document contains a high level description of the development methodology used by the Netstar Strategic Solutions
Analyst Position Description September 4, 2015 Analysis Position Description September 4, 2015 Page i Table of Contents General Characteristics... 1 Career Path... 2 Explanation of Proficiency Level Definitions...
Program Charter Your Organizational Logo here Author(s) Date Name of Program: Name of Program Manager: Template Source: http://www.cvr-it.com Page 1 of 5 Program Charter Use this document to help in the
Characteristic Best Practice Estimate Package Component / GAO Audit Criteria Comprehensive Step 2: Develop the estimating plan Documented in BOE or Separate Appendix to BOE. An analytic approach to cost
PORTFOLIO, PROGRAMME & PROJECT MANAGEMENT MATURITY MODEL (P3M3) 1st February 2006 Version 1.0 1 P3M3 Version 1.0 The OGC logo is a Registered Trade Mark of the Office of Government Commerce This is a Value
Performance planning: A guide for staff development and feedback Version: 2.1 Last Updated: April, 2015 Ryerson University Human Resources 0 Table of contents Performance planning: Staff development and
STRATEGIC PLANNING: A TEN-STEP GUIDE * I. IMPORTANCE OF PLANNING There is broad agreement among nonprofit leaders and experts that planning is a critical component of good management and governance. Planning
Who Should be on Your Project Team: The Importance of Project s and One significant factor contributing to the success of projects is having the right people engaged in the process. Who are the right stakeholders
LEGAL PROJECT MANAGEMENT Cost management of litigation is becoming a focus of legislators in both Australia and the UK, in an attempt to streamline litigation and ensure costs are proportionate. The Civil
1 CIS12-3 IT Project Management Input, Output and Tools of all Processes Marc Conrad D104 (Park Square Building) Marc.Conrad@luton.ac.uk 26/02/2013 18:22:06 Marc Conrad - University of Luton 1 2 Mgmt /
Project Processes for a Project Click the Knowledge Area title (below and left in blue underline) to view the details of each Process Group. Project Process Groups and Knowledge Areas Mapping Project Process
A Guide to Project Management The purpose of this website is to provide a job aid for project management procedures using the IPECC project management model. The information will be provided in a summarized
Chapter Three Information System Development C H A P T E R 3 INFORMATION SYSTEMS DEVELOPMENT Describe the motivation for a system development process in terms of the Capability Maturity Model (CMM) for
WHITE PAPER The Manager s Guide to Avoiding 7 Project Portfolio Pitfalls EXECUTIVE SUMMARY In today s management by projects mindset, portfolio managers and PMO directors are challenged with ensuring successful
COMMUNICATIONS PLAN Version [n.n Month Day, Year] Project Sponsor: [Name of Business Sponsor] Project Manager: [Name of Project Manager] Project Number: [Number Assigned to the Project] Document History
Project Management On-Site Training and Facilitation Services For more information, visit www.performanceweb.org Benefits of On-Site Training The Performance Institute s proven consulting methodology is
Description of Program Management Processes (Initiating, Planning) Topics Covered Program Management Process Groups salient features Description of all processes in Initiating Process Group: Initiate Program
RG Perspective Achieving Business Analysis Excellence Turning Business Analysts into Key Contributors by Building a Center of Excellence 11 Canal Center Plaza Alexandria, VA 22314 HQ 703-548-7006 Fax 703-684-5189
Purpose The purpose of this document is to provide guidance on the practice called Project Close-Out and to describe the practice overview, requirements, best practices, activities, and key terms related
Red River College Course Learning Outcome Alignment with BABOK Version 2 This alignment chart was designed specifically for the use of Red River College. These alignments have not been verified or endorsed
Development, Acquisition, Implementation, and Maintenance of Application Systems Part of a series of notes to help Centers review their own Center internal management processes from the point of view of
Project Zeus Risk Management Plan 1 Baselined: 5/7/1998 Last Modified: N/A Owner: David Jones/Zeus Project Manager Page Section 1. Introduction 3 1.1 Assumptions, Constraints, and Policies 3 1.2 Related
THE ONLY BOOK CAN SIMPLY LEARN PROJECT MANAGEMENT! Page 1 Contents ABOUT THE AUTHOR... 3 WHAT IS PROJECT MANAGEMENT?... 5 ORGANIZATIONAL INFLUENCES AND PROJECT LIFECYCLE... 11 PROJECT MANAGEMENT PROCESSES...
TIME MANAGEMENT TOOLS AND TECHNIQUES FOR PROJECT MANAGEMENT Hazar Hamad Hussain * 1. Introduction The definition of Project as a temporary endeavor... refers that project has to be done within a limited
SCOPE MANAGEMENT PLAN TEMPLATE This Project Scope Management Plan Template is free for you to copy and use on your project and within your organization. We hope that you find this template useful and welcome
Dr. Moshe ben Asher SOC 426, Social Legislation and Social Policy CSUN, Department of Sociology LECTURE NOTES ON STRATEGIC PLANNING WHAT IS STRATEGIC PLANNING OR, PUT ANOTHER WAY, WHAT ARE THE ELEMENTS
Driving business strategy into solid business results demands strong organizational execution capability. Such capability requires mastery of Project Management. It needs every key manager and executive
Switching Tracks: Finding the Right Way to Get to Maturity Level 2 by Heather Oppenheimer and Steve Baldassano When your customer contract requires that your software development process must be CMMI Level
Business Analysis Standardization & Maturity Contact Us: 210.399.4240 firstname.lastname@example.org Copyright 2014 Enfocus Solutions Inc. Enfocus Requirements Suite is a trademark of Enfocus Solutions Inc.
Public Health Accreditation Board STANDARDS & Measures VERSION 1.0 APPLICATION PERIOD 2011-2012 APPROVED MAY 2011 Standard 9.1: Use a performance management system to monitor achievement of organizational
Content Chapter 3 Managing the Information Systems (IS) Project Process of managing IS projects Skills required to be an effective project manager Skills and activities of a project manager during project
Partnering for Project Success: Project Manager and Business Analyst Collaboration By Barbara Carkenord, CBAP, Chris Cartwright, PMP, Robin Grace, CBAP, Larry Goldsmith, PMP, Elizabeth Larson, PMP, CBAP,
Professional Development Coordinator Competencies and Sample Indicators for the Improvement of Adult Education Programs A Publication of Building Professional Development Partnerships for Adult Educators
1 Initiating Forms 1.0 INITIATING PROCESS GROUP The purpose of the initiating process group is to authorize a project, provide a high-level definition of the project, and identify stakeholders. There are
Position Description February 9, 2015 Position Description February 9, 2015 Page i Table of Contents General Characteristics... 2 Career Path... 3 Explanation of Proficiency Level Definitions... 8 Summary
PAGE 1 THE APPLICATION OF A VALUE ASSURANCE SYSTEM TO OIL & GAS DEVELOPMENT PROJECTS (Guido Mattu, Franca Marini) Ing. Guido Mattu More than 25 years experience in Engineering and Project Management activities
9Lenses: Human Resources Suite 9Lenses Software for HR Leaders 9Lenses Software for HR Leaders Software Overview: People are an organization s most valuable asset. With 9Lenses Software for HR Leaders,
Project Management At Penn 1 Fundamentals Course Objective To provide you with an overview of Topics Project Management at Penn () Project Governance Phases & Project Management Activities Project Management
Training Programs for Enterprise-Wide Change Top Five Requirements for Programs that Deliver Prepared by VisionCor, Inc. 1 Contents Summary... 3 Before We Get Started... 3 Program Principles... 4 Business
PROJECT MANAGEMENT METHODOLOGY SECTION 3 -- PLANNING PHASE Table of Contents Introduction...3-1 Overview...3-1 The Process and the Project Plan...3-1 Project Objectives and Scope...3-1 Work Breakdown Structure...3-1
Central Agency for Information Technology Development of a National IT Governance Framework Project Management Agenda 1 What is project management? Why it is important? 2 Leading practices 3 Project management
PROJECT MANAGEMENT PLAN TEMPLATE This Project Management Plan Template is free for you to copy and use on your project and within your organization. We hope that you find this template useful and welcome
Integration Initiating ning Executing Monitoring & Controlling Closing 4.1 Develop Charter Statement Of Work Business Case 4.2 Develop 4.3 Direct and Manage Work 4.4 Monitor and Control Work 4.5 Perform