The Long Range Technology Plan offers a vital planning guide for administrators. A summary of its uses might include answers to four pressing questions. What should we do? Who is responsible for implementation? Who will pay for all this? Where can I find help?
What should we do? The answer is multi-faceted. SBEC mastery for all staff must be a priority. Further, TEKS adherence is the law. Leaders must supply current technology to their teachers and students. Finally, at least $50 per student must be allocated to technological needs. Phase I is well defined and helpful. However, Phases II and III leave much to be desired. A proactive district may already have exceeded these goals. They may need new direction.
Who is responsible? That is a very complex question. Obviously, School Boards, Central Office, and Administrators are responsible. Additional TEA, Service Centers, Local Agencies, State Board of Education, Texas Institutions of Higher Learning, and local Parents and Community members all have a vital role.
Who will pay for all this new technology? Answer, all of the agencies and groups listed above. Each entity must contribute to the process. STaR Chart standards maintain that to be a Target campus 30% of the budget should be allocated to technology.(STaR Chart) Further, NCLB outlines funds availability. (ED.gov)
Where can I find help? Answer, all of the agencies and groups listed above. Each agency is responsible for various areas. Local Service centers are to provide service. State Agencies should provide guidance and funding. Local districts and community stakeholders should provide implementation and guidance.
Sources:
NCLB: ED.gov
starchart.esc12.net/
tea.state.tx.us/teachnology/lrpt/lrpt_lrpthtml
Subscribe to:
Post Comments (Atom)
SBEC information must be mastered not only by educators but all leaders as well. Because this may take time, people will need help. It is important for movements like this to be backed by local support. I agree with your ideas and I find your 4 pressing questions valuable to your argument.
ReplyDelete