Turning ideas into a plan

Following the Taskforce workshop (see previous post) there were a number of issues and potential solutions identified. The next stage in the project was to turn these into specific projects. These projects could be work undertaken internally by Jisc or funded externally.

If you read the previous post you will see a list of template documents filled out during the workshop. These described the issues and then solutions that could be undertaken in less than 6 months, 6-12 months and 12+ months. As the timeframe of the co-design project is short (ends January 2014) this project looked specifically at “quick wins”. The plan, therefore, had to concentrate on these, but also recognise that this work was laying the foundations for potential longer term solutions.

As a reminder, the issues raised by the Taskforce were grouped under three areas: Governance/Strategy, Management and Admin, Users/User experience. Despite having 17 issues under these categories, it was possible to group similar ones together. This resulted in the following projects, or sub-projects, that could potentially be undertaken within this IdM project:

Project 1 – Governance/Definitions
Incorporating the following issues:
Governance/Strategy – Policies/Definitions
Governance/Strategy – AIM Higher: Culture/Ownership of problem
Governance/Strategy – Ownership of the problem
Management/Admin – Purpose of AIM system
Management/Admin – Granularity
Summary: Identify and contact 2-3 institutions to use their IdM documents and processes with examples and input into a workshop involving university representatives (HR, registry, IT, library and users) to help define roles, responsibilities and ownership, categories of users, relationship between IdM and other systems. Publish guidance on roles and responsibilities, user definitions and categories, and purpose of IdM systems.

Project 2 – Account Management
Incorporating the following issue: Management/Admin – Account Management
Summary: Set up IdM expert group to review existing solutions and design protocols and processes for semi automated creation and deletion of accounts. Publish outputs from the review.

Project 3 – Toolkit (target audience)
Incorporating the following issue: Management/Admin – Support
Summary: To ensure IT and Library Directors have the support required to position IdM with their institutions, the Toolkit developers will investigate taking existing parts of the Toolkit and look at the potential in expanding it to include briefing papers targeting specific positions within HE.

Project 4 – Map to IdM resources
Incorporating the following issue: Management/Admin – A thing for Jisc to do
Summary: Collate links and information on all Jisc funded IdM resources and project outputs. Synthesise and avoid use of technical jargon. Create a dedicated page/site with a top level IdM topic focus with links to IdM related resources.

Project 5 – Usage monitoring
Incorporating the following issue: Management/Admin – Usage Monitoring
Summary: Jisc Comms to publicise importance of usage statistics through a briefing paper, for example. Incorporate outputs from Raptor, Raptor pilots, JUSP, Raptor-JUse and LAMP projects.

Project 6 – Licensing
Incorporating the following issue: Management/Admin – Licensing
Summary: Jisc Collections to investigate and explore the definition of a software and content model licence and publish recommendations to institutions. Requires “definition of common user groups” from Project 1 – Governance/Definitions as an input.

Project 7 – User centric identities
Incorporating the following issue: Management/Admin – Cloud identity
Summary: Investigate use of 3rd party credentials (such as cloud, social media, Apple, Android or Microsoft app store, etc.) to access institutional resources and publish recommendations to institutions.

Project 8 – Usability
Incorporating the following issue: User/user experience – Usability
Summary: Undertake a landscape study to investigate previous work in this area, followed by a behavioural study in approximately 3 institutions of user behaviour when logging on to resources and their awareness of entitlements. Publish usability report and recommendations.

With all of these projects, the Taskforce will be involved by providing input, feedback and recommendations through the mailing list or project-led workshops.

As the timeframe is short it would not be possible to complete all of the above projects so they were prioritised by the Taskforce as follows:

Highest priority
Project 1 – Governance/Definitions
Project 6 – Licensing (requires outputs from Project 1)

Project 8 – Usability

Project 5 – Usage monitoring

Project 3 – Toolkit (target audience)
Project 4 – Map to IdM Resources

Project 7 – User centric identities

Project 2 – Account Management
Lowest priority

The two projects with the lowest priority (User Centric identities and Account Management) would not be considered further as part of this IdM project. However, they could still be considered if the IdM co-design work is continued after January 2014.

This left six projects that could progress. The next stage was to write more detail on each project’s requirements in project briefs and contact the relevant people who could actually do the work. More detail on the specific work of these projects will be revealed in further blog posts.

Share and Enjoy

  • Facebook
  • Twitter
  • Delicious
  • LinkedIn
  • StumbleUpon
  • Add to favorites
  • Email
  • RSS