This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Tooling Strategy and Process Revision"

From HL7Wiki
Jump to navigation Jump to search
 
(16 intermediate revisions by 3 users not shown)
Line 8: Line 8:
  
 
==Project Information==
 
==Project Information==
[http://www.hl7.org/Special/committees/v3toolstaskforce/projects.cfm?action=edit&ProjectNumber=801 Project Insight # 801] Description: Revise existing Tooling Work Group Processes to include coordination with other Work Groups and to specify criteria for tooling project selection and prioritization.
+
[http://www.hl7.org/Special/committees/v3toolstaskforce/projects.cfm?action=edit&ProjectNumber=801 Project Insight # 801] Description: Revise existing Tooling Work Group Processes to include coordination with other Work Groups and to specify criteria for [[Tooling Project Selection and Prioritization]].
 
*Initially titled 'Process alignment for ES and Tooling', with description "Tooling will work with Electronic Services to align the requirements gathering and tool selection processes to ensure resources are available to develop or enhance requests for tools that come to either group that may impact the other group."  
 
*Initially titled 'Process alignment for ES and Tooling', with description "Tooling will work with Electronic Services to align the requirements gathering and tool selection processes to ensure resources are available to develop or enhance requests for tools that come to either group that may impact the other group."  
 
*Project facilitator: Jane Curry
 
*Project facilitator: Jane Curry
 +
 +
==Project Resources==
 +
*Jane Curry, facilitator
 +
*Lynn Laakso, staff support
 +
*Dennis Cheung,
 +
*Andy Stechishin
 +
*Woody Beeler
 +
*other volunteers please self-identify
  
 
==Meeting Information==
 
==Meeting Information==
*Project meeting schedule as part of regular Tooling WG conference call
+
*Project meeting schedule - 10 AM ET following Regular Tooling call
{{:Tooling Meeting Information}}
+
**Use Tooling WG conference call line - Dial 770-657-9270 and enter pass code 586935#
 +
**GoToMeeting at https://www1.gotomeeting.com/join/699884034 (**GoToMeeting ID: 699-884-034)
  
 +
Meeting notes:
 +
* no 2012-12-13 Tooling Strategy Call
 +
*[[2012-12-06 Tooling Strategy Call]]
 +
*[[2012-11-29 Tooling Strategy Call]]
 +
*[[2012-11-21 Tooling Strategy Call]] (rescheduled for US Thanksgiving)
 +
*[[2012-11-15 Tooling Strategy Call]]
 +
*[[2012-11-08 Tooling Strategy Call]]
 +
*[[2012-11-01 Tooling Strategy Call]]
 +
*[[2012-10-25 Tooling Strategy Call]]
  
 
==Status==
 
==Status==
*Jane working on RFP
+
Strategy statement: <br/>
*Objectives:
+
It is HL7’s intent to create and maintain a comprehensive set of superior tools for every recognized  step of the development, balloting, publishing and USE of its products according to the requirements of the HL7 Board, membership and user’s needs.
**Revised process documented - Target: 2012-01 '''needs revision'''
+
*[http://gforge.hl7.org/gf/download/docmanfileversion/7114/9934/ToolingStrategyDraft20121206.docx Tooling Strategy proposal by WG]
**Revised process accepted by the board - Target: 2012-05 '''needs revision'''
+
*[http://gforge.hl7.org/gf/download/docmanfileversion/7236/10155/ToolingStrategyPolicyImplications_20130214.docx Tooling Strategy Policy Implications]
Additional elements of the Tooling Strategy:
+
*[http://gforge.hl7.org/gf/download/docmanfileversion/7070/9860/ToolingCostingCriteria.docx proposed Tooling Costing Criteria]
*defining coordination with other Work Groups
+
*[http://gforge.hl7.org/gf/download/docmanfileversion/7235/10146/ToolingStrategy_Gantt.xlsx draft Gantt chart of objectives]
**establishing Tooling Liaisons to other Work Groups,
 
**regular reporting from Liaisons
 
**setting expectations for active participation in Tooling work group
 
***Formalize processes that increase non-tool developers’ active participation in tooling projects (e.g. acceptance testing)
 
 
 
  
  
==Issues/Hot Topics==
+
==HL7’s Tooling Strategy quality metrics==
*Part of new strategy is that funding will be a subsidy for additional participation for those that are already working on areas of interest. This is in comparison to historical commissioning of the building of tools by commercial tool builders. (from 2012May Tooling WGM Minutes)
 
**Proposal for trialing a new process for funded projects using the EHRS-FM and MAX projects.
 
***a number of Tooling projects, some of which are volunteer driven need to move from a strategy of commissioning people to perform projects to a strategy of participation in other tooling efforts to build tools that work for us as well. The clear path is probably to fund this effort (from [http://hl7tsc.org/wiki/index.php?title=2012-05-12_TSC_WGM_Agenda 2012-05-12 TSC Meeting minutes])
 
***some guidance needed on what the budget document design should be for targeting likely budget amounts, such as: here are the people, these resources, and this is what we could accomplish for this chunk of money, and can scale back according to funding available. (from [[2012-04-19_Tooling_Call]])
 
*'''Proposed Process for funded tool development projects''' (see also [http://gforge.hl7.org/gf/download/docmanfileversion/6861/9450/RFPreleaseandselectionprocess.docx Proposed RFP Release and Selection Process])
 
** PSS mandatory, w co-sponsorship from requesting Work Groups
 
** Requesting Work Groups to provide resources to document requirements, review deliverables and test software; may request funding subsidy
 
** Requirements documented w sufficient detail to produce time/cost estimates
 
** Request for proposal based on requirements to solicit resources to be developed by requesting Work Groups and reviewed by Tooling
 
** Request to be sent to Contracts listserve to solicit resources
 
** May request funding subsidy for identified roles in the project that cannot be completed with only volunteers
 
** Criteria for selecting resources gives preference to individuals already volunteering
 
** Proposals need to indicate estimated time contributing as volunteer and estimated funded time
 
** Contracts to be approved deliverables based
 
** Tooling to lead proposal evaluation, any Tooling WG members will recuse themselves for any proposals they are involved in
 
** Successful proposals to enter into contract w HQ
 
** Tooling and requesting Work Groups to review and approve deliverables
 
** More detailed processes being worked out with HQ and CTO
 
:
 
'''Specification of criteria for tooling project selection and prioritization'''
 
* Recognizing that strategic efforts like SAIF, FHIR & Tooling become components of an overarching technical strategy
 
**That strategy is aligned with the organizational objectives as identified in the strategic initiatives
 
*HL7’s strategic intent to use the Eclipse Platform, including the expectations of intra-tool data exchange (from [[2012-04-12_Tooling_Call]])
 
* FHIR initiative and tooling: the production of the standard is based on a tool chain. The tool chain is open source and hosted on GForge SVN. What is Tooling's responsibility on that tool chain maintenance and provision? The ability to produce the standard from the tool chain is the concern.  By the next January WGM in Phoenix we may want to schedule a joint quarter to decide how to manage the tool chain going forward.
 
*Resolved 2011Sept: we prioritize tools:
 
**firstly, based on the critical path to ensure standards are produced on a regular basis according to schedule,
 
**secondly, based on Board direction and
 
**thirdly, subject to available funding to complete an existing tooling project so as not to dilute the ability to fully complete a project
 
:
 
'''Selection criteria in RFP''' (approved by Tooling WG on [[2012-06-21_Tooling_Call]])
 
*#Preference for resources who are already volunteering in HL7 in some capacity
 
*#Preference for resources with current involvement in sponsored project
 
*#Preference for open source software with rights to create derivatives
 
*#Meets stated licensing criteria
 
*#Proposal contains information to evaluate budget implications
 
*#Proposal indicates what deliverables would be provided in a phased approach to accommodate budget constraints and demonstrate progress
 
*#Proposal formatted to support selection process
 
*#Familiarity with methods and technology used by HL7
 
*#*Ability to work in distributed virtual environment
 
*#*Demonstrates approach to protect HL7 Intellectual Property (e.g. use of MIF-Lite)
 
*#Approach proposed for change management and knowledge and skills transfer
 
*#*During project
 
*#*Ongoing support
 
*#Compatibility of proposed tooling platform with target tooling architecture
 
*#Skill and experience of proposed resources
 
*#*Communication skills
 
*#*Software development skills
 
  
 +
The Tooling Strategy will be considered successful when:
 +
# The number of tool smiths increases
 +
# All Tools HL7 specifications are dependent on are clearly specified and users can easily find out how to use them
 +
# All Tools change management processes are actively enforced
 +
# Contributors wishing to contribute tools understand what process to follow and what responsibilities they can expect HL7 to take on
  
 +
Objectives:
 +
*Provide clarity to work groups concerning their options and obligations when choosing to use tools to produce that will be required for a Standards Specification / methodology;
 +
*Provide some certainty at a corporate level concerning what funding is required to acquire and maintain tools and how this can impact the budget;
 +
*Provide a foundation for raising money from potential sponsors by clearly specifying the roles and responsibilities of all parties and what processes are used to produce tools useful to the HL7 Community.
  
 +
===Tooling Strategy document sections and assignments===
 +
*Tooling Governance:
 +
*#Tooling Governance Groups
 +
*#*defining coordination with other Work Groups
 +
*#**establishing [[Tooling Liaisons]] to other Work Groups,
 +
*#**regular reporting from Liaisons
 +
*#**setting expectations for active participation in Tooling work group
 +
*#***Formalize processes that increase non-tool developers’ active participation in tooling projects (e.g. acceptance testing
 +
*#Tooling Risk Assessment
 +
*#*Risk assessment should involve cost/benefit analysis before undertaking projects if tooling is a mitigating strategy
 +
*#*Need state transitions for decisions and recommendations. Criteria for weighing cost/benefit need to include all types of costs and all types of benefits. (Jane/Michael)
 +
*#Candidate Metrics (Andy to draft)
 +
*#*descriptions
 +
*#*cost formula - see [http://gforge.hl7.org/gf/download/docmanfileversion/7070/9860/ToolingCostingCriteria.docx Tooling Costing Criteria]
 +
*#*Tie benefits to Strategic Initiatives
 +
*Tooling Management
 +
*#Identify management groups, potentially along product lines or platforms
 +
*#Identify Candidate Management process
 +
*#Identify product line management practices for tooling coordinators
 +
*#:see issue from [[Tooling_Project_Selection_and_Prioritization]]: ''the production of the standard is based on a tool chain, open source and hosted on GForge SVN. Tooling's responsibility on that tool chain maintenance and provision is the ability to produce the standard from the tool chain. By the next January WGM in Phoenix we may want to schedule a joint quarter to decide how to manage the tool chain going forward.''
 +
*#*Requires us to identify existing tools and understand the tools well enough to promote them and their fit in our continuum of tool use
 +
*#*MWB and Trifolia are HL7-specific tools
 +
*#*Consider tools not HL7-specific like Sparx EA, MS Visio
 +
*Tooling methodology
 +
**[http://gforge.hl7.org/gf/download/docmanfileversion/6861/9450/RFPreleaseandselectionprocess.docx Proposed RFP Release and Selection Process] from [[2012-06-21_Tooling_Call]], see [[Tooling Project Selection and Prioritization]].
 +
**Requirements, Configuration, and Release Management document needs updating. (Jane)
  
 
==Project Documents==
 
==Project Documents==
*[http://gforge.hl7.org/gf/download/docmanfileversion/6861/9450/RFPreleaseandselectionprocess.docx Proposed RFP Release and Selection Process] as discussed at [[2012-06-21_Tooling_Call]]
+
*[http://lists.hl7.org/read/attachment/220487/2/DRAFT+HL7+Tooling+Strategy+--+0.1.docx Tooling strategy from 2012Sept WGM]
 +
*[http://gforge.hl7.org/gf/download/docmanfileversion/6534/8853/ToolingStrategyDeckv11.pptx Tooling strategy proposed slide deck]
 
*[http://gforge.hl7.org/gf/project/tool-proc-arch/tracker/?action=TrackerItemBrowse&tracker_id=445 GForge issues tracker for Tooling]
 
*[http://gforge.hl7.org/gf/project/tool-proc-arch/tracker/?action=TrackerItemBrowse&tracker_id=445 GForge issues tracker for Tooling]
 
*Initial work at [[HL7_-_Tooling_%26_Electronic_Services_alignment]]
 
*Initial work at [[HL7_-_Tooling_%26_Electronic_Services_alignment]]

Latest revision as of 14:28, 25 March 2013

Project Insight # 801 Project Description: Revise existing Tooling Work Group Processes to include coordination with other Work Groups and to specify criteria for tooling project selection and prioritization.

Project Need: The HL7 Board has emphasized that the Tooling Work Group needs to focus on tools that make implementing HL7 standards easier as well as those needed to develop and publish HL7 standards. Since tools now often have a web presentation, the Electronic Services Work Group needs to be consulted, as well as Publishing to ensure tools remain coherent and to coordinate resources and schedules.

Return to Tooling Work Group

Project Information

Project Insight # 801 Description: Revise existing Tooling Work Group Processes to include coordination with other Work Groups and to specify criteria for Tooling Project Selection and Prioritization.

  • Initially titled 'Process alignment for ES and Tooling', with description "Tooling will work with Electronic Services to align the requirements gathering and tool selection processes to ensure resources are available to develop or enhance requests for tools that come to either group that may impact the other group."
  • Project facilitator: Jane Curry

Project Resources

  • Jane Curry, facilitator
  • Lynn Laakso, staff support
  • Dennis Cheung,
  • Andy Stechishin
  • Woody Beeler
  • other volunteers please self-identify

Meeting Information

  • Project meeting schedule - 10 AM ET following Regular Tooling call

Meeting notes:

Status

Strategy statement:
It is HL7’s intent to create and maintain a comprehensive set of superior tools for every recognized step of the development, balloting, publishing and USE of its products according to the requirements of the HL7 Board, membership and user’s needs.


HL7’s Tooling Strategy quality metrics

The Tooling Strategy will be considered successful when:

  1. The number of tool smiths increases
  2. All Tools HL7 specifications are dependent on are clearly specified and users can easily find out how to use them
  3. All Tools change management processes are actively enforced
  4. Contributors wishing to contribute tools understand what process to follow and what responsibilities they can expect HL7 to take on

Objectives:

  • Provide clarity to work groups concerning their options and obligations when choosing to use tools to produce that will be required for a Standards Specification / methodology;
  • Provide some certainty at a corporate level concerning what funding is required to acquire and maintain tools and how this can impact the budget;
  • Provide a foundation for raising money from potential sponsors by clearly specifying the roles and responsibilities of all parties and what processes are used to produce tools useful to the HL7 Community.

Tooling Strategy document sections and assignments

  • Tooling Governance:
    1. Tooling Governance Groups
      • defining coordination with other Work Groups
        • establishing Tooling Liaisons to other Work Groups,
        • regular reporting from Liaisons
        • setting expectations for active participation in Tooling work group
          • Formalize processes that increase non-tool developers’ active participation in tooling projects (e.g. acceptance testing
    2. Tooling Risk Assessment
      • Risk assessment should involve cost/benefit analysis before undertaking projects if tooling is a mitigating strategy
      • Need state transitions for decisions and recommendations. Criteria for weighing cost/benefit need to include all types of costs and all types of benefits. (Jane/Michael)
    3. Candidate Metrics (Andy to draft)
  • Tooling Management
    1. Identify management groups, potentially along product lines or platforms
    2. Identify Candidate Management process
    3. Identify product line management practices for tooling coordinators
      see issue from Tooling_Project_Selection_and_Prioritization: the production of the standard is based on a tool chain, open source and hosted on GForge SVN. Tooling's responsibility on that tool chain maintenance and provision is the ability to produce the standard from the tool chain. By the next January WGM in Phoenix we may want to schedule a joint quarter to decide how to manage the tool chain going forward.
      • Requires us to identify existing tools and understand the tools well enough to promote them and their fit in our continuum of tool use
      • MWB and Trifolia are HL7-specific tools
      • Consider tools not HL7-specific like Sparx EA, MS Visio
  • Tooling methodology

Project Documents