Project Request Review Process

Following materiel was recreated (mostly copied) from Dave Hamill's presentation to TSC on Monday at Fall 2007 WGM

Presented

September 17th, 2007 at Atlanta WGM by David Hamill, Director, Project Management Office

Proposal responded to a Key Initiative from the Board to the PMO to:

With the T3F, develop the criteria/process for triaging and prioritizing project requests and put in place by the Plenary meeting

Previous Process vs. New Process

Previous Process	New Process
Create Scope Statement TC Review PMO Review ARB Review PMO/TTPL Oversee Methodology	Create Scope Statement TC Review SD Review PMO/TSC Review PMO/PSC Oversee Methodology

Previous Process

1. Step 1
   • Project Facilitator creates a Project Scope Statement.
2. Step 2
   • Technical Committee reviews and approves Scope Statement.
   • Project Facilitator resolves any issues.
3. Step 3
   • Project Facilitator (co-chair) submits Project Scope Statement to PMO.
   • PMO reviews and approves Scope Statement. Project Facilitator resolves any issues.
4. Step 4
   • PMO submits the Scope Statement to the ARB for review.
   • ARB reviews Scope Statement.
   • Project Facilitator resolves any issues brought forth by ARB
5. Step 5
   • PMO and Project Lifecycle Transition Team insures that the HL7 project methodology is adhered to throughout the project.

New Process

1. Step 1
   • Project Facilitator creates a Project Scope Statement.
2. Step 2
   • Technical Committee reviews and approves Scope Statement.
   • Project Facilitator resolves any issues.
3. Step 3 (replaces the approval work currently done by the ARB)
   • Project Facilitator notifies the “new” TSC of the new Scope Statement
   • Project Facilitator indicates the appropriate Steering Division needs to review/approve Scope #*Statement for criteria such as:
     • Is this project within the scope of work done by HL7
     • Is it within the scope of the sponsoring committee
     • How is it related to other projects
     • How is it related to the activities of other committees
   • SD indicates priority within SD, if necessary. Priority is based on resources, target dates and technical strategies.
   • SD review could result in the following:
     • Amended scope statement
     • Project needs to be reviewed (jointly or separately) by another SD
     • Board approval may be necessary if the project requires internal or external funding or collaboration with an external body
   • Project Facilitator resolves any issues brought forth by the SD.
4. Step 4
   • Project Facilitator (co-chair) submits Project Scope Statement to PMO.
   • PMO reviews and approves Scope Statement.
   • Project Facilitator resolves any issues.
   • Steering Division submits Scope Statement to TSC for approval.
   • TSC approval includes the following:
     • Validate points identified by SD and PMO
     • Assign a TSC level priority
   • The SD & TSC reviews replace the ARB review, however the ARB may be called upon to resolve architectural issues.
5. Step 5
   • PMO and Project Services Committee insure that the HL7 project methodology is adhered to throughout the project.