Monday, November 24, 2014

Core Apps for the #ipadacademy

It's More Than An App

When rolling out iPads in education, often the first question we get is what are your favorite apps?  We chuckle a little, because we know that iPads in the classroom are more than apps.  And while we do use a criteria for choosing apps, we think bigger than just apps.  Bringing iPads in the classroom is just one small piece of the pie.  There is so much more to consider.   


More than an app is needed to be successful, the question becomes what do you want students to accomplish.  When the focus is on student learning, the conversation shifts from apps to how to craft a student centered learning environment.  The iPad is just a tool, a very powerful one, that if used correctly can unleash learning opportunities teachers and students have only dreamed of.  Training, coaching, and on-going opportunities to grow provides teachers a framework on best practices for teaching and learning in a digital classroom.  Instead of using the iPad as a tool to substitute what is currently done in the classroom, teachers instead learn how to shift from a teacher centered classroom to a learner centered classroom.


In Bellevue Public Schools, we use Google Apps for Ed for our student work flow.  Students have access to e-mail, Google Drive, and YouTube.  These buckets become essential tools as students begin to create work and need to share/store/submit their work from their iPads to their teachers and parents.  We favor app that export to Google Drive or YouTube, allow for creativity, are easy to share, work across all grade levels, and increase collaboration.


We’ve been at this now for three years and have learned a lot.  We shy away from in-app purchases and apps that are used in only one part of the curriculum.  We provide continuous training and support to our iPad teachers through monthly collaboration days, in class coaching and co-teaching models, and bring parents in for iPad sharing sessions. We’ve discovered that we really only need about two iPad screens of apps and only three paid apps.   

Here is a link to our favorite core apps.

Written by

Tuesday, November 18, 2014

What is Your Greatness?

New teacher technology training is one of my favorite professional development days I have the privilege of facilitating with my colleagues, Jenny and Jeanette.   New teachers bring joy, enthusiasm, passion, energy and a zest for our profession. 

Today at our new teacher training, we took the time to reflect on our greatness as educators. What do we bring each day to school and share with our students and colleagues?  What is that greatness? How does our greatness make a difference?  

Each new teacher reflected privately and then wrote his/her greatness on a clothespin decorated with Washi tape.  Then each person shared his/her greatness out loud with the group. "Patience, energy, creative, devoted,"  the new teachers said.   


As each new teacher shared their greatness with the group, they clipped their clothespin to our wire wreath.  One by one, the clothes pins were added and soon their pins developed into this stunning reminder of greatness.  Alone we are amazing and as we pool our greatness together, it develops into something unimaginable.  


The wreath will now hang proudly in our office/classroom as a reminder of all the greatness we added to our district this year when we hired our new teachers.  Our new teachers are an amazing group and their greatness is making a difference every day for our students in Bellevue Public Schools.    

Greatness wreath created at New Teacher Training, November 2014.

What is your greatness?  How does your greatness make a difference? Feel free to leave a comment.

Written by Ann Feldmann

@annfeldmann1

References:  Idea modified from a Thankful Wreath featured in the November 2014 issue of  Momaha Magazine 




Monday, November 10, 2014

Becoming a Connected Educator

October was Connected Educator month, but what exactly does this mean? Here are a few steps you can take to get you started on your path to becoming a connected educator. A few tips to remember along the way…..start small and throw fear aside. There are many people here to support and help you along the way.


Step 1: Create social media accounts such as Twitter, Facebook, and LinkedIn. The important thing to remember with this step is to become active with these sites once you create an account. For example, participate in one of these Twitter chats to engage and find people to follow--people that have the same interests as you! If you created a Facebook page or group share something each day and be sure to like other educational pages to receive links to articles, events and ideas.


Step 2: Collaborate using Google+ Hangouts or Skype-become a global educator. Hangout with fellow educators from across the nation and world to collaborate on any topic that is important to you. Use these tools with your classes, all you need is one computer and a projector, to connect to students from all over. Imagine what your students in Nebraska could learn from students in Canada or Australia. So many skills can be developed by becoming a global educator. Join this Google+ community to learn how other teachers are using Hangouts. And this Google+ community if you are interested in connecting your classrooms.


Step 3: Start a blog and share regularly. Read other blogs and start conversations through comments. When starting a blog it is important to start with short blogs, 250 words. Try and challenge yourself to write once every two weeks or even once a week. Too often we feel that we have nothing to share or that we are sharing something that has already been shared. Don’t think this way! Many people like to read different blogs about the same subject gleaning different perspectives from each blog. Blogging is also a great way to reflect and others can learn from your reflection. Click here for links to the most popular educational blogs.


Step 4: Create your own PD by taking on online class at your own pace or attending an Edcamp. There are so many opportunities out there for you to learn what you want to learn, when you want to learn it. There are webinars, Google+ Hangouts, MOOC-ed’s (Massive Open Online Courses for Educators) and Edcamps that can help you focus your learning. Take a hold of your own learning and dive right in.

Step 5: Share and reflect upon your experiences. During your journey to becoming a connected educator, share your thoughts and experiences with others through some of the tools you used above. Share out on Twitter, post on your Facebook page, host a Hangout, write a blog post, participate in an Edcamp. Whatever you choose to do, others can learn from you as they go on their journey to becoming a connected educator.

Written by Jeanette Carlson
@mrsjcarlson

Friday, October 31, 2014

Apple Learning Tour- Worth the Time

Recently myself and my two colleagues, Ann Feldmann & Jeanette Carlson, attended an Apple Event focused on curriculum in the classroom.  Our local Apple reps hosted and they did an amazing job.  What was so great about our time there was that we had time to play.  Yes, I said it! “Play”!  We were allowed to explore apps, design small projects, and reflect on our ideas.  We owned our learning with our guide, Barry Sevett, from Apple.  


Even though we are fairly well versed in all things Apple it was a good way to spend the day being the learner and not the trainer.  There are always more things we can learn from each other when given the time.



The Pyramids
I was reminded of amazing apps, books, and other resources that have strong ties to our curriculum, like the apps Back in Time and Human Body.  These are apps that even though content based could be used in so many classrooms.  I was also reminded of the rich resources in the iBooks Store.  One in particular got me excited.  E.O. Wilson’s Book of Life on Earth is just beautiful and is full of accurate scientific material.  He has now broken his book into 7 different books that are absolutely free!  I already have one teacher trying those out.  We had Romeo and Juliet read aloud to us in a variety of forms.  We checked out Lit2go audio books which are also free.  We went inside the Pyramids in Egypt from an app named The Pyramids.  We watched videos of students creating their own iBooks and publishing them to the NeBooks Project.   We enrolled in an iTunes U Course that we took with us for even more resources.  We participated in a backchannel discussion via our iTunes U course throughout the day.  I appreciated how Apple used solid teaching pedagogy during their own trainings as solid models for educators.   


The Human Body

Back in Time

Sometimes it is human nature to become satiated with a product or an idea.  I fear that some educators and leaders have done this with iPads and are considering other options.  Why, I ask would you go with any other tool than Apple when their wealth of resources for education is so huge you can hardly soak it all up?  The creation piece, individualized learning opportunities, and access to the world cannot be replicated with other devices.  


As trainers and sought after leaders in our field, it was an excellent reminder that what we are doing in our classrooms of iPads is transforming learning for kids.   Change takes time and a commitment to change takes persistence.  


If you’d like more information about the resources we learned more about, please email us, tweet us, or Facebook us.  


Happy Learning and Happy Creating


Written by:  Jennifer Krzystowczyk  

@jennykbps

Wednesday, October 15, 2014

Google Hangouts! Connecting Your Students to the World

Google Hangouts are a great way to connect your students to the world.  Recently, Mrs. Keene from Leonard Lawrence Elementary hung-out with a teacher from Raleigh, North Carolina.  The end goal is that these two classes will embark on a blogging buddy journey this year.  Each student will have a buddy who leaves comments and suggestions on each other’s writing pieces posted on their respective Kidblog.org sites.  


But first, they had to figure out where the other class lived and what grade they were in.  There are several roles involved in a good hangout.  Here are the roles we used to make the hangout successful:


  • Greeters:  These people had a clever opening and welcome greeting for the other class.  
  • A Videographer:  This person is in charge of capturing the video as the hangout is happening.
  • A Photographer:  This person takes still shots to be used in a video once the hangout is over to showcase the hangout, (see below).
  • Inquisitors: These students work in groups to come up with closed ended questions that help the mappers determine the location of the class in question.  For our Hangout we had three different inquisitor groups.
  • Documenters:  These people work on a collaborative Google doc to take notes during the hangout to document questions and answers in case anything is questioned later on.
  • The Mappers:  These students have maps in front of them.  Based on the answers to the questions being asked, they mark through areas that are eliminated.  
  • Closers:  These students say a polite “thanks” and close out the hangout with follow up steps if necessary.  


I was impressed with their questions and they learned a little bit about time zones, different foods, and sporting events in both states.  Our goal was accomplished!  Not only did the students learn a bit more about their world and others in it, they had to use deductive reasoning to solve the puzzle.

And now the fun begins!  I can’t wait to see how their blogging buddy partnership is going to flourish and impact their motivation for high quality writing.  The whole thing took about an hour including prep time, and I think was worth it.  Check out the video below from their experience.  



Written by:  Jenny Krzystowczyk
@jennykbps



Thursday, October 2, 2014

Project Matters: Metro Students Create Mobile Apps for the Zoo

by Guest Blogger:  Cassi Tucker

About the Project
The NRI Zoo Project was the second half of Project MATTERS, the two-year STEM-education focused research initiative funded by the Nebraska Research Initiative.  It took place from December 2013 through May 2014, and was a collaborative effort bringing together a number of community partners, with the goal of teaching middle and high school students from the Omaha area how to program mobile applications.  Beginning with the December kickoff, students participated in monthly workshops, in addition to independent work during the rest of the month, gradually building up a self-defined app idea until the final event, a celebratory/demonstration event hosted at the Henry Doorly Zoo & Aquarium.  To read a short blurb from the UNO team about the project, you can visit here: http://www.unomaha.edu/college-of-information-science-and-technology/news/2014/08/zoo.php

Key Partners
To make the project a success, we relied on several key individuals and groups working together.  From the University of Nebraska at Omaha (UNO) came Neal Grandgenett, from the College of Education (and the individual in charge of the grant); Zac Fowler, who is in charge of student minions at the Attic, a development group out of the College of Information Science and Technology; and myself and my coworker Ben (we’re two of the minions).  Our role was to facilitate everything and help the students during the course of the project, in whatever form that help needed to take.

From the Henry Doorly Zoo & Aquarium, we had two partners from the educational outreach department, who helped students identify projects that would be meaningful to the Zoo, as well as providing feedback to both the students and the UNO team and helping to coordinate a deployment plan.

Finally, we of course had our high school partners—four high schools (Bellevue East, Westside, Gretna, Gross Catholic) and one middle school (Papillion Jr. High) participated, and from them six student teams were developed; these teachers devoted a great deal of time and energy to help the students with development, attended meetings on Saturdays, and keep the UNO and Zoo teams informed about what the students were working on and how things were progressing.  For additional information about the project and full details of each team’s final app, please visit zoo.ist.unomaha.edu/final-projects.

Project Structure
Every school produced a team of students (or two!) who self-organized and identified the project they wanted to work on; the only major limitation given to them was that their app idea had to somehow incorporate the Zoo goals.  This created an enormous diversity in project ideas and, we hoped, would lead to higher engagement as the students were working on something they were genuinely interested in building.  All six teams chose different app ideas to go with; some ideas that began similarly quickly diverged as the teams narrowed their focus and honed in on what they really wanted to build.  Learning for the project was self-directed; students were always welcome to ask for help from the Attic team, but were encouraged to choose their own development tools, find solutions to problems, and learn the skills necessary to accomplish their goals.

Each month, the teams turned in a log of their progress and attended a meeting held either at the Zoo or on UNO’s campus; these were either workshop days, where the Attic team taught the students a new tool or technique to help them along, or demo days, when the students brought their work and showed it off, getting feedback and suggestions to move forward.  Students were given incentives to attend the meetings (such as science books, DIY kits, and other fun STEM education things), and on Zoo meeting days were also given the opportunity to wander around the Zoo, gathering information or testing their apps out in the target environment.

Student Development
Over the course of the project, students really took a lot of initiative in building their apps, some of which were extremely ambitious and complex ideas.  The Attic team worked to facilitate the success of each team, but really left it primarily to the students to research solutions to their problems and to articulate specific questions about things they needed helped with.  In some ways, it was almost like the students were learning how to learn; the success of their projects depended on their ability to independently find solutions.  The students really got invested in their projects this way and as such worked extremely hard to make them successful, putting in a lot of time and effort (both during and outside of school hours).  Not all projects were finished at the end of six months (primarily because, as I mentioned earlier, some of the teams were really ambitious in what they wanted to accomplish) but even the teams that didn’t finish had put in a lot of development time, did a lot of learning, and ended up with at least a partial product to show off at the final demo event.

Outcomes
Overall, the project was an enormous success.  The goal here wasn’t to have perfect, polished, professional applications built for the Zoo; the goal was to engage students in STEM education, interest them in the possibilities of continuing down this path, and give them the tools to direct their own interests.  In those goals, I think we saw overwhelming success; some students even identified a career path in mobile app development that they wanted to pursue.
Within each team there was also some definite growth for the members, from my own perspective.  Over the course of the six months, I saw students really find their own skills to contribute to their team—development, design, graphics, or some other role—and grow in confidence.  Students who started out by asking timid questions, assuming that they had probably just done something wrong or it was a dumb question to begin with, ended the project able to confidently ask questions and articulate what they had done to try to solve the problems.  For many of the students, this was a first foray into real programming (that is, programming with a real goal at the end, not just a “Hello World” and a grade) and that growth in confidence in their own abilities will, I think, be a strong asset for the students in the future, particularly those who continue to build on this programming knowledge.
That’s not to say there aren’t things I would suggest doing differently if I could whip out my Time-Turner and go back.  The team logs were intended to give the Attic team a better idea of what kind of development workshops would be most helpful to the teams; however, the semi-consistent enforcement of turning them in meant that we weren’t always on the same page and therefore the Saturday workshops weren’t always meaningful for the students.  The team logs were extremely helpful when we had them, so in future similar projects I would definitely have them turned in more regularly.  Additionally, because we allowed the teams to choose any project and any tools they wanted…sometimes they picked things that we had never used before.  One team in particular used a JavaScript library called CreateJS, which we at the Attic had never used before—for us, it could be challenging to help solve problems when we were trying to learn everything on the fly as well.  So, again with my Time-Turner, I’d go back and start learning some of those tools earlier so as to better help the students.  

Final Thoughts
This project was one of my absolute favorites to work on so far in my (student) career.  Coming from a high school with no programming classes at all, I understand that many students will shy away from choosing college majors in technology and engineering simply because of lack of prior exposure.  This project gave students a safe, self-driven, no-fail way to get their feet wet in the world of technology, and they were able to try ambitious new things and hone their skills.  I think that, overall, this project was a great success, due to a combination of invested partners and dedicated teachers and student teams.


Cassandra Tucker is a senior at the University of Nebraska at Omaha, working on degrees in History and IT Innovation.  She plans to pursue a Masters degree focusing on the Digital Humanities upon completion of her undergraduate work.  In her spare time, she—wait, she doesn’t have spare time.