we’re going to a new version?

We’re going to a New Version?

Bill MarlowSchool of Business, IT & Management

Bio

At Durham 23 ½ years, mostly School of Business

“Real” IT faculty, currently teaching Programming languages, Systems Analysis, Databases, Project Management, etc.

Bio (cont.)

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

What we’re Talking About

Versions of software New software vs. new versions of

software Course / Program / School / College Who this applies to…

Scope of Change

Course – 1-2 Courses, one faculty (that’s you!), one piece of software

Department – Multiple courses, multiple faculty, for example Program or School / Department size

College – Entire college

Course-Level ChangeDoing it all by yourself

High level of control over changes to be made & implemented

Few (or no ) other faculty to work with you

Few resources provided by College

School-Level ChangeWorking with your peers

Some level of control over changes to be made & implemented

Some other faculty who are making similar change

Some resources may be available

College Level ChangeA time for visibility?

Very little control over changes to be made & implemented

Many other faculty to consult with Resources likely available Can you be a Trainer?

Control vs. Resources

Level of Control

CourseDepartmentCollege

Resources

Available

Resources

Software Developer Textbook Publishers Other faculty, perhaps from other

colleges, who have used the software

Software Developer

Website (Forums, Online Courses, User Manuals, look for Support links)

“Summary of Change” Documentation

Sometimes lists of reference texts, new users, testimonials – available for contact?

Textbook Publishers

Textbooks & Instructor Resources (especially Problem Solutions)

Author / Reviewer Contact Info Who else has requested this book?

Other Faculty

Others in your department / school?

Your IT or Training Dept. may have insight about others in your college

Publishers may know others who have done the same things you are doing

Other Faculty (cont.)

Software developer may know of other academic users

Conferences like this You are probably not alone! And if you are….

Tips & Traps….

Software Acquisition Get software as soon as you can – I

try for the first week after term ends or sooner

Use a sample / trial version if you have to

Confirm versions once it is available on student laptops or lab room

Tips & Traps….(cont.)

SWF Some deans (or other admin) will

allocate extra prep time when changing versions

Probably will not put you into overtime, but at least an acknowledgment of extra effort

Tips & Traps….(cont.)

Is your homework done? At a minimum you should do the first

2-3 lab assignments during May / June USE the software for something Avoid the “I know how to do this”

attitude Note carefully where you have issues

Tips & Traps….(cont.)

I Don’t Know Students should know that this is a

new version Admit you don’t know everything

about new version It’s OK to say “I will find out”

Tips & Traps…. (cont.)

Support Staff & Admin. Be aware of what faculty are doing One note or link may be very

significant

Tips & Traps…. (cont.)

Students I do tell my students it’s new Are other students affected? For example

students who took the course previously? Is a plan required for them?

Remember what you had trouble with when doing lesson planning

Tips & Traps….(cont.)

Beta Versions of software During the Term Features of the new software – if

you’re not using them why did you convert?

The Big Five

Start as early as you canIt’s worth the time to find help

Volunteer to help others – you’ll learn too

Use the software for yourselfYou have Time and you can Research –

Use Your Existing Skills!

Contact Me….

Bill Marlow,School of Business,Durham College,2000 Simcoe St. N.,Oshawa, Ont., L1H 7L7

Bill.Marlow@durhamcollege.ca

Thank You!