Impact
With regard to the choice of an Open Source environment for their VLE, the University had tried different systems, of which Moodle simply appeared as the best choice for the OU. Admittedly the system still required a large number of of modifications, improvements, and additions, but today the system fulfils the OU's requirements. “The fundamental point is that we have a working Virtual Learning Environment that is scalable, robust and feature rich and that is being used increasingly in our courses†highlights Niall Slater, director of Learning Innovations at the OU. Even though some people would have liked to see a dedicated commercial support partner in this process, the team in charge of the VLE quickly realized that the best source of expertise is freely reachable through the Moodle community. The invaluable feedback that they get for code contributions in the form of new developments or enhancements, through bug reports and discussions has become essential to the work on the OU's VLE. The altruistic approach clearly is a welcome addition to this, as not only the OU can benefit from this large project, but also any other Moodle users world wide. The reasons for this give-and-take relationship are thus of a mutual benefit, which is an important backbone of the Moodle community.
Track record of sharing
For the development of the Moodle VLE, the OU saw little need for direct cooperation with other universities, given that each university has different requirements and specific needs. What was right for the OU in this respect, may not not been the best solution for another university. The most important source of information and cooperation for the OU therefore was the Moodle community itself. As Niall Sclater illustrates: “What we've found is that with Moodle, we're part of the world wide community, and that's really the best forum for collaboration and development.†This means that you can get almost instant feedback for any development that you publish, and you may find answers for anything that you might want to develop. And by having a large user base, which Moodle certainly has with roughly 28 million users and 2,8 million courses, most bugs and glitches are found very quickly. Responding to the question if the University has a concrete partner university, or outside support company somewhere in the UK or Europe, Sclater says: “It wouldn't make sense to restrict it to the UK or Europe. You're not getting all the expertise that's around.†With regard to the code contributions, the OU uploads most developments to the community that they consider ready for a wide use. As mentioned earlier, this is very important for the community and the OU alike, given that both benefit greatly from this. Through the forums and discussion boards, the OU can learn about shortcomings of their development and improve them accordingly.
Lessons learnt
Especially in the early phase of the project, the OU however also faced several barriers to which solutions had to be found. Sclater mentions a few points, which he has also described in a book chapter on strategic IT management of learning institutions (Sclater, 2008): – Lack of awareness – Lack of incentives – Concern to avoid alienating students – Risk aversion These are just a few key points. From a technical perspective, the choice of Moodle as the OU's VLE shows how Open Source products can be well capable of competing with proprietary solutions. It was and is seen as the best available solution that would meet the OU's demands on stability, flexibility, scalability, and also very important: support. Compared to commercial software deployments, Moodle does not rely on one support partner, but features a community of users world wide. With more than 2,5 million registered courses and roughly 28 million users, this is a substantial source of feedback and information, which is invaluable to the work of the OU. By contributing to this community with their own developments, they create a win-win situation, as their tools improve with all the feedback and assistance, and all others users benefit from the additional functionalities added by the OU. With regard to change management, the OU's case shows that the real costs of introducing a new system do not trace back only to software licenses, development work or hardware acquisitions, but also to the change management. The OU's case confirms once again that old habits have to be broken and resistance to be overcome, which in the case of the OU was done as a step-by-step approach, with guidance of every step that helped fundamentally in creating acceptance and understanding.
Showing 2 comments
Muy interesante
Que lastima que sea un poco tarde apra mi.