home

=__The Kitchen Sink__=

PWCS Class Apps Page
[]

To login and edit PWCS Class Apps Page
[]

Email from Terry Lowry on 3/21/2012
Hello iPad App Revew SubCommittee!

I've cleaned up the information from the notes at our last meeting and combined it with the additional recommended apps that have come in since then. Please see the attached document. The new ones need reviewers, so if you'd like to volunteer for any of them, please let me know. We'll have to divide them up, anyway, at Friday's meeting.

Tommi has given everyone access to the webpage now ([] to add information (Thanks Netia and Tommi for what you've already posted!). The page is looking great! When you write your reviews, I think it's best to include a **brief** description of what the app is or does and then, if you have it, an example of how it can be used instructionally.

And here are our action items for Friday's "Appy Hour(s)" :-)
 * 1) Provide feedback to Tommi on the webpage - all good? anything need to be tweaked? any difficulties using/adding info?
 * 2) Provide feedback on reviews that have been done - are they what we envisioned? Is there anything we are missing?
 * 3) Take a look at the apps we've reviewed. Are they all "Must Have" Apps? If not, let's tag them as "Nice to Haves", instead
 * 4) Assign new apps to reviewers - We will need to review the ones that came in from other ITRTs that weren't on the original list

Remember: **The ultimate goal of the committee is to have a working list of "Must Have" Apps by Friday, March 30**. While what we produce does not have to be perfect by then, and more apps can be added later, we should have something that we are all comfortable going forward with.

** Action Items from Brian Hackett **

 * 1) Please make all current documents in use regarding the points above available in word format to be shared (Google Docs)
 * 2) Establish the ‘Have to Have Apps’ for schools for (March) budget timeline.
 * 3) Based on current volume apps purchased establish an organizational process that will be used to fit into the developing review template (March)
 * 4) Establish a uniform tagging system that integrates with the interface and is searchable. (March)
 * 5) Create a repository environment for all ‘approved’ apps. (March)
 * 6) Build a uniformed ‘instructional’ technology review process or program that can be adapted for all instruction resources (websites, software, videos etc..) This item will have to be integrated with the web interface tagging system. //Note this process must include Network Security// (April) - Make sure that this review process can be expanded or is the ‘pilot’ process for detailed data collection and assessment of apps to be considered for approval list.
 * 7) Develop a PD for the review process that allows establishes uniformed reviewing of all instructional assets. (June)

Brent's Review Form
[] []#

iPad Task Force Collaborative Website:

 * ==PWCS Class Apps==

Links, Files, Etc.
==

[] [] [] [] [] [] [] [] [] [] [] [] http://balancedtech.wikispaces.com/iPad [] [] [|https://docs.google.com/a/lowrycenter.com/spreadsheet/ccc?authkey=COnNtvwO&key=0AvFbfb1mWoNwdGlweWtkZkFRS1gzUDMtTUtoTEw0MkE&hl=en&authkey=COnNtvwO#gid=0] [] [] [] http://teachwithyouripad.wikispaces.com/ [] [|http://edtechteacher.org/index.php/teaching-technology/mobile-technology-apps/ipad-as#audio]


 * 1) How do we establish the Instructional value of apps or other resources? This is a loaded question as we know that all teachers can with support show the value of any app that they take learning ownership in. It was suggest that through our testing or piloting we will be able to gain the best data on instructional value. A database that can be sorted by grade level, subject area, and unit of study might describe how certain apps were used to teach those learning objectives.
 * 2) Can we create a ‘testing’ solution for apps where we document from start to finish the instructional process (prep to assessment) All in agreement that is a process that will allow for quality data on each application. A general format for introducing any new technology might be appropriate. For example, 1) guided or focused exploration of the app/technology 2) creation of very short sample project using the app/technology 3) presentation of assessment/grading rubric for final project 4) creation of project allowing for student collaboration and sharing of expertise using the app/technology 5) on-the-spot assessment of student work allowing for differentiation of instruction 5) sharing/publishing of student work
 * 3) How do we instructional tag:
 * Consensus is that VA Standards are essential (Common Core are not as stringent as VA so it will be easy to adjust if needed down the road)
 * Grade Level & Content areas are essential I think that grade level, subject area, and unit of study are a good place to start.
 * Learning Styles here we need to develop categories for tagging. Different kinds of apps will target different learning styles, for example, Educreations will target kinesthetic (hand-drawings), auditory, and visual learning styles while Storykit will target written, visual, and auditory learning styles. Something like AudioNotes will target written and auditory, Skitch would target visual, Keynote with the hyperlinking would lend itself to higher level critical thinking... just thoughts, but all of these tags could be worked into a form that documents how teachers used specific apps in their classrooms to teach specific learning objectives.
 * Notes from meeting: One of the real problems that we going to have reviewing apps are how we purchase to review? Cost of apps range from free to $200. Short of sitting down in a room and sharing the apps via projectors or devices this needs will be an issue that the committee will need to address. Tommi has posted and we all will be able to access her document and blend it with others one (I will send a link and invite via Google docs). Because of the diverse needs of apps it seems that fewer maybe better to start with. As we start the review process we will begin with the essential apps for production on the devise that can be universal that we can share with school for the upcoming budgetary timeline. Once again Special Education has established some of the framework for this work and we will begin to adapt their efforts into our work. AJ is working with Apple to create a PWCS App site within iTunes, this would be a great advantage for purchasing approved apps. ** I'm thinking we start with must-have productivity apps and share how teachers are using these apps in their classrooms. The format could be something open-ended like a blog discussion on School Fusion, or it could be something more structured like a Google docs form that asks specific questions regarding how the app or technology was used in the classroom. My feeling is that some of these issues will need to be addressed primarily at the building level, with some flexibility to accommodate for a range of staff needs, then ITRTs might share best practices at the county level.