Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
Project Document Cover Sheet
Project Information
Project Acronym
DOULS
Project Title
Distributed Open University Learning Systems
Start Date
1 July 2010
Lead Institution
The Open University
Project Director
Niall Sclater, The Open University Strategy Unit
Project Manager &
contact details
Judith Pickering
LTS, Perry Building
The Open University
Walton Hall
Milton Keynes MK7 6AA
Partner Institutions
N/A
Project Web URL
www.open.ac.uk/blogs/douls
Programme Name
(and number)
E-learning programme: Distributed VLE
Programme Manager
Sarah Davies s.davies@jisc.ac.uk
End Date
31 December 2011
Document Name
Document Title
Development Plan
Reporting Period
July 2010 – January 2011
Author(s) & project
role
Judith Pickering, Project Manager
Jason Platts, Lead Technical Developer
Date
09/08/2010
Filename
DOULS_Development
Plan.doc
URL
Access
 Project and JISC internal
 General dissemination
Document History
Version
Date
Comments
0.1
07/12/2010
Initial Draft – J.Platts
0.2
06/01/2011
Second draft – Judith Pickering
0.3
07/01/2011
Updates to development information – J.Platts
0.4
14/01/2011
Third draft – Judith Pickering
Page 1 of 16
Document title: JISC Project Plan
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
Development Plan
In work package 2 of the project a development plan was conducted to clarify and confirm the
developments as outlined in the project plan, to justify why and to outline the associated risks
and dependencies.
Summary of visioning stage
A ‘visioning’ activity, researching and developing ideas for a ‘distributed’ Open University
learning system, was initiated by Niall Sclater (Project Director) through a serious of meetings
with project members/contributors and other institutional stakeholders. This focussed on the
potential uses of distributed learning systems, other institutions use of distributed learning and
internal developments in this area.
The report led us to conclude that there is a need to improve integration between Google
Apps for Education (a platform that is becoming a key way for students to interact with and
share content) and Moodle, the world’s most popular learning management system. In many
institutions, integration is limited to a single sign-on. It is the aim of this project to improve
integration and move towards enabling the distribution of data held within the VLE, making it
accessible from external platforms, e.g., Google, Facebook etc.
There are various potential benefits of integrating Moodle and Google Apps more closely e.g.:



Providing a more integrated (and hence less disjointed and confusing) experience for
students
Students being able to view content from their LMS/VLE in a more customisable,
personalised environment – e.g. using iGoogle
Teachers being able to create innovative learning activities using rapidly evolving
functionality not available in Moodle – but able to present it within a Moodle site
There are various ways in which Google Apps and Moodle could be further integrated:
1. Moodle transfers data to existing app, e.g., the presentation of Moodle RSS feeds
within iGoogle or viewing Moodle calendar dates within the Google calendar.
2. Existing app transfers data to Moodle, e.g., as a student flags work complete within
their Google calendar, this updates the corresponding data within the Moodle
calendar.
3. Moodle transfers data to new app, e.g., a new forum app presented in iGoogle which
gives an immediate overview of how many new posts have been made on each
forum the user is following.
4. New app transfers data to Moodle, e.g., when a user views a forum post within the
new forum Moodle app, the post is marked as read when viewed from either the
Google or Moodle platform.
5. App presented within Moodle, e.g., incorporation of a Google Doc as a Moodle
activity accessed via Moodle and then exported into the users Google account.
6. App content presented within new Moodle block, e.g., the provision of a Gmail block
within Moodle which simply links to the users Gmail account enabling the user to
monitor for incoming mail from within Moodle.
7. Deeper integration. This has been investigated by the OU Moodle Development
team who found that there are several serious technical hurdles to this, the most
significant of which is that Moodle is written in PHP, Google Apps in Java and
therefore there is no current way of emulating PHP in Google Apps without rewriting
the Moodle platform.
Page 2 of 16
Document title: JISC Project Plan
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
It is the aim of this project to deliver greater integration of Google Apps and Moodle by
undertaking the following developments:
Integration
Google
calendar
integration
Brief description
To provide the export of key study planner and VLE calendar events via a
standard iCal format, this integration will allow for students to add events
to their personal calendar in Google Apps. With regard to the study
planner items, it will be possible to create a new calendar view per
module (Google Calendar allows for multiple, colour coded calendars for
different activities). A desirable addition to this would be to establish a
means of keeping added items up to date, rather than needing to export
and import afresh if there are any updates.
Google VLE
activity module
The intention is to add another VLE/Moodle activity module that can be
added to a module site or page that interacts with a student’s Google
Apps account (or suggests that the student opt-in if not present).
In a non-collaborative case, the VLE activity can be used by the student
as directed to create a new Google document from a template that is then
pushed to their personal account to be completed or populated with
content. The student can then manage subsequent sharing via accessing
their Google Docs storage directly.
Google
Collaborative
Activity
A more collaborative approach then brings in the capability for a group
activity with more specific control over document permissions and
ownership. It is intended that the VLE/Moodle controls access, allowing
more flexible definitions of groups and groupings as for other VLE
activities. The document being worked on could then be displayed in an
embedded iFrame for work in situ on the VLE page, while still allowing for
direct access from Google Docs separately if desired.
Online personas have been created as a way to verify requirements and inform decisions
being made about the Open University Web site, from the broadest concepts to the details of
specific sites or features.
Staff workshops were conducted to educate staff in the principles of distributed learning in the
form of gadgets and widgets. This was supported by the production of a guide, ‘A short
introduction to gadgets’. Outputs from these meetings was a consolidated list of gadget ideas
which was taken forward to an expert focus group whose task it was to select and evolve the
best ideas. At a meeting of the steering group a shortlist of the following six gadgets were
approved for further specification.
Gadget
Study
Planner
Brief description
Gadget to show current week of calendar view (study planner / calendar).
Gadget needs to know userid, passwd, makes a request to Moodle. Moodle
needs to expose data first in a way that the gadget can consume e.g. RSS
feed, web service or going to a web page that returns data back.Gadget
displays planner. Maybe facility to add Module calendar events to your
Google calendar?
Module
news
News feeds – module specific but also specific to a particular topic area, e.g.,
psychology (therefore broader than module). These news feeds could be
internal or external to OU. Faculties and /or library would need to build/define
these sources, e.g., delicious tags etc.
Forum
Gadget to display the latest forum post(s).
Page 3 of 16
Document title: JISC Project Plan
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
update
Study
Would be able to capture and display data identifying students who are at a
Buddy
similar stage in their study of a module, e.g., all students who are studying
chapter x or attempting to do activity y. This information could be made
available to students (who opt into service), giving them the option of studying
together / set up their own forum etc.
TMA buddy
Enables student to select a visual way to represent how far they have
progressed through a course. The visualisation should have a playful tone
(because it sits in iGoogle), e.g., an egg timer, a cake, a clock etc. Students
can select a visual representation from a range of options. Students could
also sign up for prompting in the lead up to TMAs. The prompting should be
able to be modified by the student, i.e., the student can amend if there are
periods when they can predict they won’t be studying, e.g., it takes account of
holidays etc. Students can choose whether they would like the prompting to
be particularly frequent, e.g., ‘yes, please hassle me’. Again the hassling
should be more playful / informal outside of the OU VLE. The gadget could
be further developed so it links with the OU story (mood) gadget enabling
students to respond e.g., with ‘I’m on it’, ‘I’m struggling’, ‘help’. Perhaps a
conditional response to the student reply could be the triggering of tutor
support. After submission of the TMA the student could then feedback how
happy they were with their submission which may link with their final scores .
Module
suggestion
A ‘future course’ gadget that gathers student’s personal interests and
suggests courses based upon those interests.
Overview of development plans
Development work required to meet the vision of a distributed learning system falls under two
broad categories; developing integrations with external systems (Google Apps), developing
services and gadgets.
Phase I Development – Jan 2011 – June 2011
This phase will focus primarily on developing integrations between Moodle and Google Apps,
and developing the frameworks and tools required to build gadgets that integrate with Moodle.
This phase will also consider how to present gadgets to users, including issues of promotion,
education, installation and support. Usability test are currently underway to investigate
whether a Google start page or a standard iGoogle page would be the most appropriate
vehicle for gadget delivery to users.
Other areas that will require investigation are:
Considerations when integrating with Moodle 2.0, the OUs VLE platform
Issues associated with user profiles
Security associated with domain level API access
If this integration work goes to plan, it is hoped that it will be possible to progress with the
development of the gadget specifications. This will involve mapping the gadgets against our
online student personas which have been developed as a method to verify our developments
in addition to putting concepts through usability evaluation.
The aim is also to produce one or two prototype gadgets within this timeframe, to include
preliminary evaluation of end-users experience, principally through usability testing.
Page 4 of 16
Document title: JISC Project Plan
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
Phase II Development –May 2011 – Sept 2011
Phase II will focus on developing gadgets from the approved list along with the services in the
VLE that will provide information to them. Efforts will be concentrated on gadgets that are the
most feasible at this stage; either due to development effort required, maturity of specification
or availability of connecting VLE services.
Potential for further integration between the VLE (Moodle) and Google Apps will be explored
and any feasible developments undertaken.
There will also be the potential to continue development on features released in phase I due
to feedback received once they are available to users.
This phase of development will also involve evaluation of end user experience of the gadgets
and features developed during the project to date.
Phase III Development – Aug 2011 – Dec 2011
Phase III development will focus on the continuing development of gadgets (and their
associated services) from the approved list. There will also be investigation and development
using features developed in the project in at least one alternate platform, e.g., Facebook or
W3C Widgets.
This phase of development will also involve comprehensive evaluation of end user experience
of the gadgets.
List of developments
1.
2.
3.
4.
5.
6.
7.
8.
Moodle plugin to allow OpenSocial Gadgets to access Moodle web-services.
JavaScript library to assist with gadget connection to Moodle plugin.
Moodle plugin to allow users to export course event information into Google calendar.
Code library to interface with Google Apps/Docs API.
Moodle module that initiates collaboration on Google documents.
Google gadgets.
Web-services etc in Moodle to support gadget requirements.
Migration of gadget to alternate platform.
Page 5 of 16
Document title: JISC Project Plan
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
Development and testing plan
A usability and accessibility testing plan and guidance has been produced as part of the workpackages as outlined below.
A. Work Packages
WORKPACKAGES
1: Organisation
1.1 Develop detailed project plan
1.2 Setup website
1.3 Finalise external contract
1.4 Setup Steering Group
1.5 Steering Group meetings
1.6 JISC Project Reports
1.7 Project Progress Monitoring and Reporting
1.8 Dissemination event to JISC community
1.9 JISC Final Project Reports
2: Vision
2.1 Undertake Desk research
2.2 Develop User scenarios
2.3 Technical investigation
2.4 Usability research
2.5 Prototype development + user testing
2.6 Produce Development Plan
2.7 Preparatory development
2.8 Staff workshop
Page 6 of 16
Document title: JISC Project Plan
Month
1
07
2
08
3
09
4
10
5
11
6
12
7
01
8
02
9
03
10
04
11
05
12
06
13
07
14
08
15
09
16
10
17
11
18
12
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
WORKPACKAGES
3: Development 1
3.1 Software development
3.2 Usability testing
3.3 Software testing + release
3.4 Documentation
4: Development 2
4.1 Review
4.2 Software development
4.3 Usability testing
4.4 Software testing + release
4.5 Documentation
5: Development 3
5.1 Review
5.2 Software development
5.3 Usability testing
5.4 Software testing + release
5.5 Documentation
Project start date: 01/07/2010
Project completion date: 31/12/2011
Duration: 18 months
Page 7 of 16
Document title: JISC Project Plan
Month
1
07
2
08
3
09
4
10
5
11
6
12
7
01
8
02
9
03
10
04
11
05
12
06
13
07
14
08
15
09
16
10
17
11
18
12
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
Workpackage and activity
WORKPACKAGE 1: Organisation
Earliest
start
date
Latest
completion
date
July 2010
Dec 2011
Disseminate the project outputs and outcomes
to the JISC and the wider education community.
1.1 Develop detailed project plan
July 2010
July 2010
1.2 Setup website
July 2010
July 2010
1.3 Finalise external contract
1.4 Setup Steering Group
July 2010
July 2010
July 2010
July 2010
1.5 Steering Group meetings
1.6 JISC Project Reports
July 2010
Jan 2011
June 2011
Jul 2010
Nov 2011
Nov 2011
Dec 2011
Jan 2011
June 2011
Dec 2011
Nov 2011
Dec 2011
Outputs
(clearly indicate deliverables &
reports in bold)
Milestone
Responsibility
Objectives: Project Management, planning and
progress reporting.
1.7 Project Progress Monitoring and Reporting
1.8 Dissemination event to JISC community
1.9 JISC Final Project Reports
Page 8 of 16
Document title: JISC Project Plan
Project Plan (including an evaluation
plan, QA plan, Dissemination Plan,
Exit/Sustainability Plan, Workpackage
details and Budget) submitted in early
August 2010.
Tasks to be continually reviewed and
up-dated throughout the project.
JISC Website Template submitted
Project Website setup and populated
with project details. Editing permission
assigned to relevant members of project
team.
Contracts signed
Initial Steering Group Meeting.
Agreement on frequency of following
meetings.
Steering Group meetings take place.
1st Project report
2nd Project report
Frequent project meetings.
Organise/attend event.
Final Report submitted to JISC (draft
submitted 1 month before end date).
Completion Report submitted to JISC.
1
PM
PM
PM
PM + NS
PM + NS
PM
6
PM
PM
PM
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
Workpackage and activity
WORKPACKAGE 2: Vision
Earliest
start
date
Aug 2010
Latest
completion
date
Dec 2010
Aug 2010
Oct 2010
Outputs
(clearly indicate deliverables &
reports in bold)
Milestone
Responsibility
Objectives:
Explore opportunities for integration between
OU learning systems and Google Apps with a
view to creating an e-portfolio solution
Identify key areas of existing functionality in OU
learning systems that could utilise a distributed
approach and assess the impact of this
approach on end-users
Identify features in the learning systems
roadmap that could utilise a distributed
approach and assess the impact of this
approach on end-users
Evaluate students, staff and other end-users
experience of the solution, assessing usability
and impact.
1.1 Undertake Desk research
Investigation into: potential uses of distributed
learning systems, other institutions use of
distributed learning, internal developments in this
area.
2.2 Develop User scenarios
Aug 2010
Mid Nov 2010
2.3 Technical investigation
Aug 2010
Mid Nov 2010
Page 9 of 16
Document title: JISC Project Plan
Report on key functions, roles,
activities and ICT at the OU.
NS + PM
Report on investigation into distributed
learning systems.
Personas and user scenarios updated
to reflect outcomes from 2.1.
Dependencies: 2.1
Technical Model - report on possible
technical approaches and potential
CJ
JP
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
issues.
2.4 Usability research
Sep 2010
Mid Nov 2010
2.5 Prototype development + user testing
Mid Nov
2010
Mid Dec 2010
2.6 Produce Development Plan
Dec 2010
Jan 2011
2.7 Preparatory development
Sep 2010
Jan 2011
2.8 Staff workshop
Dec 2010
Dec 2010
Page 10 of 16
Document title: JISC Project Plan
Usability/accessibility plan.
Sessions with end-users scheduled.
Prototype for user testing and
evaluation.
Dependencies: 2.1, 2.2, 2.3, 2.4
Report on vision for future learning
systems – based on outcomes from
2.1-2.5.
Development Plan (based on Report on
vision for future learning systems) – List
of developments that will be undertaken
in Phase 1 & 2.
Dependencies: 2.1, 2.2, 2.3, 2.4, 2.5
Development of systems in preparation
for following phases.
Staff workshop organised.
Actions/Notes from workshop.
CJ, AJ, CC
JP
2
PM
JP
PM
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
Workpackage and activity
Earliest
start
date
Jan 2011
Latest
completion
date
June 2011
Outputs
(clearly indicate deliverables & reports
in bold)
Evaluate students, staff and other end-users
experience of the solution, assessing usability
and impact
3.1 Software development
Jan 2011
April 2011
Development of services and applications
identified in development plan.
3.2 Usability testing
Jan 2011
June 2011
3.3 Software testing + release
April 2011
June 2011
3.4 Documentation
April 2011
June 2011
WORKPACKAGE 3: Development 1
Milestone
Responsibility
Objectives: Develop, test and release services
within OU learning systems to provide data to
external systems
Develop, test and release standards-compliant
applications for third-party platforms that interface
with OU learning systems
Dependencies: 2.6
Monthly sessions with end users.
Outcomes reported to project team.
Issue log from result of functional,
usability and accessibility testing.
Updated software ready for release.
Release of Widgets into OU system and
made available to community.
Dependencies: 3.1
Documentation (testing, end-user and
developer) to accompany software
release.
Dependencies: 3.3
Page 11 of 16
Document title: JISC Project Plan
JP
CJ, AJ
3
JP, CC
JP
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
Workpackage and activity
Earliest
start
date
May 2011
Latest
completion
date
Sep 2011
Outputs
(clearly indicate deliverables & reports
in bold)
Evaluate students, staff and other end-users
experience of the solution, assessing usability
and impact
4.1 Review
May 2011
June 2011
4.2 Software development
May 2011
July 2011
Review of Development 1 work.
Update of Development plan.
Development of services and applications
identified in development plan.
4.3 Usability testing
July 2011
Sep 2011
4.4 Software testing + release
July 2011
Sep 2011
4.5 Documentation
July 2011
Sep 2011
WORKPACKAGE 4: Development 2
Milestone
Responsibility
Objectives: Develop, test and release services
within OU learning systems to provide data to
external systems
Develop, test and release standards-compliant
applications for third-party platforms that interface
with OU learning systems
Page 12 of 16
Document title: JISC Project Plan
Dependencies: 2.6, 4.1
Monthly sessions with end users.
Outcomes reported to project team.
Issue log from result of functional,
usability and accessibility testing.
Updated software ready for release.
Release of Widgets into OU system and
made available to community.
Dependencies: 4.2
Documentation (testing, end-user and
developer) to accompany software
release.
Dependencies: 4.4
PM
JP
CJ, AJ
4
JP, CC
JP
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
Workpackage and activity
Earliest
start
date
Aug 2011
Latest
completion
date
Dec 2011
Outputs
(clearly indicate deliverables & reports
in bold)
Evaluate students, staff and other end-users
experience of the solution, assessing usability
and impact
5.1 Review
Aug 2011
Sep 2011
5.2 Software development
July 2011
Oct 2011
Review of Development 2 work.
Update of Development plan.
Development of services and applications
identified in development plan.
5.3 Usability testing
Oct 2011
Dec 2011
5.4 Software testing + release
Oct 2011
Dec 2011
5.5 Documentation
Oct 2011
Dec 2011
WORKPACKAGE 5: Development 3
Milestone
Responsibility
Objectives: Develop, test and release services
within OU learning systems to provide data to
external systems
Develop, test and release standards-compliant
applications for third-party platforms that interface
with OU learning systems
Page 13 of 16
Document title: JISC Project Plan
Dependencies: 2.6, 5.1
Monthly sessions with end users.
Outcomes reported to project team.
Issue log from result of functional,
usability and accessibility testing.
Updated software ready for release.
Release of Widgets into OU system and
made available to community.
Dependencies: 5.2
Documentation (testing, end-user and
developer) to accompany software
release.
Dependencies: 5.4
PM
JP
CJ, AJ
4
JP, CC
JP
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
Page 14 of 16
Document title: JISC Project Plan
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
Risks, Issues and Dependencies
Risk
Probability
(1-5)
Severity
(1-5)
Score
(P x S)
2
3
6
Lack of feedback on the
solution before the end of
the project
Parallel developments alter
in scope or are delayed
1
4
4
3
3
9
IT are unable to get staff
and tutors into Google
(other than manual set-up)
2
4
8
Delayed decision making
with regard to Google
calendar integration (impact
on Moodle calendar), delays
DOULS progress
Members of the module
team or tutors are unable to
access the functional
account preventing them
from setting up Google
collaborative activities
2
3
6
Press for resolution. Supply
deadline and make stakeholders
aware of dependencies and
implications.
5
1
5
Consider the use of alternatives to
module functional accounts.
Googles continual update of
the systems and features
means that changes occur
with little warning and no
version control, leading to
outdated guidance and
support documentation and
incompatibility with OU
systems and processes.
Google goes offline
Failure of single sign-on link
to sign into Google account
from OU, leading to no
direct access to Google.
4
2
8
Manage relationship with Google to
provide as much notice as possible
of changes. Advise module teams
not to embed guidance within
module materials.
1
2
4
4
4
8
Protected by 99.9% uptime
Alternate access route to be
available.
2
2
4
4
2
8
Keep up to date with information
on platforms throughout the whole
project.
Promote these gadgets as
‘experimental’, ‘pilots’ and ‘optional
for study’. Partner with Google (in
first instance) to tackle accessibility
barriers of platform.
Technical
Development delays
Legal
Changes to terms and
conditions of external
platforms (inc Google Apps)
Lack of accessibility of
gadgets developed or
platforms used for
deployment prevents full
development exploitation
Page 15 of 16
Document title: JISC Project Plan
Action to Prevent/Manage Risk
Ensure experienced staff and
robust project management in
place
Iterative prototyping, testing and
reviewing will be scheduled into the
plan.
Ensure close collaboration
between projects and address
issues at an early stage.
Moodle VLE activity module and
Google Collaborative Activity will
need to be rolled out on a pilot
basis until staff can be added to
the system automatically.
Project Acronym: DOULS
Version: 0.3
Contact: Judith Pickering
Date: 07/12/2010
Gadget specific risks
Study Buddy development
is dependent upon
consultation outcomes from
personalisation strand of
VLE development project
Development of module
suggestion gadget is
dependent upon other parts
of the university supplying
the data we need
1
2
2
Liaise closely with personalisation
strand.
5
5
25
Suggest that the development is
owned by another group, e.g.,
Marketing and they develop the
back end leaving DOULS to supply
the gadget expertise. Make links
with the Lucero project.
1
3
3
Lack of students for usability
testing
3
4
12
Lack of access to
accessibility testing experts
3
4
12
Formulate consultation plan,
Identify key stakeholders, map
requirements against personas,
undertake usability and
accessibility testing at multiple
stages including the concept
phase.
Produce usability and accessibility
testing plan. Flag need for testing
as early as possible. Consider
alternatives to traditional face to
face testing. Map against
personas.
Look to engage freelance testers
and contract them on small tasks
as soon as possible to reduce time
to familiarise themselves with
project requirements.
Project Management
Unable to capture
accurately all stakeholders
needs during requirements
assessment.
Page 16 of 16
Document title: JISC Project Plan