Rock+RoomNeit2010+Open+Space+5+D

Couple quick points: John Hutzler @ Heschel
 * erate funding has dropped requirement for tech plan
 * general, less a tech plan -- formalized strategic plan -- put together 3-4 people who get tech (admin faculty etc) -- we're going to meet an hour every 2-3 months and convene more often if need be -- but intitutionalize the longterm vision and manage the classes....
 * has templates for development and will be happy to forward (john [AT] heschel [dot] org)
 * planning is good and hard

Templates: -- [|Erate] -- NAIS

(Keep things lofty -- not specific.) -- don't want to get locked in to something that you don't want.

Budget part of tech plan? -- or separate --

Reshan -- Town School --
 * As part of the NAIS recommendations for self study -- were 'required' to create tech plan
 * They split infrastructure from curriculum -- but had Tech people go on both --
 * curriculum led the infrastructure -- which means that ed goals led technology purchasing.
 * Using learning goals from the UbD to help draft -- school-wide goals
 * Took goals from school -- then embellished with a tech lens -- not skill or tool specific -- but an approach
 * the big idea then drilled down to more granular and short term (student skill & tech matrix) -- plotting with each division where things might/should be taught -- but that list needs to be updated annually... this is built in to the plan.
 * another sheet with division by where we are, and where we ought to be -- to be revisited each summer.
 * Finally -- made concrete bulleted recommendations. To be affirmed or nixed by Head of School.
 * Biggest success has been PD. Previously no formal evaluation of faculty -- but have now been able to create a formalized structure of what teachers are doing to update themselves based on the students.
 * Created tech professional development credit system -- 'teachers need x credits of tech PD' -- made it easy to attain, (e.g. 3 credits for an in-house after-school workshop, 4 credits for in-house half day, 5 for full day -- etc.) -- need to write a summary in order to get your credit -- creates a library of shared experiences, and even say 'this isn't so useful' -- this is posted on a thread on the website. -- Also on the site are upcoming professional development opportunities -- Credit system is maintained via a Google spreadsheet -

More notes - Tech Plan Notes NEIT 2010 -E Rate funding, Tech Plans not required anymore... -formalize strategic planning -small group that meets to discuss trends at your school, faculty, admin, board member? -NYSAIS Tech plans??? -Short - one paragraph, be flexible, not specific -Implementation of tech...issues for not getting it going. -committee that meets once a month -tech use is not evaluated for teachers; what are using, what did you do, do the kids learn better because. -tech. development for faculty...stipends for attendees? -Global Nomad - didn’t work

-Collaborative project curriculum -open to work with each teacher -New literacy's - digital...??? -Does the tech plan influence the budget? Not usually associated -formal tech. review for faculty part of overall review Audit of what each teacher knows/uses... Goals for faculty for each faculty member -keep the goals open that don’t have to be re-written

-Split in 2 groups 1. Curriculum - developed 1st, to steer infrastructure.

2.Infrastructure

Built around school mission statement

The NET standards...based our goals on those...

John Hutzler, The Heschel School, DOT, __john@heschel.org__  -has information willing to share about tech. plans

Look at self study and accreditation notes

Tech Committee? -Head of school...suggestions, academic tech committee, sub committees, less informed that are willing to work, not always the most technically savvy, representation from each division 2 per, include specials,