Difference between revisions of "Institutional readiness"

From wiki.dpconline.org
Jump to navigation Jump to search
Line 1: Line 1:
==Process==
==Process==
''This should be a numbered list''
''This is the process that a practitioner should follow to build this section of the business case. This should be a numbered list!''
* Maturity models: AIDA, ISO TRAC, NDSA levels etc.
* Maturity models: AIDA, ISO TRAC, NDSA levels etc.
** Purpose: comparator analysis (functional competencies, best practice)
** Purpose: comparator analysis (functional competencies, best practice)
Line 19: Line 19:


==Content==
==Content==
 
''This should describe the contents or structure of the business case, resulting from following the Process above''
Describe the change you want to see in the organisation
Describe the change you want to see in the organisation
* where are we now
* where are we now
Line 45: Line 45:


==Communications==
==Communications==
''Notes relevant to tailoring this section to the appropriate audience and communicating the the business case to that audience''


==Resources==
==Resources==
''These are external resources of relevance to this section. Links can be incorporated into the text above if that is more useful''

Revision as of 10:20, 31 July 2013

Process

This is the process that a practitioner should follow to build this section of the business case. This should be a numbered list!

  • Maturity models: AIDA, ISO TRAC, NDSA levels etc.
    • Purpose: comparator analysis (functional competencies, best practice)
  • Cross-institutional readiness (different groups involved? e.g. IT, library divisions, vendors e.g. hosted services)
    • awareness of other cultures or policy contexts within different divisions (e.g. use of cloud or in-house systems) -- what has got a chance of getting through and what will get laughed out of the room?
  • Digital preservation objectives as part of organisational mission?
  • Gap analysis - skills, functions, required change (also useful to do comparator analysis with peer institutions)
  • Ownership, responsibility, accountability - roles and responsibilities, organisational structure, job specifications
    • clear leadership and communication? collaboration rather than enforcement
  • Stakeholder analysis - demand, expectations, priorities, awareness/engagement - what are they trying to achieve? How does DP support them?
    • Examples from different domains? Internal and external, senior management, users, depositors, etc.


Content

This should describe the contents or structure of the business case, resulting from following the Process above Describe the change you want to see in the organisation

  • where are we now
  • where do we want to be
  • timetable
    • staged progression over time? long-term vision and/or small term component of that?
    • continuous improvement? capacity of the organisation to adapt to change?

Skills

  • staff time / availability
  • exemplar skills profiles from organisations (in-house might mean local tech skills, hosted might mean project management/procurement/SLAs)
  • training programmes - does this mean change to existing posts? or change to team workloads?

Infrastructure

  • approaches to storage/hardware
  • approaches to software (e.g. repository systems)

Finances

  • financial preparedness - ability to fund the necessary infrastructure, staffing
  • sustainability of any funding allocated to DP

Stakeholders

  • ways to engage? language? (e.g. IT: 'business continuity', ITIL)
  • demarkation of functional responsibilities (e.g. define DP policy vs execute part of it; support and guidance vs mandates)

Communications

Notes relevant to tailoring this section to the appropriate audience and communicating the the business case to that audience

Resources

These are external resources of relevance to this section. Links can be incorporated into the text above if that is more useful