Difference between revisions of "Work Group Three-Year Plans"
Jump to navigation
Jump to search
m |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
| − | <big>Work Groups' Three Year Planning projects are visible [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?&action=list&FilterProjectNumber=&FilterProjectSponsor=&FilterKeyword=&FilterStatus=3-Year%20Plan%20Item&FilterDateField=&FilterStartDate=&FilterEndDate=&sortBy=ProjectSponsors&sortDirection=asc here]in the Project Insight Searchable Database, having a Project Status of 'Three-Year Plan Item' | + | <big>Work Groups' Three Year Planning projects are visible [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?&action=list&FilterProjectNumber=&FilterProjectSponsor=&FilterKeyword=&FilterStatus=3-Year%20Plan%20Item&FilterDateField=&FilterStartDate=&FilterEndDate=&sortBy=ProjectSponsors&sortDirection=asc here]in the Project Insight Searchable Database, having a Project Status of 'Three-Year Plan Item' |
| + | |||
| + | |||
| + | *Activities identifiable as Projects that can be scheduled in three-year plans should be sent to the [mailto:pmo@hl7.org PMO] for inclusion in the Project Insight Searchable Database. For a project intended to communicate future planning you can include as little as a title, description, and anticipated date when work will begin. | ||
| + | **As planning dates come near, a full project scope statement should be developed and approved through the Work Group, Steering Division, and TSC. | ||
| + | **Three-year plans should be reviewed (and updated if necessary) at least annually. | ||
| − | |||
*Why create three-year plans? See November 2008 Technical Newsletter (Headline bottom of page 7, content begins on page 8), [http://www.hl7.org/documentcenter/public/techNewsletter/HL7_TECHNEWSLETTER_20081125.pdf#page=8 here] | *Why create three-year plans? See November 2008 Technical Newsletter (Headline bottom of page 7, content begins on page 8), [http://www.hl7.org/documentcenter/public/techNewsletter/HL7_TECHNEWSLETTER_20081125.pdf#page=8 here] | ||
| − | *See [http://gforge.hl7.org/gf/download/docmanfileversion/ | + | |
| + | |||
| + | *See [http://gforge.hl7.org/gf/download/docmanfileversion/6760/9299/Three-YearPlan_MC_Guidelines20091224.doc Guidelines on three-year plans], versus what might be more appropriate for inclusion in a Mission and Charter statement. </big> | ||
Latest revision as of 17:04, 8 August 2012
Work Group Three-Year Plans (Strategic Forecasting)
Work Groups' Three Year Planning projects are visible herein the Project Insight Searchable Database, having a Project Status of 'Three-Year Plan Item'
- Activities identifiable as Projects that can be scheduled in three-year plans should be sent to the PMO for inclusion in the Project Insight Searchable Database. For a project intended to communicate future planning you can include as little as a title, description, and anticipated date when work will begin.
- As planning dates come near, a full project scope statement should be developed and approved through the Work Group, Steering Division, and TSC.
- Three-year plans should be reviewed (and updated if necessary) at least annually.
- Why create three-year plans? See November 2008 Technical Newsletter (Headline bottom of page 7, content begins on page 8), here
- See Guidelines on three-year plans, versus what might be more appropriate for inclusion in a Mission and Charter statement.
