71
edits
Changes
Jump to navigation
Jump to search
Line 14:
Line 14: + + + + + + + + + +
→Types of Requests
The first are barriers and bugs to executing the desired lesson plans. The second are tools and technologies to manage many students and allow them to work together. The major headigs below fall in to the second category. We should add any lesson specific bugs or features here as well.
The first are barriers and bugs to executing the desired lesson plans. The second are tools and technologies to manage many students and allow them to work together. The major headigs below fall in to the second category. We should add any lesson specific bugs or features here as well.
For lesson specific features priority will be given to the following kinds of issues:
* SW is hard to explain and/or its not discoverable so kids need 1 - 1 help.
* SW is time consuming, slow or requires too many clicks.
* Something we want to do is not possible.
* New or updated activity is needed.
* Crash or failure to perform as intended, especially if it entails data loss.
* Class management is too time consuming for the teacher.
Time is extremely precious in class. You get one hour with the kids so every second counts. If something is not clear to kids and you have to explain it to each kid or touch each computer, that is very costly. If it takes 1 minute to show a kid how to do something, there are 20 kids and you have lost 1/3 of your class!
==Solid Collaboration==
==Solid Collaboration==