PMO Templates, version 2000
by Robert Perrine

 
Proverbs 16:3
"Commit your work to the Lord and your plans will be established."

    Purpose
    These web pages describe a Project I referred to as the "Recursion Project".
    The high level objectives for this project are:
  1. Identify the documents required to complete a mid-sized project.
  2. Build an example of each of those documents.
  3. Provide links to other examples of each document.
    There are three business needs behind this project
  1. A desire to share my knowledge with others.
  2. A desire to expand my knowledge.
  3. A desire to transform my knowledge into a tangible, transportable form.

  4. This third desire stems from a process that educators call "synthesis". Basically, synthesis occurs when you take materials that you have studied and create something new. Synthesis is a time honored sign of the transition from journeyman to master. A journeyman travels from master to master, using the tools built by the master. A master is expected to build his or her own tools. I've built plenty of tools for other masters. Now I am building my own.
    Contents
  1. References
  2. Documents
    1. Methodology
    2. Scope
    3. Communications
    4. Human Resources
    5. Time
    6. Integration
  3. Project Archives
    1. Formal Acceptance
    2. Change Requests
    3. Status Reports
  4. Copyright
  5. Revision History
  1. Key References
    The majority of the references used during this project are web sites listed, below, in conjunction with the appropriate documents. The following table lists additional references with broader scope.
      Published materials
    1. A Guide to the Project Management Body of Knowledge (PMBOK Guide). Project Management Institute. ISBN 1-880410-25-7.
    2. PMI Compendium of Project Management Practices. Project Management Institute. ISBN 1-930699-02-6.
    3.  
      Comprehensive web sites
    4. Canadian Enhanced Management Framework
    5. Michigan State project template bundle previously located at
      "http://www.michigan.gov/dit/0,1607,7-139-18391_22016_22372---,00.html"
    6. New York State project management templates

    7.  
      PMI web sites
    8. Project Management Institute
    9. PMI local chapter in Orange County, California, USA

    10.  
  2. Documents
    1. Methodology
      1. Methodology Guidelines
        • Recursion 1-1 Guidelines
        • University of Waterloo Project Management Methodology Project previously located at
          "http://ist.uwaterloo.ca/pmg/pminist/PMinIST_min_sep9.htm
      2. Methodology Templates
      3. Methodology Policies
        • PENDING: Recursion 1-3 Policies Bundle
      4. Methodology Distribution Set
        • Recursion 1-4 Distribution is THIS web site
    2. Scope
      1. Product Description
      2. Project Charter
        • Recursion 2-2 Project Charter
        • Project Charter for W3C XML Protocol development
        • Project Charter for the PMI PMBOK 2004 project previously located at
          http://www.pmi.org/info/PP_PMBOK04Charter.pdf
        • Project Charter for the North Dakota Stagenet Project previously located at
          http://www.stagenet.nd.gov/current-projects/project-charter.pdf
        • Project Charter for Kings County judicial information handling previously located at
          http://www.metrokc.gov/oirm/projects/lsj/program_charter2-1-1.doc
      3. Scope Statement
        • Recursion 2-3 Scope Statement
        • Scope Statement for the Minnesota Unemployment Insurance upgrade previously located at
          http://www.uimn.org/uitip/library_archive.htm
      4. Scope Management Plan
        • PENDING: Recursion 2-4 Scope Management Plan
        • Scope Change Request Guidelines for Washington DOT
        • Scope Management Plan template from the University of Waterloo previously located at
          http://ist.uwaterloo.ca/projects/templates/smp.pdf
        • Scope Change Guidelines from Washington DIS previously located at
          http://www.dis.wa.gov/pmframework/examples/changemgmt.htm
      5. Work Breakdown Structure
      6. Formal Acceptance
        • Recursion 2-6 Formal Acceptance Template
        • Recursion 2-6 Formal Acceptance on Component will be placed in the on-line project archive.
        • Formal Acceptance dispute from ICL previously located at
          http://www.scit.wlv.ac.uk/~cm1995/cbr/cases/case05/ELEVEN4.HTM
        • Formal Acceptance Test Plan from Gemini previously located at
          http://ftp.gemini.edu/gemini_DAO/GAOS/CDR/cdr_appendices_pdf/Appendix_18.pdf
        • Formal Acceptance Plan for US Coast Guard Lifeboat previously located at
          http://www.uscg.mil/hq/g-a/47'mlb/Acceptance%20Inst.htm
        • Formal Acceptance of Hong Kong Educational Quality Project previously located at
          http://www.info.gov.hk/qef/download/qa_tod/Fin_RptE.doc
    3. Communications
      1. Communications Management Plan
        • Recursion 3-1 Communications Management Plan
        • Communications Plan for a US Navy Recruiting project previously located at
          http://www.nmci.navy.mil/Primary_Areas/Schedule/Files/Recruiter%20Transition%20Project%20Files/Files/Recruiter_updates_52104/Recruiting_Project_Comm_Mgmt_Plan.doc
        • Communications Management Plan for University of Melbourne website redesign previously located at
          http://www.mdhs.unimelb.edu.au/forstaff/docs/comm_mgmt_plan.pdf

      2. Project Report
      3. Project Archives
      4. Change Requests
      5. Lessons Learned
      6. Performance Reports
        • PENDING: Recursion 3-6 Performance Report
      7. Project Presentations
        • PENDING: Recursion 3-7 Project Presentation
        • Project Presentation by CIO to Montana Legislature previously located at
          http://dli.state.mt.us/phoenix/ciopresentationtolegislature.pdf
      8. Project Closeout
        • PENDING: Recursion 3-8 Project Closeout
    4. Human Resources
      1. Organization Chart
      2. Roles and Responsibilities Assignments
      3. Staffing Management Plan
      4. Project Team Directory
    5. Time
      1. Activity Lists
      2. Project Schedule
      3. Schedule Management Plan
    6. Integration
      1. Project Plan
        • Project Plan for the Virginia Web-based Standards of Learning Technology Initiative
        • Project Plan for Seattle transit improvements previously located at
          http://www.cityofseattle.net/humanservices/ads/AreaPlan/Transportation/TranspInventoryNeedsAssmtDec2003.pdf
        • Project Plan for the Georgia Botanical Gardens "Our Shared Forests" project previously located at
          http://www.arches.uga.edu/~ting/7550/ProjectPlanF1Designs.pdf
        • Project Plan for the Central European Air Traffic Services previously located at
          http://www.eurocontrol.int/ceats/reports/CWPMP%201.1%20May%202003_Released%20Issue.pdf
    7. Pending
      1. Cost Estimating
        • Cost estimating handbook for NASA previously located at
          http://www.jsc.nasa.gov/bu2/PCEHHTML/pceh.htm
      2. Checklists
      3. Earned Value
        • Time Tracking
        • Earned Value by Tammo T. Wilkens previously located at
          http://www.acq.osd.mil/pm/paperpres/wilkins_art.pdf
        • Earned Value by Ozzie Lomax previously located at
          http://www.kcpmichapter.org/lomax.ppt
      4. Risk Identification
        • Risk Identification by G.Blau and G.Sinclair previously located at
          http://www.cepmagazine.org/pdf/060180.pdf
      5. BenchMarking
  3.  
     
  4. Project Archives
    1. Formal Acceptance
    2. Change Requests
    3. Status Reports
     
     
  5. Copyright
    Summer 2004, Irvine, California, USA, copyright by Robert E. Perrine, PMP.
    Offered as is, with no warranty regarding the accuracy or suitability of this material. Copyright reserved. Please, however free to copy and share these documents with the following restrictions.
    1. You may not charge for use or distribution of this material.
    2. Your usage of this material is conditioned upon your compliance with the PMI Code of Ethics.
    3. All distributions must be made with the intent to further the collected wisdom of humanity.
    4. You may not remove my name or my copyright notices from these documents.

  6. Thank you for taking the time to visit my web site.

    Robert Perrine, PMP
    25 June 2004

  7. Revision History
    1. 25 Jun 2004. Robert Perrine. Initial release.
    2. 27 Jun 2004. Robert Perrine. Began adding links to external example documents.
    3. 03 Jul 2004. Robert Perrine. Initial upload of Scope documents.
    4. 04 Jul 2004. Robert Perrine. Created Project Archives section and did initial upload of Communications documents.
    5. 05 Jul 2004. Robert Perrine. Renumbered all documents to match the Work Breakdown Structure. Continued effort on Communications and Scope.
    6. 06 Jul 2004. Robert Perrine. Rebuilt all documents using an updated style template.
    7. 07 Jul 2004. Robert Perrine. First upload of a Time document.
    8. 10 Jul 2004. Robert Perrine. Began conversion from MS Word to Adobe InDesign.
    9. 23 Jul 2004. Robert Perrine. Updated numbering and naming for Methodology, Scope and Communications.
    10. 16 Nov 2007. Robert Perrine. Began conversion from Adobe back to Microsoft. I strongly recommend you avoid using products from Adobe.