Technical PM Presentation


Published on

Presentation for a technical project management role, focusing on communication, documentation, change management and entry/exit criteria.

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

Technical PM Presentation

  2. 2. The Goal <ul><li>To consistently and reliably deliver quality, pre-determined features for the company’s product suite on a regularly scheduled basis. </li></ul><ul><li>Requirements to meet this goal: </li></ul><ul><ul><li>Pre-agreed feature list for each release </li></ul></ul><ul><ul><li>Team-wide communications plan </li></ul></ul><ul><ul><li>Deadline-driven collaboration ethic </li></ul></ul><ul><ul><li>Established documentation standards & practices </li></ul></ul><ul><ul><li>Transparent change management process </li></ul></ul><ul><ul><li>Pre-determined entry & exit criteria </li></ul></ul>
  3. 3. The Six Week Cycle Myth <ul><li>A six-week release cycle is really (approximately) a ten-week project cycle. </li></ul><ul><li>Why this distinction is important: Effective schedule management (including resource planning, change, communications, documentation and client expectation management) needs to take into account the time before and after the release. The definition of “project” needs to expand to include the needs and expectations of all stakeholders, both internal and external. </li></ul>Week 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 R1                                                     R2                                                     R3                                                     R4                                                     R5
  4. 4. Communications Mgmt – Approach 90% of Project Management is Communication
  5. 5. Communications Mgmt – Meetings <ul><li>All meetings have published agendas, action items & minutes </li></ul><ul><li>Regularly scheduled meetings, supplemented with as-needed ad hoc meetings </li></ul><ul><li>Planning: feature lockdown, risks & issues, entry & exit criteria agreement, documentation expectations, resource allocation & schedule development </li></ul><ul><li>Executing: status, change management & trade-off evaluation, risk & issue management, entry & exit criteria review, documentation collaboration & review, team-to-team handoff & review </li></ul><ul><li>Closing: evaluation, unresolved issues, documentation publication </li></ul>Agenda & Minutes Productivity
  6. 6. Communications Mgmt – Knowledge Mgmt <ul><li>Centralized transparent communications forums for capturing on-going activity </li></ul><ul><ul><li>Regularly published status reports </li></ul></ul><ul><ul><li>Published & updated risks & issues </li></ul></ul><ul><ul><li>Publicly available project calendar & timeline </li></ul></ul>
  7. 7. Documentation Management <ul><li>Documentation Requirements </li></ul><ul><ul><li>Pre-determined ownership responsibilities (author, reviewers, approvers, etc.) </li></ul></ul><ul><ul><li>Centralized, searchable, team-wide repository </li></ul></ul><ul><ul><li>Audience-appropriate format & content </li></ul></ul><ul><li>Documentation Categories </li></ul><ul><ul><li>Internal </li></ul></ul><ul><ul><ul><li>Product – features, specifications, release notes, training materials </li></ul></ul></ul><ul><ul><ul><li>Project documents – risks, issues, scheduling & resource planning, status updates, entry/exit criteria, scope & change log </li></ul></ul></ul><ul><ul><li>External </li></ul></ul><ul><ul><ul><li>Release – features, training materials, schedule, known issues </li></ul></ul></ul>
  8. 8. Change Management <ul><li>Managing change </li></ul><ul><ul><li>Understanding & communicating trade-offs </li></ul></ul><ul><ul><ul><li>Who gets to decide? </li></ul></ul></ul><ul><ul><ul><li>Is everyone aware of the repercussions? </li></ul></ul></ul><ul><ul><li>Tracking & logging change decisions </li></ul></ul><ul><ul><ul><li>Centralized, transparent documenting of changes & implications </li></ul></ul></ul><ul><ul><li>Managing expectations as early as possible </li></ul></ul><ul><ul><ul><li>Bad news does not get better with age </li></ul></ul></ul><ul><ul><ul><li>Communicate early & often </li></ul></ul></ul>
  9. 9. Entry & Exit Criteria <ul><li>Cannot have “exit criteria” without “entry criteria” </li></ul><ul><li>Pre-agreed deliverable, timeline and ownership </li></ul><ul><li>Transparent change process, including publication of trade-offs & downstream impact </li></ul>
  10. 10. Decision Checkpoints <ul><li>Pre-agreed </li></ul><ul><ul><li>Status updates </li></ul></ul><ul><ul><li>Risk review/planning </li></ul></ul><ul><li>Ad hoc </li></ul><ul><ul><li>Risk mitigation </li></ul></ul><ul><ul><li>Issue management </li></ul></ul><ul><ul><li>Change negotiation </li></ul></ul><ul><ul><li>Trade-off decisions </li></ul></ul>
  11. 11. Questions?