Final Intro

Teacher and peer evaluation are critical to our success and improvements.

Be sure to support each meeting’s objectives by performing self-reviews, providing feedback to peers, and acting on the feedback received from teachers and peers. The best way to support dialogue in our environment is to provide a Review Ticket (GitHub Issues and/or GitHub Pages Utterance).

  1. Individual Issues:
    • It is required to build an issue and/or blog that describes your personal journey in all sprints.
    • By the end of this period, you should have personal issues/blogs related to Sprint 1, Sprint 2, and Sprint 3.
  2. Teaching/Lesson Issue(s)/Blog:
    • To collaborate effectively, there should be issue(s) assigned to you from the team.
    • This issue should show preparation, teaching, and grading.
  3. Homeworks:
    • The teacher will want you to summarize homeworks effectively.
    • A significant part of your success will depend on how you present and self-evaluate.
  4. Home Page, Blogs, and and Game
    • Be prepared to Demo your personal Web Site.
    • Show your key accomplishments through trimeseter.

Final Evaluation

This section outlines the criteria and guidelines for the final evaluation of your trimester work. The evaluation is divided into two main categories: Assignments and Skills. Each category has specific items that will be graded based on the provided guidelines.

Grading Guideline

  • 55%: Minimum per item
  • 75%: Mostly done
  • 85%: Complete
  • 90%: Maximum perfection

Assignments Evaluation

Assignment Points Grade Evidence
Sprint 1-3 Review Ticket 3    
Sprint 3 Teaching Issue(s)/Plan 2    
Homeworks 5    
Home Page 2    
Total 12    

Skills Evaluation

Skill Points Grade Evidence
Work Habits (Analytics) 1    
Beyond Perfunctory 1    
Live Review 2    
Total 4    

Raw Form

| **Assignment**             | **Points**    | **Grade** | **Evidence** |
|----------------------------|---------------|-----------|--------------|
| Sprint 1-3 Review Ticket   | 3             |           |              |
| Sprint 3 Teaching Issue(s)/Plan | 2        |           |              |
| Homeworks                  | 5             |           |              |
| Home Page                  | 2             |           |              |
| **Total**                  | 12            |           |              |

#### Skills Evaluation

| **Skill**                  | **Points**    | **Grade** | **Evidence** |
|----------------------------|---------------|-----------|--------------|
| Work Habits (Analytics)    | 1             |           |              |
| Beyond Perfunctory         | 1             |           |              | 
| Live Review                | 2             |           |              | 
| **Total**                  | 4             |           |              |

Tri 1-3 Review Ticket

Show your teacher that you have chronicled your accomplishments for the trimester.

Checklist

  1. Tools Mastery:
    • Demonstrate your proficiency with the tools you have used.
    • Provide examples of how you have effectively utilized these tools in your projects.
  2. Programming Skills:
    • Show your ability to work in the programming languages you have learned.
    • Include code samples or project snippets that highlight your skills.

Summary

  • Tools Mastery: Demonstrate proficiency and effective use of tools.
  • Programming Skills: Showcase your ability to work in the programming languages.
  • College Board Requirements: Explain alignment with lessons taught.

Sprint 3 Team Issue / Plan

Planning has evidences.

Collaboration Evidences

  • Iteration and Improvement:
    • Show iteration on computing innovations and how it was improved through collaboration.
    • Provide examples of how collaboration produced an innovation that reflected the diversity and talents of the team.
    • Explain how diverse perspectives helped avoid bias or a single perspective.
  • Think-Pair-Share:
    • Provide examples of how pair programming improved ideas.
    • Describe instances of team coordination that helped the project.
  • Online Collaboration Tools:
    • Show evidence of using online tools to support collaboration (e.g., Slack, GitHub Issues, GitHub Project, Copilot).
    • Provide examples of feedback and idea sharing among students/developers.

Night at the Museum (N@tM) Presentation Feedback

Gather feedback and information from your N@tM presentation to reflect on your project and identify areas for improvement.

Checklist

  1. Presentation Overview:
    • Provide a brief summary of your N@tM presentation.
    • Highlight the key points and features you presented.
  2. Audience Feedback:
    • Collect feedback from the audience, including peers, teachers, and visitors.
    • Summarize the positive feedback and areas for improvement mentioned by the audience.
  3. Questions and Answers:
    • Document the questions asked by the audience during your presentation.
    • Provide your answers to these questions and any additional insights gained.
  4. Demonstration and Interaction:
    • Describe how you demonstrated your project to the audience.
    • Highlight any interactive elements and how the audience engaged with your project.
  5. Reflections and Improvements:
    • Reflect on the feedback received and your overall presentation experience.
    • Identify specific areas for improvement and potential next steps for your project.

Summary

  • Presentation Overview: Summarize your N@tM presentation and key points.
  • Audience Feedback: Collect and summarize feedback from the audience.
  • Questions and Answers: Document audience questions and your responses.
  • Demonstration and Interaction: Describe how you demonstrated your project and audience engagement.
  • Reflections and Improvements: Reflect on feedback and identify areas for improvement.