1 / 19

The IBIS Community of Practice

The IBIS Community of Practice. April 15, 2009. Purpose. Introduce the notion of a Community of Practice (CoP) for those of us using the IBIS-PH software. Problem. Software is expensive to develop. The industry changes quickly.

rmadden
Télécharger la présentation

The IBIS Community of Practice

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. The IBIS Community of Practice April 15, 2009

  2. Purpose • Introduce the notion of a Community of Practice (CoP) for those of us using the IBIS-PH software.

  3. Problem • Software is expensive to develop. • The industry changes quickly. • Utah cannot maintain IBIS into the future without the generous federal funding we have been so fortunate to have received.

  4. Proposed Solution • Systems that were supported by federal $$ are essentially “open source” • Not technically part of the Open Source Initiative.

  5. Partial Definition of Open Source: • Free Redistribution No royalties or fees • Source Code Must include source code • Derived Works Allow modifications, derived works, and distribution of such • . . . From Open Source Initiative website: http://www.opensource.org/docs/definition.php

  6. Community of Practice • “The current environment for organizations is one that is characterized by uncertainty and continuous change. This rapid and dynamic pace of change is forcing organizations that were accustomed to structure and routine to become ones that must improvise solutions quickly and correctly… Knowledge Networks: Innovation through Communities of Practice. Paul Hildreth and Chris Kimble (Eds.) (2004) <http://www.cs.york.ac.uk/mis/knicop.html>

  7. Community of Practice • “…To respond to this changed environment organizations are moving away from the structures of the past that are based on hierarchies, discrete groups and teams and moving towards those based on more fluid and emergent organizational forms such as networks and communities.”

  8. Community of Practice • How does it function? • People become members of a CoP through shared practices; they are linked to each other through their involvement in certain common activities. It is mutual engagement that binds members of a CoP together as a social entity (Wenger, 1998).

  9. Community of Practice • Common Purpose / Motivation • The CoP members will have some sort of common goal or common purpose and it is often the case that the CoP is internally motivated i.e. driven by the members themselves as opposed to some external driver.

  10. Community of Practice • Relationships • Relationships are a key part of a CoP and is what makes it possible for a team to become a CoP - as the informal relationships develop the source of legitimation in the group shifts in emphasis. These relationships are key to the issues of trust and identity in a CoP.

  11. Community of Practice • Formal or Informal? • In many cases, a CoP is not a formally constituted group and membership is entirely voluntary. In some cases, the organization might not even be aware of its existence.

  12. Community of Practice • What is produced? • The members of a CoP build up an agreed set of communal resources over time. This "shared repertoire" of resources represents the material traces of the community. Written files can constitute a more explicit aspect of this common repository although more intangible aspects such as procedures, policies, and specific idioms may also be included (Wenger, 1998).

  13. IBIS Community of Practice • Maintain source code (use staff talent or share contractual talent) • Develop features, functionality • Share ideas, developments • Provide mutual technical assistance

  14. Adopters-live Utah Arizona New Mexico Missouri New Jersey Adopters – in progress Washington D.C. Alaska National Center for Health Statistics (NCHS) Explorers Minnesota Wisconsin New Hampshire Massachusetts University of Kentucky National Association of City and County Health Officials (NACCHO) IBIS Community of Practice

  15. Benefits • Share strength, development resources • E.g., Average .5 FTE in each of 18 states: 9 FTEs working on developing and maintaining the software. • Share ideas for use, training • Provide mutual technical support

  16. Community of Practice Website www.ibisph.org • Source code repository • Web forum • Software documentation

  17. What’s In It for CoP Members? • Health programs, policy-makers, community members gain greater data insight (evidence-based decision-making). • Analysts are freed of some tedious data reporting tasks. • Leverage Utah’s 14 years of development. • Little out-of-pocket software and hardware costs for enterprise class applications. • Can deploy additional system features over time.

  18. What’s In It for Utah? • IBIS will benefit from additional perspectives, knowledge and experience. • After 2007, Utah could no longer afford a full-time, dedicated developer. As IBIS is open source, it is hoped that others will enhance and share their enhancements with the community, thus allowing the applications to continue to evolve – which benefits everyone.

More Related