1 / 18

BAM Governance Model BAM Summit April 1 st , 2010

BAM Governance Model BAM Summit April 1 st , 2010. Paul Davis Contractor, CBIIT Essex Management Wendy Ver Hoef Contractor, CBIIT ScenPro, Inc. 2010. Topics. Objectives of this discussion Proposed Working Structure for BAM Governance Composition and Purpose of Governance Teams

mandar
Download Presentation

BAM Governance Model BAM Summit April 1 st , 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BAM Governance ModelBAM SummitApril 1st, 2010 Paul Davis Contractor, CBIIT Essex Management Wendy Ver Hoef Contractor, CBIIT ScenPro, Inc. 2010

  2. Topics • Objectives of this discussion • Proposed Working Structure for BAM Governance • Composition and Purpose of Governance Teams • Governance Team Workflows

  3. Objectives To determine… • If governance is necessary and if so what it should look like • If we can leverage other governance bodies to perform the same functions • What level to release BAM models - at an overall level or within each domain • When to release BAM models - when major areas are completed, periodically on a set schedule regardless of completion status, or only when a domain is complete

  4. Do we need a BAM governance model? A governance model for the BAM is recommended because: • Increasing number and diversity of stakeholders • Clinical Research, Life Sciences, Population Sciences, Patients • Multiple applications/services mapped to the BAM • Multiple external organizations leveraging the BAM for their own internal uses • Increasing amount of coordination and communication • Possible cross-BAM integration • Potential impact from/to development of new services • Developing best practices • Ensuring consistency

  5. What should governance provide? • Strategic direction and alignment with caBIG • Managing stakeholder expectations • Set priorities • Monitor progress • Manage resource allocation • Establish best practices

  6. Proposed Working Structure for BAM Governance

  7. Proposed BAM Working Structure BAM Leadership Team caBIG Community BAM Advisory Group GOVERNANCE Domain 1 BAM Steering Committee Domain 2 BAM Steering Committee … Working Group Working Group caBIG Community Imaging Workspace Developers Architects Patient Advocates PopSci Workspace CDLs CTMS Workspace Service Designers Life Sciences Workspace SMEs Cancer Center Directors

  8. Composition and Purpose of Governance Teams

  9. BAM Leadership Team • Representatives from: • NCI Staff • caBIG Workspace Leads (NCI Contractors) • NCI Analysts • Purpose • Set strategic direction for BAM (across all areas of the BAM) • Identify significant new work for development • Allocate resources as necessary • Resolve complex cross-BAM issues • Approve new releases • Endorse Best Practices • Meeting Frequency • Quarterly

  10. caBIG Community BAM Advisory Group • Representatives from: • caBIG Community (external to NCI) • Purpose • Represent caBIG Community perspective to the BAM Leadership Team • Provide recommendations/advice to the BAM Leadership team as requested • Meeting Frequency • One month prior to the Leadership Team Quarterly meeting

  11. Domain-Specific BAM Steering Committees • Representatives from: • Domain-Specific NCI Staff • Domain-Specific caBIG Workspace Leaders • NCI Analysts • Purpose • Set overall direction within a specific domain based on strategic direction set by BAM Leadership Team • Evaluate new work requests • Prioritize work requests • Coordinate Working Group resources and monitor progress • Escalate issues to BAM Leadership Team • Meeting Frequency • Monthly

  12. Domain-Specific BAM Working Groups • Representatives from: • Domain-Specific NCI Staff • Domain-Specific caBIG Workspace Members • NCI Analysts • Purpose • Develop assigned work deliverables • Develop recommendations based on requests from Steering Committee • Meeting Frequency • As needed for mature/released BAMs (or perhaps monthly) and weekly or bi-weekly for new development

  13. Governance Team Workflows

  14. BAM Development Workflow

  15. BAM Release Workflow

  16. Acknowledgements Wendy Ver Hoef – NCI Analyst, ScenPro, Inc. Michele Ehlman – NCI Analyst, Essex Management David Loose – Essex Management Michael Otjen - Sapient

  17. Objectives To determine… • If governance is necessary and if so what it should look like • If we can leverage other governance bodies to perform the same functions • What level to release BAM models - at an overall level or within each domain • When to release BAM models - when major areas are completed, periodically on a set schedule regardless of completion status, or only when a domain is complete

  18. Thank you Paul Davis paul.davis2@nih.gov 860-941-6246

More Related