Managing Inquiry-based Learning: Learning from experience
•Télécharger en tant que PPT, PDF•
1 j'aime•453 vues
We have taught a suite of inquiry-based learning modules for the past 20 years. Two problems that have occurred frequently are that the students can be poor at organising their schedules and setting deadlines, whilst at the same time we have moved towards marking schemes which are focused on process applied rather than product produced. These two factors have mandated that the students need to provide evidence that they are planning and following the process that has been set. To support this we have introduced a suite of custom support software.
![Teaching Overview ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
Similaire à Managing Inquiry-based Learning: Learning from experience
Similaire à Managing Inquiry-based Learning: Learning from experience (20)
Plus de cilass.slideshare
Plus de cilass.slideshare (20)
Dernier
Dernier (20)
Managing Inquiry-based Learning: Learning from experience
- 1. C.D. Thomson, A. Corbett, M. Holcombe University of Sheffield, Department of Computer Science and the Institute of Work Psychology This work was supported by an EPSRC grant: EP/D031516 – the Sheffield Software Engineering Observatory.
- 4. Week Date Deliverable Items 1 14-15/2 THURSDAY – initial briefing and lecture on XP, FRIDAY – meeting clients 2 21-22/2 THURSDAY – lecture on Unit tests, FRIDAY – Management meeting 3 28-29/2 THURSDAY – lecture on System testing and modelling, FRIDAY - Release 1: Demo to client and manager. Place code and binary in release directory . 4 26/2 THURSDAY – lecture on how to package and deliver software, FRIDAY – Management and client meeting – deliver requirements document 5 13-14/3 THURSDAY – lecture on debugging, refactoring, library development, Place code and binary in release directory. FRIDAY – Management and client meeting Easter 16/3-7/4 6 10-11/4 THURSDAY – lecture and XP review, FRIDAY – Management and client meeting 7 17-18/4 FRIDAY - Release 3: Demo to client and manager. Place code and binary in release directory. 8 24-25/4 FRIDAY – Management meeting 9 1-2/5 FRIDAY - Release 4: Demo to client and manager. Place code and binary in release directory. 10 8-9/5 FRIDAY – Extensive systems testing and Demonstration to client. 11 15-16/5 MONDAY – Final release to client. Please hand in a CD and printed documentation to be set to the client, via reception. WEDNESDAY – QA exercise email to Mike and the other team. 12 22-23/5 MONDAY – Final release and QA hand in, to be checked by the managers, place in team directory. (NB you may correct any errors found by the client or after the QA exercise). FRIDAY – Poster presentations in the Lewin Lab and Personal Evaluations via reception (posters also from Crossover and Genesys teams – external visitors will be present..
- 6. Timeline Crossover Software Hut Genesys 2004 2002 2003 2001 2005 2006 2007 2008 Current management tool introduced Linked wiki First wiki Web management tool Formalised templates Test server
- 16. Figure 2: Software Hut 2003-4 usage. Figure 1: Software Hut 2004-5 usage.
- 21. Tool screens
- 22. Tool screens
- 23. Tool screens
- 24. Useage Data Figure 3. Software Hut 2007-8 Figure 3. Software Hut 2006-7 Week Week Number of hits Number of hits
- 31. Wiki useage (modify) Week (2007-8) Number of modifications
- 32. Wiki screens