Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Technology Use Plan


Published on

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

Technology Use Plan

  1. 1. Technology Use Plan By Shanda Veatch EDTECH 571
  2. 3. Planning Team <ul><li>Member of the school Board </li></ul><ul><li>Administrator </li></ul><ul><li>Representative of classified staff </li></ul><ul><li>Representative of teaching staff </li></ul><ul><li>Curriculum Coordinator, or equivalent </li></ul><ul><li>Technology Consultant from the community </li></ul><ul><li>Parent </li></ul><ul><li>Technology Coordinator </li></ul>
  3. 4. Process Description
  4. 5. Vision Statement <ul><li>Washington State Educational Technology Plan </li></ul><ul><li>Vision for Educational Technology (Expanded Version) </li></ul><ul><li>In a society increasingly dependent on information and knowledge, equitable and universal access to technology, media and information resources are essential to the learning process. With access to and proficiency in the use of these tools, and with the guidance of skilled educators and community members, all students have the opportunity to become actively engaged and take responsible roles in their learning as they think, create, conduct inquiries, solve problems and communicate in individual, collaborative and interdisciplinary settings. As a result, students emerge as lifelong learners, productive members of the workforce, and citizens that can effectively contribute to our democratic way of life </li></ul><ul><li>Vancouver School District Technology Vision Statement </li></ul><ul><li>Each of our learners will become technologically literate and use technology purposefully, effectively and ethically in the learning process. Technology will enhance instruction and be balanced with other resources to personalize learning </li></ul>
  5. 6. Plan/Goal Objectives 2007-2010 TECHNOLOGY PLAN DISTRICT TECHNOLOGY GOALS Goal: Technology Literacy for Students SMART Goal Statement: By the spring of 2010, 80 % of all 8th graders will be at tier 2 or 3 on the technology literacy indicator scale. Strategy: Information Processing 1. Students will access and retrieve electronic information. *Use search strategies. *Use electronic encyclopedias, almanacs, indexes and catalogs. *Use electronic dictionary/thesaurus and calculators. *Use laser disc, VCRs, CD-ROM, and other remote control devices *Use local area networks to locate information. *Use the Internet to access and send information. 2. Students will use information to support learning in all content areas. Rationale: Students will use technology to access, retrieve, evaluate and interpret visual/auditory information. Evaluation Procedure: Activity/Task Professional Development Evaluation (Measurable Change) People Involved Starting and Ending Dates Resources: Description / Type Cost / Funding Source 5th through 8th grade computer and keyboarding classes. Technology Conferences and classes 8th grade Technology Literacy Survey; Individual classroom assessment. Middle School Teachers; Technology Director. 9/1/2007 - 6/30/2010 Students will apply their computer skills across curriculum. Technology Conferences or Classes 8th grade Technology Literacy Survey; Individual classroom assessment. Middle School Teachers; Technology Director. 9/1/2007 - 6/30/2010 Updated Software for computers and servers 3000.00/ General fund
  6. 7. Needs Assessment <ul><li>According to The Washington State Office of the Superintendent of Public Instruction Educational Technology Essential Conditions Rubric , all districts are to achieve proficiency in the following key areas. All educational technology needs assessments must include the following : </li></ul><ul><li>Student Technology Literacy Standards </li></ul><ul><li>Technology Standards for Teachers </li></ul><ul><li>Technology standards for Education Leaders and Staff </li></ul><ul><li>Community Connections </li></ul><ul><li>Technology Support </li></ul><ul><li>Instructional Technology Staffing </li></ul><ul><li>Adequate Ongoing Funding </li></ul><ul><li>Electronic Data Support Systems </li></ul><ul><li>Student Access to Technology </li></ul><ul><li>Teacher/Education Leader/ Staff Access to Technology </li></ul><ul><li>Aligned Curriculum-based tools and Resources </li></ul><ul><li>Network Capability/ Internet Access/ Video Capacity </li></ul><ul><li>Technology Professional Development Plan and Funding </li></ul><ul><li>Models and Content of professional Development </li></ul>
  7. 8. Plan for Professional Development <ul><li>The Washington State Department of Educational Technology outlines the following focus areas for staff development: </li></ul><ul><li>Research </li></ul><ul><li>Software or hardware training </li></ul><ul><li>Attend conference (NCCE Spokane) </li></ul><ul><li>Content area PD opportunities- face-to-face or online, on-going </li></ul><ul><li>Professional Development Models: </li></ul><ul><li>Workshops , Hands-on Labs, Train the Trainer, Learning Teams, Mentoring, Authentic Task Approach, Online Training </li></ul><ul><li>Some possible ideas for building level professional development are: </li></ul><ul><li>Basic, intermediate and advanced PowerPoint, Office and Publisher </li></ul><ul><li>Photoshop and Movie Maker training </li></ul><ul><li>Collaborative web resource investigations within departments </li></ul><ul><li>Web Page development classes </li></ul><ul><li>Assistive technology training </li></ul>
  8. 10. Timeline <ul><li>Feds require multi-year district technology plans; most building SIP plans are 1-year plans (sometimes 2-yr, occasionally 3-yr) </li></ul><ul><li>Needs should be identified at building level in SIP plans, but may need district help to achieve them (i.e., funding, PD) </li></ul><ul><li>The timeline for integrating and coordinating technology across the curriculum at Gaiser MS will require 2 years : </li></ul><ul><ul><li>August-December 2008: Needs Assessment/ Professional Development (Analysis, Design, Development) </li></ul></ul><ul><ul><li>January- December 2009: Implementation </li></ul></ul><ul><ul><li>September- March 2010: Evaluation, revision (Development) </li></ul></ul><ul><ul><li>March- June 2010: Implementation/ Evaluation </li></ul></ul>