1 June 15 / Slide 1 / Title of Document Top 10 Things Your Project Manager Should Be Telling You A TUSC PMO Presentation.

Slides:



Advertisements
Similar presentations
Facilitated by Joanne Fraser RiverSystems
Advertisements

The Value of a Project Management Office Copyright: Kathy J. Lang, 2004.
P ROJECT S TATUS S UMMARY. Insert Date Presentation Title Goes Here Sample Project Status/Schedule Summaries In addition to managing a project plan in.
Key Concepts: Definition of a Project Characteristics of a Project
BSBPMG508A Manage Project Risk Manage Project Risk Introduction to Project Risk Diploma of Project Management Qualification Code BSB51507 Unit Code.
Systems Analysis and Design 8 th Edition Chapter 3 Managing Systems Projects.
Project Management Overview. Project driven or Non Project driven Organizational “drivers” Marketing Engineering Manufacturing.
Project Change Management
Systems Analysis and Design 8th Edition
Change is a Process Organizational Stages Individual Stages (ADKAR) Business Need Concept and Design Implementation Post-Implementation Awareness Desire.
Systems Analysis & Design Sixth Edition Systems Analysis & Design Sixth Edition Toolkit Part 4.
By Saurabh Sardesai October 2014.
Section 4.0 Project Implementation. Factors that Ensure Success  Update the project plan  Stay within scope  Authorized change implementation  Providing.
Degree and Graduation Seminar Stakeholder Management
Readiness Index – Is your application ready for Production? Jeff Tatelman SQuAD October 2008.
PRESENTED BY TRUST THOMAS EROMOSELE STUDENT NO:
Chapter 9. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
NORMA GOMEZ, MBA, MSN, RN, CNN Unique Challenges for the Nephrology Professional in Managing Change.
Project Management What The Heck Is That?. Why Do We Need Project Management? Critical towards delivery of effective IT initiatives Ensures we align projects.
Project Human Resource Management
Degree and Graduation Seminar Project Management Processes
Toolkit 4.
Project Management: Madness or Mayhem
Project Risk Management. The Importance of Project Risk Management Project risk management is the art and science of identifying, analyzing, and responding.
Software Testing Lifecycle Practice
What is Project Management? How does it affect how you do your job?
BSBPMG503A Manage Project Time Manage Project Time Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG503A.
1 The Discovery Phase Why it’s the most important phase of any project A TUSC PMO Presentation.
Project Management : Techniques and Tools (60-499) Fall 2014 / Winter 2015.
Travel Website Enhancement Project Project Update First Name Last Name.
Certificate IV in Project Management Introduction to Project Management Course Number Qualification Code BSB41507.
GBA IT Project Management Final Project - Establishment of a Project Management Management Office 10 July, 2003.
BSBPMG508A Manage Project Risk The PMBOK defines Risk as – “an uncertain event or condition that, if it occurs, will have a positive or negative effect.
1 The University of California Berkeley Extension X470 Project Management Lisa Bausell.
BSBPMG405A Apply Human Resource Management Approaches Apply Human Resource Management Approaches Unit Guide C ertificate IV in Project Management
Project Status Report Presenter Name Presentation Date.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
The Project Management Life Cycle. What is the Project Management Life Cycle? A project life cycle simply includes the necessary steps, from beginning.
What is Project Management? What makes it different from a process, service or program?
Project Management: Tips and Tools ITS Project Management Office/K. Kyzer, A. Shoop Nov. 15, 2012.
Strengthening Partnerships: Shaping the Future Portland, OR June 6 th – 10 th, 2004 Planning for Success Implementing the California EDRS.
PLUG IT IN 6 Project Management. 1.Project Management for Information Systems Projects 2.The Project Management Process 3.The Project Management Body.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Project Management Methodology
(Project) RISK MANAGEMENT PROCESS SEPTEMBER 5, 2008.
1 © The Delos Partnership 2004 Project Management Executing the Project.
BSBPMG501A Manage Application of Project Integrative Processes Manage Project Integrative Processes Unit Guide Diploma of Project Management Qualification.
Applying Project Management Practices to Continuously Improve the Chance of IT Project Success Charlie C. Chen, Ph.D., PMP Dept. of Computer Information.
Project Organization Chart Roles & Responsibilities Matrix Add Project Name.
BSBPMG508A Manage Project Risk Manage Project Risk Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG508A.
Where Module 04 : Knowing Where the Project Is 1.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
Software Project Management Lecture 3. What is Project Management?  Project management is “the application of knowledge, skills, tools and techniques.
Implementing Program Management Standards at Duke Energy.
Managing Multiple Projects Steve Westerman California Department of Motor Vehicles Steve Young Mathtech, Inc.
Project Life Presented by Chuck Ray, PMP ITS Project Manager.
Overview of A Guide to the Project Management Body of Knowledge (PMBOK ® Guide)—Fourth Edition.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
Chapter 11 Project Management.
4.4 Monitor and Control Project Work
Description of Revision
People Change Management: The Keys to a Successful Project
Lecture # 3 Software Development Project Management
Lecture 2 Project Management Concepts
Managing Project Work, Scope, Schedules, and Cost
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

1 June 15 / Slide 1 / Title of Document Top 10 Things Your Project Manager Should Be Telling You A TUSC PMO Presentation

2 June 15 / Slide 2 / Title of Document Top Ten Things you need to know 85% of a Project Manager’s time is spent COMMUNICATING

3 June 15 / Slide 3 / Title of Document Top Ten Things you need to know Communication Quality Not enough Information Too much Information Timeliness of Information Communication Plan Setting Expectations Who gets what and when do they get it What are the key things you should know each week What key things should be monitored monthly How much should the delivery team know How much should the management team know Is it in writing?

4 June 15 / Slide 4 / Title of Document Typical vs Critical What is Typical to hear? What is Critical to hear? Analyze the types of communication in key project areas  Scope  Risks  Issues  Cross Project Dependencies  Budget  Project Team  Organizational Readiness

5 June 15 / Slide 5 / Title of Document Scope Management  Typical Scope Management Plan  What is in scope  What is out of scope  Log of scope changes  Critical #1 How much push back are you receiving on scope? #2 What is the overall impact on the original budget?

6 June 15 / Slide 6 / Title of Document Risk Management  Typical Risk Management Plan  Quantification of risk  Qualification of risk  Mitigation plans  Monitoring for new risks  Critical #3 How effective have the Risk Management & Mitigation strategies been?

7 June 15 / Slide 7 / Title of Document Issue Management  Typical Issue management process defined  Type, Owner, Status, Resolution Issue escalation process Weekly review of issues  Critical #4 How effective is the escalation process ?  What issues have been escalated  Did escalation process help to resolve the issue  Are there patterns to the types of issues needing escalation  What types of issues are not being resolved

8 June 15 / Slide 8 / Title of Document Project Dependencies  Typical Identify the dependencies within the project Project level - Critical Path awareness  Critical #5 What other projects have the ability to impact this project’s success  What is the critical path for the entire organization  How are cross project dependencies tracked  Who has the ability to resolve grid lock  How are dependency-level conflicts resolved  Is there an organizational level steering committee

9 June 15 / Slide 9 / Title of Document Budget Management  Typical Overall Budget Weekly burn-rate (Actuals)  Critical #6 Budgetary view of Project progression  Actuals vs Budget – to –date  Estimate at completion  Earned Value Can it really be calculated What level makes sense

10 June 15 / Slide 10 / Title of Document Team Management  Typical Team roster Team turnover  Critical #7 How effective is the team  Internal Factors that contribute Skill Sets, Personality Conflicts, Attitude, Stress Levels Unrealistic deadlines Frequent changes to requirements  External Factors that contribute Travel & commuting issues The right Tool for the job Team Space & Meeting facilities

11 June 15 / Slide 11 / Title of Document Quality  Typical Number of defects found in testing Number of defects found once in production  Critical #8 Quality of Deliverables  What is the Quality Management Plan How is quality measured How frequently is it measured Are there patterns that identify quality issues

12 June 15 / Slide 12 / Title of Document Organizational Readiness  Typical Change Management Plan  Critical #9 How accepting is the organization to change How Effective is the Change Management Team How much push-back is the organization providing ○ Excessive number of Scope changes ○ High-levels of absenteeism ○ Delays in User Acceptance ○ High-level of turnover Change Is a Good Thing I Love Change

13 June 15 / Slide 13 / Title of Document Organizational Readiness #10 How ready is the organization to support the program once it is in production Operational processes and monitoring ○ Who will monitor process ○ Who will monitor data ○ What is the process for logging post-production issues Ongoing Maintenance ○ Who will address post-production issues ○ Who will be able to enhance application when business rules change

14 June 15 / Slide 14 / Title of Document The Top 10 in review Critical Review Point Project Initiation * Project Execution Project Closure Scope Containment w/in OrgOnceMonthly Scope Impact to ProjectMonthlyOnce Risk Mitigation EffectivenessOnceMonthly Issue Escalation EffectivenessMonthly Cross Project DependenciesOnceMonthlyOnce Project Cost ProgressionMonthly Team EffectivenessQuarterly Quality of DeliverablesOnceMonthly Organizational Change AcceptanceMonthly Organizational ReadinessOnceMonthlyWeekly * Assumes a project timeline of 6 months or more.

15 June 15 / Slide 15 / Title of Document A TUSC PMO Presentation Top 10 Things Your Project Manager Should Be Telling You References: A guide to the Project Management Body of Knowledge, (PMBOK Guide). 3 rd Edition, Nov Project Management Institute, Pennsylvania, USA Just Enough Project Management, Curtis R. Cook, McGraw-Hill, 2004

16 June 15 / Slide 16 / Title of Document Thank You