Periodic Fable

Monday, 19 November 2007

Risk analysis of e-learning projects

I have recently been doing risk assessments of some e-learning projects we have in train. There are some risks that seem to cross all types of projects in a variety of contexts.

When assessing risks of e-learning projects I consider:

* Likelihood (high, medium, low)
* Potential impact (high, medium, low)
* Speed of onset (fast, slow)

Some of the main risks I have found to be important include:

Unclear roles of individuals and partners in the project

Likelihood: low Impact: high Onset: slow

To avoid/mitigate:
Be very clear about roles of individuals and partners at the beginning and at every meeting.
Hold regular meetings where progress and actions are checked.
Be clear about institution’s organisational structures and the key organisational issues
Basic stakeholder analysis – brainstorm all stakeholders: internal and external. Make time for stakeholders with high impact and high interest and continually monitor stakeholder relationships.
Get in writing, with agreement from all, what the expectations are of each partner in clear and simple terms.
Have a single dedicated project manager
Lack of buy-in from some stakeholders

Likelihood: high Impact: high Onset: slow

To avoid/mitigate:
As early as possible engage and maintain a high level of commitment and engagement needed at senior and operational levels.
Get recognition of the strategic importance of the project relating to key strategies
Get early adopters, champions and enthusiasts involved.
Make realistic and applicable templates for others to follow.
Failure to meet project objectives

Likelihood: medium Impact: high Onset: slow

To avoid/mitigate:
Have clear aims and objectives.
Have a clear project plan and timescale
Set milestones - and meet them
Know “best solution” and “acceptable” outcome
Staff resourcing, changes and sustainability

Likelihood: high Impact: high Onset: fast

To avoid/mitigate:
This one is particularly relevant to HE and FE. Consider motivation and clarity.
Involve personnel at risk at the start. Know where to turn if the worst happens.
Clearly assign resource time from all partners. Agree that schedules will slip if this is not stuck to.
Keep track of other e-learning opportunities and funding
Prioritise user-centred design - practical and relevant to the people involved
Make sure there is sufficient time for testing and evaluation
IT and policy issues

Likelihood: medium Impact: high Onset: fast

To avoid/mitigate:
Include decision makers early on
Do a technical audit with the IT department at the start and find out exactly what is available and possible
It may be necessary to adapt the project if the infrastructure is not going to support it in the timescale of the project.
Labels: e-learning projects, project management, risk analysis

posted by Helen Whitehead 7:51 AM

(0) comments