Team Collaboration Info: This page will be hidden once we go live with the site
Team Name: Breaking Designs Weebly Site: http://breakingdesigns.weebly.com
Bookbuilder Login: breakingdesigns\edtech123
Team e-mail: [email protected]\edtech123
Team Logo: http://imgur.com/43bPL
Team Conference Line: Conference number (605) 475-4700 : Access Code: 944345#
Project Due Dates
Process and products for the Team Project:
due dates posted but the team can work through the process more quickly as appropriate
1- Due Oct 9: Email with basic information on the team and method of communication, brainstorm of ideas for a topic, establish team name
2- Due Oct 16: Establishment of the wiki/web with a front page with a original graphic, timelog page All team members have access to this wiki/web and can edit.
Read about Analysis
3- Due Oct 23: Analysis page: Individual graphic organizer/concept map embedded into the wiki/web page on Analysis with a little information on how the graphic works with the topic. (Team will decide who will do what sort of graphic organizer either the need, learner analysis, task analysis, or goal).
Read about Design
4- Due Oct 30: Design page: Team storyboard for the materials embedded into the Development page. The storyboard serves as the roadmap for the materials. Development of lesson/training.
Read about Development, Accessible materials, Graphic Design
5- Due Nov 6: Develop page: Materials and lesson completed in draft format, formative evaluation developed. Begin implementation of the lesson and materials. Read about Formative Evaluation
6- Due Nov 13: Implementation Page: Formative evaluation posted for team members to submit comments. Individuals in class complete formative evaluation.
7- Due Nov 20: Evaluation Page: Post Summative Evaluation results and any Formative Evaluation to date results from 722 peers posted. (on-going will continue through Nov 27)
8-Due Nov 27: Continue collecting Data from Formative Evaluation, make modifications based on formative evaluation. Post results from Summative evaluation based on implementation.
Individual screencast videos created on different aspects of implementation.
9- Due Dec 4: Final Team report due.
due dates posted but the team can work through the process more quickly as appropriate
1- Due Oct 9: Email with basic information on the team and method of communication, brainstorm of ideas for a topic, establish team name
2- Due Oct 16: Establishment of the wiki/web with a front page with a original graphic, timelog page All team members have access to this wiki/web and can edit.
Read about Analysis
3- Due Oct 23: Analysis page: Individual graphic organizer/concept map embedded into the wiki/web page on Analysis with a little information on how the graphic works with the topic. (Team will decide who will do what sort of graphic organizer either the need, learner analysis, task analysis, or goal).
Read about Design
4- Due Oct 30: Design page: Team storyboard for the materials embedded into the Development page. The storyboard serves as the roadmap for the materials. Development of lesson/training.
Read about Development, Accessible materials, Graphic Design
5- Due Nov 6: Develop page: Materials and lesson completed in draft format, formative evaluation developed. Begin implementation of the lesson and materials. Read about Formative Evaluation
6- Due Nov 13: Implementation Page: Formative evaluation posted for team members to submit comments. Individuals in class complete formative evaluation.
7- Due Nov 20: Evaluation Page: Post Summative Evaluation results and any Formative Evaluation to date results from 722 peers posted. (on-going will continue through Nov 27)
8-Due Nov 27: Continue collecting Data from Formative Evaluation, make modifications based on formative evaluation. Post results from Summative evaluation based on implementation.
Individual screencast videos created on different aspects of implementation.
9- Due Dec 4: Final Team report due.
Timeline for Project
You will all be assigned a team.
1- Decide how the team will communicate or “meet.” Methods that you plan to use for major communication (wiki, google docs, oovoo, skype, adobe connect, voicethread, google hangout etc)
2- Discuss lesson and materials to present to the client on topic based on a needs assessment
3- Dr. Wissick & Ms. Readalot will approve each project idea.
Each each team will submit:
1- Description of the roles in the group
2- Content & rationale for your instruction-based on a needs analysis.
3- Complete analysis of the target learners and task analysis of the content.
Each team should work on the lesson and materials
Each team should:
Each team should
By the end of the semester, each team should
Final products for each team: Documentation of the process
1- Decide how the team will communicate or “meet.” Methods that you plan to use for major communication (wiki, google docs, oovoo, skype, adobe connect, voicethread, google hangout etc)
2- Discuss lesson and materials to present to the client on topic based on a needs assessment
3- Dr. Wissick & Ms. Readalot will approve each project idea.
Each each team will submit:
1- Description of the roles in the group
2- Content & rationale for your instruction-based on a needs analysis.
3- Complete analysis of the target learners and task analysis of the content.
Each team should work on the lesson and materials
- Complete a storyboard for the materials to be developed
- Update weekly time log with hours and tasks completed by each team member.
- Work on materials with formative evaluation included as part of development
Each team should:
- Have completed materials to present to class & client
- Prepare screencast videos discussing their materials, lesson and rationale
- Prepare a survey for formative evaluation and feedback
- Conduct formative evaluation trials with outside users & SME
- Continue to maintain time logs
Each team should
- Conduct formative evaluation – reiterative.
- Conduct formative evaluation with 722 peers.
- Make modifications to the project as a result of peer reviews and formative evaluation trials.
- Conduct summative evaluation of the lesson and materials.
- Continue to maintain time logs
By the end of the semester, each team should
- Post final report on your Product
- Submit completed time logs
- Complete team evaluation survey to be submitted to client.
Final products for each team: Documentation of the process
- Lesson: One lesson/training that has been implemented with a target group.
- Materials: Set of media-based materials to accompany the lesson, justification for use of materials included (Bookbuilder preferred as all the supports for UDL are available but it might not be appropriate for target audience or content.)
- Wiki/Web: Process of ADDIE has been documented in a wiki, weebly or web.
- Final Report: Final report summarizes the process and discusses key components addressed.
