Project Initiation process, to ballot or not to ballot

From HL7 TSC
Revision as of 15:45, 3 March 2008 by Charliemccay (talk | contribs) (New page: -----Original Message----- From: Charlie McCay Sent: 28 February 2008 17:26 To: 'Singureanu, Ioana (Patriot Tech)'; George Beeler; T3SD - Technical & Support Svces SD; TSCadmins@lists.h...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search



Original Message-----

From: Charlie McCay Sent: 28 February 2008 17:26 To: 'Singureanu, Ioana (Patriot Tech)'; George Beeler; T3SD - Technical & Support Svces SD; TSCadmins@lists.hl7.org Cc: psc@lists.hl7.org Subject: RE: Motion on Project life cycle and

Ioana The Process being discussed was the "Project Initiation and approval" process. The feeling on the TSC call was that the Project Scope Statement Template should be maintained alongside the Initiation and Approval process that provides its context, and that while these may be published as part of the HDF, they should be maintained by the PSC, and approved by the T3SD and TSC rather than by the ballot process. The expectation would be that the PSC would manage a peer review process, and that the SD and TSC would only withhold approval if they saw a serious flaw in the process, otherwise their comments would be fed into the next round of revisions for the process+template. The rationale for having an SD approval step is to check for any unforeseen publishing / tooling / etc issues. The rationale for having TSC approval is that the TSC is responsible for project coordination and communication across the working group All the best Charlie


Charlie McCay, charlie@RamseySystems.co.uk Ramsey Systems Ltd, 23D Dogpole, Shrewsbury, Shropshire SY1 1ES tel +44 1743 232278 / +44 7808 570172 skype: charliemccay linkedin:charliemccay



Original Message-----

From: Singureanu, Ioana (Patriot Tech) [1] Sent: 28 February 2008 17:07 To: George Beeler; T3SD - Technical & Support Svces SD Cc: psc@lists.hl7.org; Charlie McCay Subject: RE: Motion on Project life cycle and

Hi Woody:

If by "project review processes" you mean "Project lifecycle process", then that process is already approved. If you mean instead the "Project initiation and approval" (which is only one step in the overall lifecycle) then that process was already drafted in included in the HDF DSTU as a part of the Jan 08 ballot. This process will be further clarified in the future DSTU ballot in May. Both lifecycle and project approval are processes developed by PSC and its predecessor.

The item that needs TSC attention is the Project Scope Statement template.

Please clarify...


Original Message-----

From: gwbeeler@gmail.com [2] On Behalf Of George Beeler Sent: Thursday, February 28, 2008 11:55 AM To: T3SD - Technical & Support Svces SD Subject: Fwd: Motion on Project life cycle and

The "original" wording of the TSC minute is here. FYI - Woody



Forwarded message ----------

From: George Beeler <woody@beelers.com> Date: Mon, Feb 25, 2008 at 10:44 AM Subject: Motion on Project life cycle and To: TSC List - new <tscadmins@lists.hl7.org>


The definition of the project review processes (diagrams and notes)

and project scoped statement(s) should be developed by the PSS
Committee, and offered through the T3SD to the TSC for adoption. The
PSS should recommend whether they believe that a single project scope
statement can support all project "types" or not.
--
George W. Beeler, Jr., Ph.D.
Beeler Consulting LLC
Email: woody@beelers.com
Phone: +1 507 254 4810
Fax: +1 507 281 8961


************************************************
To access the Archives of this or other lists or change your list

settings and information, go to: http://www.hl7.org/listservice



-- George W. Beeler, Jr., Ph.D. Beeler Consulting LLC Email: woody@beelers.com Phone: +1 507 254 4810 Fax: +1 507 281 8961


To access the Archives of this or other lists or change your list settings and information, go to: http://www.hl7.org/listservice