Ten i pods
-
Upload
jscypinski -
Category
Education
-
view
204 -
download
0
description
Transcript of Ten i pods
Ten iPods
We put ten iPod touches into the hands of ten students with behavioral challenges. What could possibly go wrong?
1
2
3
4
5
6
7
8
9
10
Who and why?
5 Behavior Support Team Members
3 Middle Schools
2 Years: Middle schoolers don’t want like to look different…
…unless they think it’s cool.
Hypothesis:
Our hypothesis was that the use of the iPod Touches would improve the students’ ability to take ownership of their behavioral plans, improving their overall rates of positive behaviors and assisting them to generalize positive behaviors to all school settings.
Expected Challenges
• iPods lost, broken, or stolen.
• Teachers resistant to kids using the iPods.
• Kids playing games, using the internet inappropriately, or texting during class.
Unexpected Challenges
• Learning to use the technology (note: Young interns are invaluable.)
• Finding a suitable app: Middle schoolers are not usually motivated by stars and smilies.
More Unexpected Challenges
• Difficulty gaining parent and teacher permission and buy-in.
• The learning curve for teachers was sometimes steep (I thought I was the only one).
• Issues with passwords, passcodes, protections, and internet access.
A Suitable App: Google Docs
Checking In:
Selecting Students
• Past experiences with paper trackers.• Interest in technology.• Need.• Known to behavior team members.• Willingness to complete baseline data and
work with a behavior team consultant.
Results: Unexpected09
/12..
.09
/13..
.09
/14..
.09
/15..
.09
/16..
.09
/19..
.09
/20..
.09
/21..
.09
/22..
.09
/23..
.09
/26..
.09
/27..
.09
/28..
.09
/29..
.09
/30..
.10
/03..
.10
/04..
.10
/05..
.10
/06..
.10
/07..
.10
/10..
.10
/11..
.10
/12..
.10
/13..
.10
/14..
.10
/17..
.10
/18..
.10
/19..
.10
/20..
.10
/21..
.10
/24..
.10
/25..
.10
/26..
.10
/31..
.11
/01..
.11
/02..
.11
/03..
.11
/04..
.11
/07..
.11
/08..
.11
/09..
.11
/14..
.11
/15..
.11
/16..
.11
/17..
.
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
Completion Rates
11/18/2011
12/05/2011
12/06/2011
12/07/2011
12/08/2011
12/12/2011
12/14/2011
12/15/2011
01/06/2012
01/10/2012
01/12/2012
01/13/2012
01/24/2012
01/30/2012
01/31/2012
02/01/2012
02/02/2012
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
Before and After09
/12..
.09
/14..
.09
/16..
.09
/20..
.09
/22..
.09
/26..
.09
/28..
.09
/30..
.10
/04..
.10
/06..
.10
/10..
.10
/12..
.10
/14..
.10
/18..
.10
/20..
.10
/24..
.10
/26..
.11
/01..
.11
/03..
.11
/07..
.11
/09..
.11
/15..
.11
/17..
.11
/28..
.11
/30..
.12
/02..
.12
/06..
.12
/08..
.12
/12..
.12
/14..
.12
/16..
.01
/04..
.01
/06..
.01
/10..
.01
/12..
.01
/17..
.01
/19..
.01
/23..
.01
/25..
.01
/27..
.01
/31..
.02
/02..
.
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
Totals Linear (Totals)
ipod
How it’s used…
• Collect behavior data from classroom teachers.
• Listen to Pandora and ignore annoying students.
• Look cool. • Calculator.• Reminder alarms.
Our first iPod was assigned in November…
Our first theft occurred in December…
1
2
In January we learned how to track stolen iPods.
When a second theft occurred in February, the iPod was recovered within one hour.
3
February Update
• 2 Students using the iPod successfully.• 2 did not use it successfully.
Phase II:
• Put iPods in the hands of teachers and let them experiment.
• Teachers identify a student.
• Focus on students transitioning from one program to another. (i.e. 5th-6th)
Currently, eight iPods are in use by students grades 5-8.
13
45
6
7
8
9
One is on loan to a speech path to trial as a possible communication device for a middle school student.
10
Currently, eight iPods are in use by students grades 5-8.
Student Fidelity RateDaily Behavior
percentage
Self-rating / Agreement with
Teachers Taper Tracker? MaintenanceAS Low Low / Erratic Low N/A N/A
DH Low High High N/A N/A
MB Low High High Yes Yes
JD High High High Not yet Not yet
CJP High High N/A Not yet Not yet
SH High High High Not yet Not yet
JT N/A
OGD High High High Not yet Not Yet
LMP N/A
Suggestions…
• Allow time to experiment with the technology before implementation.
• Encourage peer tech support.
• Provide frequent mini-trainings.