At our last e-Learning Symposium in May 2008 we decided to continue and extend this blog to incorporate e-learning and technology development at DMU. In that spirit we have now finally migrated the DMU Pathfinder blog [located here] to a new site called DMU Learning Exchanges, which will incorporate a blog, with reports on projects and faculty developments, as well as help and guidance for staff and students.
As a result there will be no further extensions or postings to this blog. We'd like to thank you for reading and hope that you pop over to DMU Learning Exchanges to find out what we are up to going forward.
Showing posts with label DMU. Show all posts
Showing posts with label DMU. Show all posts
Wednesday, 28 January 2009
Thursday, 27 September 2007
Project meeting: 25 September 2007
So we met yesterday to let the teams catch-up on each others' work-packages. The progress reports have now all been posted on our Blackboard-based Wiki. Team members who weren't there should read the reports. We are also using the Wiki for conference reports and to flag relevant project outcomes and issues.
Work-package headlines from yesterday are as follows:
1. WP1: There are issues of maintaining momentum with PG Cert HE staff who are planning to teach and actually teaching. The assessment for the PG Cert students has been revamped to include e-learning. The June group are editing action plans and we need now to offer them follow-up sessions. [Action: HC and RH]
2. WP1/WP6: Steve Mackenzie is delivering some synchronous development sessions on pedagogical and technological issues with members of the PG Cert HE and Faculty of HLS. We will evaluate this approach to test its sustainability. Library front-desk staff may also benefit from this approach, as their shift-work impacts upon access to professional development. [Action: SM and AB]
3. WP3: There are issues of maintaining momentum with Library staff who are thinking about using Web 2.0 approaches in their work. We intend to offer developmental sessions, linked to staff development reviews. [Action: AB] We also intend to review the ISAS approach to using Wikis as knowledge bases [Action: RH] The team also intend to review the non-technical issues around the conversion of extant support and training materials for a Web 2.0 age. [Action: JT, MYK and AB]
4. WP4: the iTunes issue for catching and feeding Blackboard-hosted podcasts t users has been resolved, so that the podcast tool now works with iTunes. A key issue is the apparent reticence of users to be recorded for the production of webcasts. We have feedback to suggest that some users do not like hearing or seeing themselves on-line, or committing to this type of “publication”. This is a potential issue that will require intervention with specific teaching teams in order to build effective local, coping strategies. Initial evidence suggests that few students use or subscribe to podcasts, so there may be a cultural issue for staff teams. The third issue arising is the support we can offer staff in answering the question of streaming vs podcasting.
5. WP5: case studies will be produced for AAD, BAL, Hums and Library in the use of tools to support first-years in student-student communication. [Action: HC to talk to Jo Leese in DSU re: student reps' experiences of tools like Facebook]
6. WP6: Our Second Life Island has been purchased and activated, and staff who registered an interest have been invited in. Twelve staff are registered so far, and a user group has been formed. A building party is being held on 15 October. Subsequent staff development events will be planned and delivered by the user-group. A meeting was held with Howard Rheingold in the IOCT in September to discuss ways forward with SL. We intend to use his videos to prime some of our developments. Steve Mackenzie is delivering some synchronous development sessions. We will evaluate this approach to test its sustainability. The DMU e-Learning Pathfinder team have a Facebook group. There is no protocol for its use, but its development will be mapped as a project management and dissemination tool.
7. WP7: RH has been in contact with NIACE about the publication of the project’s findings. [Action: RH to meet with JC re: conference]
See also: http://www.pageflakes.com/dmupathfinder
Matters arising:
Work-package headlines from yesterday are as follows:
1. WP1: There are issues of maintaining momentum with PG Cert HE staff who are planning to teach and actually teaching. The assessment for the PG Cert students has been revamped to include e-learning. The June group are editing action plans and we need now to offer them follow-up sessions. [Action: HC and RH]
2. WP1/WP6: Steve Mackenzie is delivering some synchronous development sessions on pedagogical and technological issues with members of the PG Cert HE and Faculty of HLS. We will evaluate this approach to test its sustainability. Library front-desk staff may also benefit from this approach, as their shift-work impacts upon access to professional development. [Action: SM and AB]
3. WP3: There are issues of maintaining momentum with Library staff who are thinking about using Web 2.0 approaches in their work. We intend to offer developmental sessions, linked to staff development reviews. [Action: AB] We also intend to review the ISAS approach to using Wikis as knowledge bases [Action: RH] The team also intend to review the non-technical issues around the conversion of extant support and training materials for a Web 2.0 age. [Action: JT, MYK and AB]
4. WP4: the iTunes issue for catching and feeding Blackboard-hosted podcasts t users has been resolved, so that the podcast tool now works with iTunes. A key issue is the apparent reticence of users to be recorded for the production of webcasts. We have feedback to suggest that some users do not like hearing or seeing themselves on-line, or committing to this type of “publication”. This is a potential issue that will require intervention with specific teaching teams in order to build effective local, coping strategies.
5. WP5: case studies will be produced for AAD, BAL, Hums and Library in the use of tools to support first-years in student-student communication. [Action: HC to talk to Jo Leese in DSU re: student reps' experiences of tools like Facebook]
6. WP6: Our Second Life Island has been purchased and activated, and staff who registered an interest have been invited in. Twelve staff are registered so far, and a user group has been formed. A building party is being held on 15 October. Subsequent staff development events will be planned and delivered by the user-group. A meeting was held with Howard Rheingold in the IOCT in September to discuss ways forward with SL. We intend to use his videos to prime some of our developments. Steve Mackenzie is delivering some synchronous development sessions. We will evaluate this approach to test its sustainability. The DMU e-Learning Pathfinder team have a Facebook group. There is no protocol for its use, but its development will be mapped as a project management and dissemination tool.
7. WP7: RH has been in contact with NIACE about the publication of the project’s findings. [Action: RH to meet with JC re: conference]
See also: http://www.pageflakes.com/dmupathfinder
Matters arising:
- headsets and webcams for all team members;
- monies to be re-charged this week with covering letters to budget holders; and
- access to iTunes for all team members.
Labels:
DMU,
Pathfinder,
project management,
workpackage
Wednesday, 6 June 2007
We're up
Okay folks, here we go. There will be cricket-based nonsense again in this blog, especially in-light of the Vaughan-Flintoff-fredalo incident and its implications for team-play/-work/-liness.
Anyway, our Pathfinder has no name. I think we need one. Email rhall1@dmu.ac.uk with suggestions based upon our 5 aims:
1. To build enhanced institutional knowledge of both Web 2.0 technologies and developmental strategies that support pedagogic and epistemological participation. [c.f. HEFCE e-Learning Strategy Measures of Success 1, 3, 4 and 8; Strands 1.1, 1.4, 1.5, 2.1, 3.1 and 4.4]
2. To implement professional development strategies for staff in Human Resources, Information Systems and Services (ISAS), and Library Services, for the integration of institutional and non-institutional virtual spaces. [c.f. HEFCE e-Learning Strategy Measures of Success 1, 6 and 8; Strands 1.1, 1.5, 3.1, 4.3 and 4.4.]
3. To deliver differentiated strategies for extending virtual spaces through social networks and user-generated content that are aligned with our e-learning networks, in order to deliver improved retention and progression. [c.f. HEFCE e-Learning Strategy Measures of Success 1 and 3; Strands 1.2, 2.1 and 3.1.]
4. To scope professional development methodologies that utilise Web2.0 technologies. [c.f. HEFCE e-Learning Strategy Measure of Success 8; Strands 1.1, 1.4 and 2.3.]
5. To create social networking links with other project teams and experts, in order to build capacity for innovative e-learning within the sector. [c.f. HEFCE e-Learning Strategy Measure of Success 5; Strands 2.3, 4.1, 6.1 and 6.2.]
We have a Project Plan, emailed off to the HEA/Glenaffric, and our first team meeting has lead to the formation of 7 work-packages with teams assigned to th production of each: deadline 22 June @ high noon. Management-by-exception and clear reporting are key for us. Essentially this means that once we agree the criteria for the work to be done, then teams take responsibility for production of relevant work-packages. Unless there are problems with scope, quality, time-scales or resources, teams have the ability to make decisions without referring to theProject Manager [me]. We will require monthly highlight reports about progress, which should be uploaded onto the project Wiki, alongside final reports etc.. If there are problems with scope, quality, time-scales or resources, which affect the workpackage then an exception report will be needed so that we can agree a contingency with the HEA.
Our Project Board will be a sub-committee of the University Learning and Teaching Committee, who will be responsible for endorsing the project, and advising on and approving progress. This group will receive termly highlight reports from the Project Manager, and will be a key vehicle for monitoring and disseminating project outputs within and without of the institution. It will meet for the first time in the next few weeks.
Don't forget that name!
Anyway, our Pathfinder has no name. I think we need one. Email rhall1@dmu.ac.uk with suggestions based upon our 5 aims:
1. To build enhanced institutional knowledge of both Web 2.0 technologies and developmental strategies that support pedagogic and epistemological participation. [c.f. HEFCE e-Learning Strategy Measures of Success 1, 3, 4 and 8; Strands 1.1, 1.4, 1.5, 2.1, 3.1 and 4.4]
2. To implement professional development strategies for staff in Human Resources, Information Systems and Services (ISAS), and Library Services, for the integration of institutional and non-institutional virtual spaces. [c.f. HEFCE e-Learning Strategy Measures of Success 1, 6 and 8; Strands 1.1, 1.5, 3.1, 4.3 and 4.4.]
3. To deliver differentiated strategies for extending virtual spaces through social networks and user-generated content that are aligned with our e-learning networks, in order to deliver improved retention and progression. [c.f. HEFCE e-Learning Strategy Measures of Success 1 and 3; Strands 1.2, 2.1 and 3.1.]
4. To scope professional development methodologies that utilise Web2.0 technologies. [c.f. HEFCE e-Learning Strategy Measure of Success 8; Strands 1.1, 1.4 and 2.3.]
5. To create social networking links with other project teams and experts, in order to build capacity for innovative e-learning within the sector. [c.f. HEFCE e-Learning Strategy Measure of Success 5; Strands 2.3, 4.1, 6.1 and 6.2.]
We have a Project Plan, emailed off to the HEA/Glenaffric, and our first team meeting has lead to the formation of 7 work-packages with teams assigned to th production of each: deadline 22 June @ high noon. Management-by-exception and clear reporting are key for us. Essentially this means that once we agree the criteria for the work to be done, then teams take responsibility for production of relevant work-packages. Unless there are problems with scope, quality, time-scales or resources, teams have the ability to make decisions without referring to theProject Manager [me]. We will require monthly highlight reports about progress, which should be uploaded onto the project Wiki, alongside final reports etc.. If there are problems with scope, quality, time-scales or resources, which affect the workpackage then an exception report will be needed so that we can agree a contingency with the HEA.
Our Project Board will be a sub-committee of the University Learning and Teaching Committee, who will be responsible for endorsing the project, and advising on and approving progress. This group will receive termly highlight reports from the Project Manager, and will be a key vehicle for monitoring and disseminating project outputs within and without of the institution. It will meet for the first time in the next few weeks.
Don't forget that name!
Subscribe to:
Posts (Atom)