A Capability Maturity Model for Research Data Management
CMM for RDM » 1. Data Management in General » 1.1 Commitment to Perform

Changes for document 1.1 Commitment to Perform

Last modified by Arden Kirkland on 2014/05/18 11:53
From version 23.1
edited by Arden Kirkland
on 2014/05/10 10:55
To version 24.1
edited by Arden Kirkland
on 2014/05/14 20:08
Change comment: added rubric

Content changes

... ... @@ -43,6 +43,24 @@
43 43 Whether a data management project is at a community level or research group level, the objectives and expectations should be clearly defined and communicated. This is especially important when multiple partners are involved because documenting the nature of collaborative partnership supports open communication ([[Hale et al., 2003>>||anchor="Hale"]]). Policies for data management, use, and services are an instrument of communication. Providing them on an institution or project’s websites as separate documents offers open communication with the community members and constituencies. Data service providers should maintain open and effective communication venues for the community. For example, Cornell’s Research Data Management Service Group uses their website to provide communication channels for their community on different levels ([[https:~~/~~/confluence.cornell.edu/display/rdmsgweb/Home>>url:https://confluence.cornell.edu/display/rdmsgweb/Home||rel="__blank"]]).
44 44
45 45
46 +== Rubric ==
47 +
48 +|= |=Rubric for 1.1 - Commitment to Perform
49 +|Level 0
50 +This process or practice is not being observed |No steps have been taken to establish organizational policies or senior management sponsorship for stakeholder or end user needs, quantitative objectives, or communication policies
51 +|Level 1: Initial
52 +Data are managed intuitively at project level without clear goals and practices |Stakeholder and end user needs, objectives, and communication have been considered minimally by individual team members, but nothing has been quantified or included in organizational policies or senior management sponsorship
53 +|Level 2: Managed
54 +DM process is characterized for projects and often reactive |Stakeholder and end user needs and objectives have been recorded for this project, but have not taken wider community needs or standards into account and have not resulted in organizational policies or senior management sponsorship
55 +|Level 3: Defined
56 +DM is characterized for the organization/community and proactive |The project follows approaches to stakeholder and end user needs and objectives that have been defined for the entire community or institution, as codified in organizational policies with senior management sponsorship
57 +|Level 4: Quantitatively Managed
58 +DM is measured and controlled |Quantitative quality goals have been established regarding stakeholder and end user needs and objectives, and both data and practices are systematically measured for quality.
59 +|Level 5: Optimizing
60 +Focus on process improvement |Processes regarding stakeholder and end user needs and objectives are evaluated on a regular basis, and necessary improvements are implemented.
61 +
62 +
63 +
46 46 == References ==
47 47
48 48 {{id name="Cornell"/}}
... ... @@ -68,3 +68,39 @@
68 68
69 69
70 70
89 +
90 +(% style="position: absolute; left: 511px; top: 1607px; width: 1px; height: 1px; overflow: hidden;" %)
91 +(((
92 +(% border="1" cellpadding="0" cellspacing="0" dir="ltr" style="table-layout: fixed; font-size: 13px; font-family: arial, sans, sans-serif; border: 1px solid rgb(204, 204, 204);" %)
93 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)(% class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; border-spacing: 0px; font-size: medium;" %)Examples for 1.1 - Commitment to Perform
94 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Level 0
95 +This process or practice is not being observed|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)No steps have been taken to establish organizational policies or senior management sponsorship for stakeholder or end user needs, quantitative objectives, or communication policies
96 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Level 1: Initial
97 +Data are managed intuitively at project level without clear goals and practices|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Stakeholder and end user needs, objectives, and communication have been considered minimally by individual team members, but nothing has been quantified or included in organizational policies or senior management sponsorship
98 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Level 2: Managed
99 +DM process is characterized for projects and often reactive|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Stakeholder and end user needs and objectives have been recorded for this project, but have not taken wider community needs or standards into account and have not resulted in organizational policies or senior management sponsorship
100 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Level 3: Defined
101 +DM is characterized for the organization/community and proactive|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)The project follows approaches to stakeholder and end user needs and objectives that have been defined for the entire community or institution, as codified in organizational policies with senior management sponsorship
102 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Level 4: Quantitatively Managed
103 +DM is measured and controlled|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Quantitative quality goals have been established regarding stakeholder and end user needs and objectives, and both data and practices are systematically measured for quality.
104 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Level 5: Optimizing
105 +Focus on process improvement|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Processes regarding stakeholder and end user needs and objectives are evaluated on a regular basis, and necessary improvements are implemented.
106 +)))
107 +
108 +(% style="position: absolute; left: 511px; top: 1607px; width: 1px; height: 1px; overflow: hidden;" %)
109 +(((
110 +(% border="1" cellpadding="0" cellspacing="0" dir="ltr" style="table-layout: fixed; font-size: 13px; font-family: arial, sans, sans-serif; border: 1px solid rgb(204, 204, 204);" %)
111 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)(% class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; border-spacing: 0px; font-size: medium;" %)Examples for 1.1 - Commitment to Perform
112 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Level 0
113 +This process or practice is not being observed|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)No steps have been taken to establish organizational policies or senior management sponsorship for stakeholder or end user needs, quantitative objectives, or communication policies
114 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Level 1: Initial
115 +Data are managed intuitively at project level without clear goals and practices|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Stakeholder and end user needs, objectives, and communication have been considered minimally by individual team members, but nothing has been quantified or included in organizational policies or senior management sponsorship
116 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Level 2: Managed
117 +DM process is characterized for projects and often reactive|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Stakeholder and end user needs and objectives have been recorded for this project, but have not taken wider community needs or standards into account and have not resulted in organizational policies or senior management sponsorship
118 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Level 3: Defined
119 +DM is characterized for the organization/community and proactive|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)The project follows approaches to stakeholder and end user needs and objectives that have been defined for the entire community or institution, as codified in organizational policies with senior management sponsorship
120 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Level 4: Quantitatively Managed
121 +DM is measured and controlled|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Quantitative quality goals have been established regarding stakeholder and end user needs and objectives, and both data and practices are systematically measured for quality.
122 +(% style="height: 16px;" %)|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Level 5: Optimizing
123 +Focus on process improvement|(% style="padding: 0px 3px; vertical-align: bottom; text-align: left; direction: ltr;" %)Processes regarding stakeholder and end user needs and objectives are evaluated on a regular basis, and necessary improvements are implemented.
124 +)))

XWiki Enterprise 5.1-milestone-1 - Documentation