Hosted by CU logo University of Colorado
Boulder
Powered by ESGF-CoG logo
Welcome, Guest. | Login | Create Account
CoG logo
You are at the CoG-CU node
 

Metadata: Governance

Why care about governance?

Studies have shown that defining a project's goverance is highly correlated with project sucess (Bannerman, 2009) (Dubinsky, 2011). 

Governance aligns an organization’s practices and procedures with its goals, purposes, and values. Definitions vary, but in general governance involves overseeing, steering, and articulating organizational norms and processes (as opposed to managerial activities such as detailed planning and allocation of effort). Styles of governance range from authoritarian to communalist to anarchical, each with advantages and drawbacks. We have chosen to define our governance ontology after Bannerman (2009) which defines governance as structures, processes, and relational mechanisms:

  • Structures include organizational entities such as steering committees or working groups.
  • Processes included defined tasks that accomplish a projects goal. 
  • Relational mechanisms are arrangements that facilitate the communication between groups.

We have modified Bannerman (2009) to further divide governance into two levels of effort...strategic and operational. This division is useful when examining the project governance roll-up.  

  • A strategic entity is one involved with the identification of long-term or overall aims and interests of a project and the means of achieving them. 
  • An operational entity is involved with the the routine functioning and activities of the project.

Each of the ontological entities below can be divided into strategic and operational versions.  The only difference between is the controlled vocabulary associated with each.  For ease of understanding, they are listed separately.  

Governance Structures

1) Strategic Bodies

Attribute Name Definition Required Cardinality Controlled Vocabulary
Title N/A Yes 1 N/A
Description N/A Yes 1 N/A
Members N/A No Multiple N/A
Terms of Reference A description of the duties and responsibilities of the organizational body. No 1 N/A
Purpose/Role N/A Yes Multiple
  • Strategic Direction
  • Advice or Guidance
  • Evaluation or Review
  • External Coordination
  • Other
Meeting Frequency N/A No 1
  • Daily
  • Weekly
  • Every Two Weeks
  • Monthly
  • Twice Yearly
  • Annually
  • As Needed
  • Other

 

2) Operational Bodies

Attribute Name Definition Required Cardinality Controlled Vocabulary
Title N/A Yes 1 N/A
Description N/A Yes 1 N/A
Members N/A No Multiple N/A
Terms of Reference A description of the duties and responsibilities of the organizational body. No 1  
Purpose/Role N/A Yes Multiple
  • Research
  • Development
  • Requirements Identification
  • Task Prioritization
  • Testing
  • Evaluation or Review
  • Meeting or Event Planning
  • User Support
  • External Coordination
  • Administration
  • Other
Meeting Frequency N/A No 1
  • Daily
  • Weekly
  • Every Two Weeks
  • Monthly
  • Twice Yearly
  • Annually
  • As Needed
  • Other

3) Lead (e.g. Strategic) Organizational Roles

Attribute Name Definition Required Cardinality within the Object Controlled Vocabulary
Title String used to succintly describe a organizational role. Yes 1 NA
Description Long description providing extra information about an organizational role. No 1 NA
Responsible Party Embed the CIM Repsonsible Party object model No Many NA
Role Type of organizational role (see controlled vocabulary) Yes 1
  • Principal Investigator
  • Co-Investigator
  • Program Manager
  • Project Manager
  • Software Architect

3) Member (e.g. Operational) Organizational Roles

Attribute Name Definition Required Cardinality within the Object Controlled Vocabulary
Title String used to succintly describe a organizational role.  Yes 1 NA
Description Long description providing extra information about an organizational role. No 1 NA
Responsible Party Embed the CIM Repsonsible Party object model No Many NA
Role Type of organizational role (see controlled vocabulary) Yes 1
  • Administrative Assistant
  • Data Manager
  • Outreach Coordinator
  • Researcher
  • Software Developer
  • Webmaster

 


Governance Relational Mechanisms

Below is a description of the Communications and Coordination  object, which has several attributes.  The cardinality of the object itself can be many. 

Attribute Name Defintion Required Cardinality within the object Type
Title String used to describe the name of the meeting Yes  1 NA

Meeting Frequency

String used to describe the frequency of the meeting (e.g. Weekly on Wednesdays, Monthly, Yearly) No  1 NA
Participation Instructions Sting used to describe how someone might participate (e.g. dial in phone numbers for a telco, link to a face-2-face meeting) No 1 NA
Members  List of regular participants No  Many NA
Type  String used to describe the type of meeting Yes  1
  • Telco
  • Face-to-face
  • Webinar
  • Internet chat
  • Wiki
  • Mailing list
Purpose Type of meeting (see controlled vocabulary) No 1 Same controlled vocabulary as "organizational body"
Membership Indicates whether the means is open or closed to non-members No 1
  • Open
  • Closed
  • By invitation

Governance Processes

The following attributes are simple Name/Value pairs

Attribute Name

Definition Cardinality
Task Prioritization Strategy  A paragraph describing how tasks are prioritized. This description may include: a) Who participates, b) How often do they meet, c) How do they meet, d) Are the results public (recommended). 1
Requirements Identification Process  A paragraph descibing how requirements are identified.  This description may include a) Who can identify, b) What system is used to track requirments, c) Is the list public (recommended) 1
Governance Philosophy A paragraph describing a project's overall approach to governance. 1
Development Philosophy A paragraph describing a project's overall approach to software development.  1
Last Update: Nov. 5, 2014, 2:39 p.m. by deleted user