A Perspective On Project Management

686 views

Published on

Illustrates Tony Guinta\'s approach to Project Management. © Copyright 2008, Tony Guinta, PMP. All rights reserved.

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
686
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Copyright © 2008 Tony Guinta, PMP
  • A Perspective On Project Management

    1. 1. A Perspective on Project Management Tony Guinta, PMP
    2. 2. Role of Project Management <ul><li>Work with customers to understand and define business objectives and strategies </li></ul><ul><li>Turn business strategies into project objectives, deliverables, and requirements </li></ul><ul><li>Deploy and manage available resources in order to meet project objectives </li></ul>June 7, 2009 Copyright © 2008 Tony Guinta, PMP
    3. 3. Meeting Business & Project Objectives June 7, 2009 Copyright © 2008 Tony Guinta, PMP Define business objectives Determine strategies Turn strategies into project objectives Define deliverables Define requirements Implement Attain customer acceptance Build Test Design Improve
    4. 4. Importance in Defining Objectives <ul><li>Avoid embracing a strategy without first clarifying the objective </li></ul><ul><li>If objectives are unclear, strategies will be faulty and lead to poor results </li></ul><ul><li>Objectives should be SMART: </li></ul><ul><ul><li>Specific – what is to be achieved? </li></ul></ul><ul><ul><li>Measureable – how do we know the objective has been accomplished? </li></ul></ul><ul><ul><li>Achievable – is the objective feasible? </li></ul></ul><ul><ul><li>Realistic – can it be accomplished with available resources? </li></ul></ul><ul><ul><li>Time specific – when must the objective be met? </li></ul></ul>June 7, 2009 Copyright © 2008 Tony Guinta, PMP
    5. 5. Objectives & Strategies June 7, 2009 Copyright © 2008 Tony Guinta, PMP Define Objective Increase revenue by 10% by Q3 Indentify possible strategies Produce new product Expand into new markets Cost Demand Qualify & quantify Select strategy $ Potential Cost Demand $ Potential Risk Risk Produce new product
    6. 6. Project Objectives June 7, 2009 Copyright © 2008 Tony Guinta, PMP Business Objective Strategy Project Objective + = Increase revenue by 10% by Q3 Create new products Build Widget ABC to increase revenue by 10% by Q3
    7. 7. June 7, 2009 Copyright © 2008 Tony Guinta, PMP Define problem or opportunity System does not produce XYZ report Quantify Results in 2 hrs/day to manually create report Define objective 2 hrs/day x 260 days/year = 520 hrs/year 520 hrs x $16.83/hr = $8,751.60/year, or 25% of one resource Reduce costs in creating report XYZ by $8,751.60 by start of next year Defining objectives related to a problem or opportunity
    8. 8. Objectives, Deliverables, & Requirements June 7, 2009 Copyright © 2008 Tony Guinta, PMP Project Objective Deliverable Requirements Reduce costs in creating report XYZ by $8,751.60 by start of next year Develop automated version of report XYZ Layout Level of detail Aggregates Attributes Parameters
    9. 9. Document Flow of Objectives, Deliverables, & Requirements June 7, 2009 Copyright © 2008 Tony Guinta, PMP Project Charter Objectives Scope Statement Deliverables Objectives Deliverables Requirements WBS WBS Dictionary Work packages Activities List Network Diagram MS Project Plan Activities Critical Path Schedule Resources Cost Activities Objectives
    10. 10. Tracking & Reporting Project Progress June 7, 2009 Copyright © 2008 Tony Guinta, PMP MS Project Plan Excel Spreadsheets Actual Costs Approved Changes Schedule Data Cost Data Issues Log Risk Details Risk Register Issue Details Status Report Schedule Details Cost Details Actual Work
    11. 11. Project Management Plan June 7, 2009 Copyright © 2008 Tony Guinta, PMP Scope Management Plan Schedule Management Plan Cost Management Plan Quality Management Plan Staffing Management Plan Communications Management Plan Risk Management Plan Procurement Management Plan Project Management Plan
    12. 12. Risk Management June 7, 2009 Copyright © 2008 Tony Guinta, PMP <ul><li>Meetings </li></ul><ul><li>Interviews </li></ul><ul><li>Questionnaires </li></ul><ul><li>Probability </li></ul><ul><li>Impact </li></ul><ul><li>Estimated Monetary Value </li></ul><ul><li>(EVM = Probability x $Outcome) </li></ul><ul><li>Risk </li></ul><ul><li>Owner </li></ul><ul><li>Trigger </li></ul><ul><li>Response </li></ul><ul><li>Occurrences </li></ul><ul><li>Trigger Events </li></ul><ul><li>Responses </li></ul><ul><li>Workarounds </li></ul><ul><li>Newly identified risks </li></ul>Identify Qualify Quantify Plan Response Risk Register Monitor
    13. 13. Configuration Management June 7, 2009 Copyright © 2008 Tony Guinta, PMP Change Control Process Version Control Process Document Templates Project Issues Log Defect Tracking System Document Repository Support Knowledge Base Configuration Management Project Lifecycle Process
    14. 14. Meetings <ul><li>Every meeting has an agenda </li></ul><ul><li>The objective of the meeting is made clear from the start </li></ul><ul><li>Tangent items are documented in the issues log and participants gently steered back to the agenda </li></ul><ul><li>Action items documented and assigned </li></ul><ul><li>Recap email sent out after meeting with action items and follow-up plan </li></ul>June 7, 2009 Copyright © 2008 Tony Guinta, PMP Steering Status Review Workshops Customer Team Objectives Deliverables Requirements Functional Design Technical Design Milestone Design Prototype
    15. 15. Status Reports <ul><li>Clearly states the status of: </li></ul><ul><li>Schedule </li></ul><ul><li>Budget </li></ul><ul><li>Milestones </li></ul><ul><li>Risks – newly identified risks, trigger events, occurrences, effectiveness of responses </li></ul><ul><li>Issues impacting scope, schedule, budget, and quality along with corrective action being taken </li></ul><ul><li>Approved changes </li></ul>June 7, 2009 Copyright © 2008 Tony Guinta, PMP
    16. 16. Problem Solving <ul><li>Separate symptom from cause </li></ul><ul><li>Determine root cause before implementing corrective action </li></ul><ul><li>If corrective action requires a change, it must go through the change control process </li></ul>June 7, 2009 Copyright © 2008 Tony Guinta, PMP Define Problem Identify possible causes Determine response Determine root cause Execute response
    17. 17. Team Management <ul><li>Facilitate communication among team members </li></ul><ul><li>Lead through exercises, e.g.: </li></ul><ul><ul><li>Problem Solving </li></ul></ul><ul><ul><li>Defining business rules / workflow </li></ul></ul><ul><ul><li>Functional design </li></ul></ul><ul><ul><li>Technical design </li></ul></ul><ul><li>One-on-one interaction: </li></ul><ul><ul><li>Mentor (process, communication, problem solving, politics & diplomacy) </li></ul></ul><ul><ul><li>Provide constructive feedback </li></ul></ul><ul><ul><li>Assist in defining career goals and taking the appropriate action in order to achieve them </li></ul></ul>June 7, 2009 Copyright © 2008 Tony Guinta, PMP
    18. 18. Team Assignments <ul><li>Assignments are always clearly defined </li></ul><ul><ul><li>Objective – what will be achieved by meeting the deliverable? </li></ul></ul><ul><ul><li>Deliverable - what is the tangible work product to be delivered? </li></ul></ul><ul><ul><li>Time - When is it due? </li></ul></ul><ul><ul><li>Success criteria - How will it be measured? </li></ul></ul><ul><li>Follow-up </li></ul><ul><ul><li>Evaluate work product </li></ul></ul><ul><ul><li>Provide positive and constructive feedback </li></ul></ul>June 7, 2009 Copyright © 2008 Tony Guinta, PMP
    19. 19. Quality Assurance <ul><li>Success criteria </li></ul><ul><li>Benchmarks </li></ul><ul><li>Data validation approach </li></ul>June 7, 2009 Copyright © 2008 Tony Guinta, PMP Define test cases Create testing scripts Test Submit defects for repair <ul><li>Execution step </li></ul><ul><li>Expected results / success criteria </li></ul><ul><li>Execute plan </li></ul><ul><li>Document results </li></ul><ul><li>Submit through defect tracking system </li></ul><ul><li>Assign appropriate resource </li></ul><ul><li>Indicate severity / priority </li></ul>
    20. 20. Implementation June 7, 2009 Copyright © 2008 Tony Guinta, PMP <ul><li>Routers / Switches </li></ul><ul><li>LAN </li></ul><ul><li>WAN </li></ul><ul><li>Hardware </li></ul><ul><li>Software </li></ul><ul><li>Configuration </li></ul><ul><li>Backup Schedule </li></ul><ul><li>Database installation </li></ul><ul><li>Hardware </li></ul><ul><li>Runtime environment </li></ul><ul><li>Security </li></ul><ul><li>Training </li></ul><ul><li>Support </li></ul><ul><li>Start Time </li></ul><ul><li>Finish Time </li></ul><ul><li>Dependencies </li></ul>Prepare production environment Execution Plan Network Infrastructure Server Environment User Environment Resources Tasks
    21. 21. Closing June 7, 2009 Copyright © 2008 Tony Guinta, PMP <ul><li>Objectives </li></ul><ul><li>Deliverables </li></ul><ul><li>Requirements </li></ul><ul><li>All documentation updated and in sync </li></ul><ul><li>What went right </li></ul><ul><li>What went wrong and how to avoid in the future </li></ul><ul><li>Insure satisfaction </li></ul><ul><li>Gain signoff to close project and release resources </li></ul>Verify Scope Verify Project Documentation Update Lessons Learned Customer Signoff
    22. 22. Ongoing Support June 7, 2009 Copyright © 2008 Tony Guinta, PMP <ul><li>FAQ </li></ul><ul><li>Common issues and responses </li></ul><ul><li>Knowledge base (data model, function reference, etc.) </li></ul><ul><li>Change Control Board </li></ul><ul><li>Request submission process </li></ul><ul><li>Approval workflow </li></ul><ul><li>Criteria and Timetable for change levels (e.g., Level 1, 2, 3) </li></ul><ul><li>Service Levels (e.g., Level I, 2, & 3) </li></ul><ul><ul><li>Resources </li></ul></ul><ul><ul><li>Response time </li></ul></ul><ul><ul><li>After-hours support </li></ul></ul><ul><li>Who to contact if resource unavailable or unresponsive </li></ul><ul><li>Issue # </li></ul><ul><li>Severity </li></ul><ul><li>Assigned to </li></ul><ul><li>Details </li></ul><ul><li>Etc. </li></ul>Support Documentation Change Control Process Service Levels Escalation Trouble Ticket Tracking System
    23. 23. June 7, 2009 Copyright © 2008 Tony Guinta, PMP THE BEGINNING Tony Guinta, PMP SlinkySays Consulting, Inc. 3432 Denmark Ave # 76 Eagan, MN 55123-1088 651-206-0055 [email_address] http://www.slinkysays.com

    ×