1. We’re going to a New Version? Bill Marlow School of Business, IT & Management

2. Bio u At Durham 23 ½ years, mostly School of Business u “Real” IT faculty, currently teaching Programming languages, Systems Analysis, Databases, Project Management, etc.

3. Bio (cont.) u 23.5 years * 2 = 47 semesters, 4.5 courses per semester = 211 courses, changing to new version / new software 30% of the time = 63 software changes

4. What we’re Talking About u Versions of software u New software vs. new versions of software u Course / Program / School / College u Who this applies to…

5. Scope of Change u Course – 1-2 Courses, one faculty (that’s you!), one piece of software u Department – Multiple courses, multiple faculty, for example Program or School / Department size u College – Entire college

6. Course-Level Change Doing it all by yourself u High level of control over changes to be made & implemented u Few (or no ) other faculty to work with you u Few resources provided by College

7. School-Level Change Working with your peers u Some level of control over changes to be made & implemented u Some other faculty who are making similar change u Some resources may be available

8. College Level Change A time for visibility? u Very little control over changes to be made & implemented u Many other faculty to consult with u Resources likely available u Can you be a Trainer?

9. Control vs. Resources Resources Available

10. Resources u Software Developer u Textbook Publishers u Other faculty, perhaps from other colleges, who have used the software

11. Software Developer u Website (Forums, Online Courses, User Manuals, look for Support links) Website u “Summary of Change” Documentation u Sometimes lists of reference texts, new users, testimonials – available for contact?

12. Textbook Publishers u Textbooks & Instructor Resources (especially Problem Solutions) u Author / Reviewer Contact Info u Who else has requested this book?

13. Other Faculty u Others in your department / school? u Your IT or Training Dept. may have insight about others in your college u Publishers may know others who have done the same things you are doing

14. Other Faculty (cont.) u Software developer may know of other academic users u Conferences like this u You are probably not alone! u And if you are….

15. Tips & Traps…. u Software Acquisition u Get software as soon as you can – I try for the first week after term ends or sooner u Use a sample / trial version if you have to u Confirm versions once it is available on student laptops or lab room

16. Tips & Traps….(cont.) u SWF u Some deans (or other admin) will allocate extra prep time when changing versions u Probably will not put you into overtime, but at least an acknowledgment of extra effort

17. Tips & Traps….(cont.) u Is your homework done? u At a minimum you should do the first 2-3 lab assignments during May / June u USE the software for something u Avoid the “I know how to do this” attitude u Note carefully where you have issues

18. Tips & Traps….(cont.) u I Don’t Know u Students should know that this is a new version u Admit you don’t know everything about new version u It’s OK to say “I will find out”

19. Tips & Traps…. (cont.) u Support Staff & Admin. u Be aware of what faculty are doing u One note or link may be very significant

20. Tips & Traps…. (cont.) u Students u I do tell my students it’s new u Are other students affected? For example students who took the course previously? Is a plan required for them? u Remember what you had trouble with when doing lesson planning

21. Tips & Traps….(cont.) u Beta Versions of software u During the Term u Features of the new software – if you’re not using them why did you convert?

22. The Big Five Start as early as you can It’s worth the time to find help Volunteer to help others – you’ll learn too Use the software for yourself You have Time and you can Research – Use Your Existing Skills!

23. Contact Me…. Bill Marlow, School of Business, Durham College, 2000 Simcoe St. N., Oshawa, Ont., L1H 7L7 Bill.Marlow@durhamcollege.ca

24. Thank You!