Agile Research for Open Education Researchers
•Als PPTX, PDF herunterladen•
1 gefällt mir•959 views
Taking lessons from Agile Programming/eXtreme Programming into how we do research. From deliverables and meetings to sprints and scrums. Based on version presented at Open University CALRG conference 11 June 2013. CC-BY
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Agile Research for Open Education Researchers
Ähnlich wie Agile Research for Open Education Researchers (20)
Mehr von Patrick McAndrew
Mehr von Patrick McAndrew (19)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Agile Research for Open Education Researchers
- 1. www.open.ac.uk Professor Patrick McAndrew Institute of Educational Technology The Open University @openpad Becoming more agile researchers: Experiences from researching Open Education Resources
- 3. Opening up The Open University's Institute of Educational Technology
- 4. Opening up The Open University's Institute of Educational Technology
- 5. Opening up The Open University's Institute of Educational Technology
- 9. Shared knowledge Peer researchers Individual Research team Peer approval Scientific behaviour Studies Desk research Research instruments Researcher Community Division of labourRules Subject Object Tools Impact Policy makers Funders Practicitioners
- 10. Research 2.0βeta (Based on O’Reilly Web 2.0) 1. Study the interesting things that happen 2. Look for patterns that can apply more widely 3. Encourage all to be part of the experiment 4. Build valuable activities that give data 5. Recognise openness has a lot of benefits 6. Draw conclusions while wanting more data 7. Be prepared for the user that arrives anywhere 8. Realise there is no way to control all access McAndrew, P., Godwin, S., & Santos, A. (2009). Research 2.0: How do we know about the users that do not tell us anything? http://oro.open.ac.uk/23854/
- 11. Research 2.0βeta (Based on O’Reilly Web 2.0) 1. Study the interesting things that happen 2. Look for patterns that can apply more widely 3. Encourage all to be part of the experiment 4. Build valuable activities that give data 5. Recognise openness has a lot of benefits 6. Draw conclusions while wanting more data 7. Be prepared for the user that arrives anywhere 8. Realise there is no way to control all access McAndrew, P., Godwin, S., & Santos, A. (2009). Research 2.0: How do we know about the users that do not tell us anything? http://oro.open.ac.uk/23854/
- 14. The Open University's Institute of Educational Technology
- 15. 06/17/10
- 16. 06/17/10 a. Use of OER leads to improvement in student performance and satisfaction. b. The open aspect of OER creates different usage and adoption patterns than other online resources c. Open education models lead to more equitable access to education, serving a broader base of learners than traditional education. d. Use of OER is an effective method for improving retention for at-risk students. e. Use of OER leads to critical reflection by educators, with evidence of improvement in their practice f. OER adoption at an institutional level leads to financial benefits for students and/or institutions. g. Informal learners use a variety of indicators when selecting OER. h. Informal learners adopt a variety of techniques to compensate for the lack of formal support, which can be supported in open courses. i. Open education acts as a bridge to formal education, and is complementary, not competitive, with it. j. Participation in OER pilots and programs leads to policy change at institutional level. k. Informal means of assessment are motivators to learning with OER
- 17. Working with… •Open Courseware Library •CCCOER •+++ •School of Open •Bridge to Success •+++ •Flipped classroom •Gulf of Maine Institute •+++ • Connexions/Open University • TESS India • +++ Higher Education Schools (K- 12) Community Colleges Informal learning 17
- 20. 06/17/10
- 21. Agile Research
- 22. Agile Research
- 23. Agile Research
- 24. Agile Development/ (eXtreme Programming) Product Backlog Sprints Scrums Timebox Burndown Velocity
- 25. 06/17/10 Task size bingo Sprint velocity Product vision Sprint review Daily scrum Sprint backlog Agile in action Thanks to FutureLearn programming team May 2013
- 26. Becoming agile • Sprinting towards year 1 • Scrumming together • Tracking our velocity • Flexing as we reflect
- 28. Deliverable -> Sprint backlog 06/17/10
- 29. 06/17/10
- 31. 06/17/10
- 32. 06/17/10
- 33. 06/17/10
- 35. 06/17/10
- 36. 06/17/10
- 38. Patrick McAndrew Institute of Educational Technology www.open.ac.uk/iet @openpad Patrick.McAndrew@open.ac.uk
Hinweis der Redaktion
- Study the interesting things that happen: For researchers we need to spot the interesting and unpredictable in the unexpected actions of individuals as well as considering the mass actions at scale. Spotting the interesting behaviours of “lead users (Von Hippel, 2005) can help identify emergent ideas.Look for patterns that can apply more widely: Draw out patterns looking for shared characteristics and be open to signs of clustering behaviour by examining individual cases and see trends that can benefit others.Encourage all to be part of the experiment: Extending an invitation to all involved, end-users and producers, helps to maximise the value in experiments and bring out routes to extra information.Build valuable activities that give data: Activities that provide authentic outputs, especially if they are digital, mean that there is less need to request data solely for research purposes. For example, reflective logs help the learner but can also provide insight to the researcher and badges (Knight & Casilli, 2012) that encourage progress can also help track the overall performance of learners.Recognise openness has a lot of benefits: Openness encourages transfer between systems, provides the chance for early discussion, and expands dissemination.Draw conclusions though you wish you had more data: No computer system is ever completely finished or perfect, rather it is always a beta release that can be refined. Similarly no research project ever has all the data and can be sure of the results, but to be of value indicative results need to be available in early forms. This challenges the peer review process.Be prepared for the user that arrives anywhere: In researching openness it is important to recognise the reduced control inherent in the design. Data gathering that depends on users reading advice or passing through other points (e.g. logins) will not work in all circumstances.Realise there is no way to control all access: Openness allows transfer so it is likely that at some point there will be activity that we know nothing about. As researchers we must therefore operate with incomplete data, and partial knowledge in particular where information can travel from site to site. Table 1: Principles for Research 2.0 (modified from (McAndrew et al., 2009))
- Study the interesting things that happen: For researchers we need to spot the interesting and unpredictable in the unexpected actions of individuals as well as considering the mass actions at scale. Spotting the interesting behaviours of “lead users (Von Hippel, 2005) can help identify emergent ideas.Look for patterns that can apply more widely: Draw out patterns looking for shared characteristics and be open to signs of clustering behaviour by examining individual cases and see trends that can benefit others.Encourage all to be part of the experiment: Extending an invitation to all involved, end-users and producers, helps to maximise the value in experiments and bring out routes to extra information.Build valuable activities that give data: Activities that provide authentic outputs, especially if they are digital, mean that there is less need to request data solely for research purposes. For example, reflective logs help the learner but can also provide insight to the researcher and badges (Knight & Casilli, 2012) that encourage progress can also help track the overall performance of learners.Recognise openness has a lot of benefits: Openness encourages transfer between systems, provides the chance for early discussion, and expands dissemination.Draw conclusions though you wish you had more data: No computer system is ever completely finished or perfect, rather it is always a beta release that can be refined. Similarly no research project ever has all the data and can be sure of the results, but to be of value indicative results need to be available in early forms. This challenges the peer review process.Be prepared for the user that arrives anywhere: In researching openness it is important to recognise the reduced control inherent in the design. Data gathering that depends on users reading advice or passing through other points (e.g. logins) will not work in all circumstances.Realise there is no way to control all access: Openness allows transfer so it is likely that at some point there will be activity that we know nothing about. As researchers we must therefore operate with incomplete data, and partial knowledge in particular where information can travel from site to site. Table 1: Principles for Research 2.0 (modified from (McAndrew et al., 2009))
- IET has specialist role in Accessibility. Module H810: Accessible Online Learning. Research – long history. Work on Standards, Personalisation.Practical support to improve accessibility – including specialist testing facilities.