Sprint 3 Discussion: Evaluation & Feedback Guide

Hey guys! Let's dive into the nitty-gritty of Sprint 3 and how we're going to evaluate our progress. This blog post is all about ensuring we're on the right track with our projects and providing constructive feedback to each other. Remember, teacher and peer evaluations are super crucial for our growth and success. So, let’s get into it and make this sprint our best one yet!

Final Intro

To kick things off, it's essential to understand that teacher and peer evaluation play a significant role in our development and overall achievements. Constructive feedback helps us identify areas of improvement and build on our strengths. In this sprint, just like the previous ones, we need to focus on not just completing tasks, but also on reflecting on our work and learning from each other.

To truly support dialogue and collaboration in our learning environment, we should provide what we call a Review Ticket. This can be in the form of GitHub Issues or GitHub Pages Utterances. These tickets serve as a platform for discussing our progress, challenges, and solutions. Engaging in these discussions allows us to gain insights from different perspectives and enhance the quality of our work. The more we interact and share our thoughts, the better equipped we are to tackle complex problems and innovate.

Individual contributions are tracked through personal issues and blog posts, detailing your journey in each sprint. By the end of Sprint 3, you should have documented your experiences, challenges, and accomplishments in personal blogs related to all three sprints. This reflective practice is not just about recording what you did; it’s about understanding how you’ve grown and what you’ve learned along the way. These individual reflections form a crucial part of your overall assessment and demonstrate your commitment to continuous improvement.

Teamwork is another cornerstone of this sprint. To collaborate effectively, you should have team-assigned issues that showcase your ability to work together. These issues should illustrate the entire progression, from initial ideation and development to integration through pull requests and validation via testing. Documenting this process allows you to demonstrate your collaborative skills and the impact of teamwork on your project. It's not just about the final product, but also about the journey and how you navigated it as a team. Remember, the best projects are often the result of diverse minds coming together, sharing ideas, and working towards a common goal.

Preparation is key to success in any endeavor, and this sprint is no different. While checklists can be helpful, they should be seen as guidelines rather than strict rules. Your teacher will be looking for your ability to summarize information effectively and present your work in a clear and concise manner. A significant part of your success will hinge on how you present your project and self-evaluate your performance. This includes being honest about your challenges, highlighting your achievements, and articulating what you’ve learned throughout the sprint. Self-evaluation is a critical skill that not only helps you improve but also demonstrates your self-awareness and commitment to growth.

Final Evaluation

Alright, let's break down how we're going to be graded. This section outlines the criteria and guidelines for the final evaluation of your work this trimester. The evaluation is split into two main parts: Assignments and Skills. Each part has specific things we'll be looking at, so pay attention!

When we talk about the final evaluation, it's crucial to understand that we're assessing not just your final product but also the process you followed to get there. This includes your active participation in discussions, your contribution to team efforts, and your ability to reflect on and learn from your experiences. The evaluation criteria are designed to provide a comprehensive view of your performance, covering both the tangible deliverables and the intangible skills you've developed.

Assignments form a significant part of your evaluation. These include things like your Sprint Review Tickets, Team Issue Plans, contributions to the project from beginning to end, your presentation at the Night at the Museum event, and your live demo. Each assignment is designed to assess specific aspects of your work, from your ability to document your progress to your skills in presenting and collaborating with others. The weighting of each assignment reflects its importance in the overall learning objectives of the sprint. Make sure you've completed each assignment to the best of your ability and that you can clearly articulate your contributions and learnings from each one.

Skills, on the other hand, focus on your overall competency and growth in key areas. This includes your work habits, evidence of your role in the team, your ability to design for function and purpose, and your performance during live reviews. These skills are fundamental to your development as a student and a professional. They demonstrate your ability to work effectively, collaborate with others, think critically, and communicate your ideas. Skills evaluation is often more subjective than assignment grading, but it's based on consistent observations and feedback throughout the trimester. Demonstrating growth in these skill areas is a significant indicator of your overall progress and success.

Grading Guideline

Here’s a quick rundown of how the grading works:

• 55%: Bare minimum to pass.
• 75%: You mostly got it done.
• 85%: You completed the assignment.
• 90%: Maximum perfection – you nailed it!

The grading guidelines provide a clear framework for understanding expectations and how performance is assessed. Each level represents a different degree of completion and mastery of the material. Aiming for the higher percentages not only improves your grade but also demonstrates a commitment to excellence and a thorough understanding of the concepts. The grading is designed to be fair and transparent, providing you with a clear understanding of where you stand and what you need to do to improve.

Assignments Evaluation

Here’s a table breaking down the assignments, points, grades, and how to show your evidence:

Assignment	Points	Grade	Evidence
Sprint 1-3 Review Ticket	3
Sprint 3 Team Issue(s)/Plan	2
Beginning-2-End Contribution	2
N@tM Team Presentation	2
Live Review Indi Demo	1
Total	10

The assignments evaluation table provides a clear breakdown of the specific tasks you need to complete, their respective point values, and the evidence you need to provide to demonstrate your work. This table serves as a roadmap, guiding you through the key components of the evaluation process. The "Evidence" column is particularly important as it highlights what you need to showcase to receive a good grade. This might include code samples, project documentation, presentation slides, or other artifacts that demonstrate your effort and understanding.

Raw Form

| **Assignment**                | **Points**    | **Grade** | **Evidence** |
|-------------------------------|---------------|-----------|--------------|
| Sprint 1-3 Review Ticket      | 3             |           |              |
| Sprint 3 Team Issue(s)/Plan   | 2             |           |              |
| Beginning-2-End Contribution  | 2             |           |              |
| N@tM Team Presentation        | 2             |           |              |
| Live Review Indi Demo         | 1             |           |              |
| **Total**                     | 10            |           |              |

| **Skill**                  | **Points**    | **Grade** | **Evidence** |
|----------------------------|---------------|-----------|--------------|
| Work Habits (Analytics)    | 1             |           |              |
| Evidence of Role in Team   | 1             |           |              |
| Function / Purpose Design  | 1             |           |              |
| Live Review                | 2             |           |              |
| **Total**                  | 5             |           |              |

This raw form gives you a clear view of how each assignment and skill is weighted in the overall evaluation. It's a helpful reference to understand where to focus your efforts and ensure you're meeting the requirements for each category. The distinction between assignments and skills is important. While assignments are specific tasks with defined outcomes, skills reflect your broader competencies and abilities.

Tri 1-3 Review Ticket

Time to show your teacher everything you've achieved this trimester! This is where you chronicle all your hard work and accomplishments.

The Tri 1-3 Review Ticket is your opportunity to showcase your journey throughout the trimester. It's a comprehensive record of your achievements, challenges, and learnings. This review ticket is not just a summary; it's a reflection of your growth and development over time. It allows you to demonstrate your mastery of tools and programming skills, as well as your ability to align your work with College Board requirements. Think of it as your personal portfolio, highlighting the best of your work and demonstrating your commitment to excellence.

Checklist

Here’s what you need to include in your review ticket:

1. Tools Mastery:
   • Show off your skills with the tools you've been using.
   • Give examples of how you've used these tools effectively in your projects.
2. Programming Skills:
   • Prove you can work in the programming languages you've learned.
   • Include code snippets or project examples to highlight your skills.
3. College Board Requirements:
   • Explain how your work lines up with the College Board's standards.
   • Provide specific projects that meet these requirements.

The checklist provides a structured approach to creating your review ticket. Each item focuses on a key aspect of your learning and development. Tools Mastery is about demonstrating your proficiency in using various software and hardware tools effectively. Programming Skills highlights your ability to write code and develop software solutions. College Board Requirements ensures that your work aligns with academic standards and prepares you for future educational opportunities. Addressing each item thoroughly will result in a comprehensive and compelling review ticket.

Summary

To recap, make sure your review ticket includes:

• Tools Mastery: Prove you’re a tool whiz.
• Programming Skills: Show off your coding chops.
• College Board Requirements: Explain how you’re meeting the standards.

This summary reinforces the key elements of a successful review ticket. It’s a quick reminder of the main points you need to cover to demonstrate your progress and achievements. By focusing on tools mastery, programming skills, and alignment with College Board requirements, you can create a review ticket that accurately reflects your hard work and dedication throughout the trimester.

Sprint 3 Team Issue / Plan

Let's talk about planning! Show your teacher all the evidence of the awesome plans you've made as a team this sprint.

The Sprint 3 Team Issue / Plan is a critical component of your evaluation as it highlights your ability to work collaboratively and effectively plan project tasks. Planning is the backbone of any successful project, and this section allows you to showcase your team's strategic thinking and organizational skills. It’s not just about having a plan, but also about demonstrating the evidence of that plan and how it was executed.

Collaboration Evidences

Here’s what you should cover to show off your collaboration skills:

• Iteration and Improvement:
  • Show how you've iterated on computing innovations and made them better through collaboration.
  • Give examples of how teamwork has led to innovations that reflect everyone's talents.
  • Explain how diverse views have helped you avoid bias.
• Think-Pair-Share:
  • Share instances where pair programming improved your ideas.
  • Describe times when team coordination really helped the project.
• Online Collaboration Tools:
  • Show evidence of using tools like Slack, GitHub Issues, and GitHub Project to collaborate.
  • Give examples of how you shared feedback and ideas online.

These collaboration evidences provide a framework for demonstrating your team's ability to work together effectively. Iteration and Improvement highlights the iterative nature of software development and the value of continuous feedback. Think-Pair-Share showcases the benefits of pair programming and team coordination. Online Collaboration Tools emphasizes the importance of using digital platforms to facilitate communication and collaboration. Providing specific examples in each category will strengthen your evaluation and demonstrate your commitment to teamwork.

Program Function and Purpose

Let's dig into your project's purpose and how it works:

• Project Purpose:
  • Describe what your project is meant to do.
  • Explain what kind of innovation it is (like a game or social media app).
• Understanding and Development:
  • Describe how knowing the project's purpose helped you develop it.
  • Inputs: Explain how you defined inputs.
  • Events: Describe the events that come from inputs.
  • Outputs: Explain the outputs from inputs or events.
  • User Interface Design: Show off your UI design.
  • Data Definition: Show how you’ve defined data.
• Individual Coding Knowledge:
  • Explain your personal coding contributions, like code segments and functions.
  • Show how the program behaves when it’s running.
  • Frontend Coding: Explain how your frontend code is set up and works.
  • Backend Coding: Explain how your backend code is different from the frontend.

This breakdown of program function and purpose dives deep into the core elements of your project. Project Purpose sets the stage by defining the project’s goals and category of innovation. Understanding and Development delves into the technical aspects, such as defining inputs, events, outputs, and user interface design. Individual Coding Knowledge highlights your personal contributions and understanding of both frontend and backend coding. Addressing each of these points comprehensively will demonstrate your technical proficiency and your ability to articulate complex concepts.

Beginning-2-End Contribution

Talk about your role in the project from start to finish! This is about your individual work and your teamwork.

The Beginning-2-End Contribution section is designed to highlight your role in the project throughout its lifecycle, both as an individual contributor and as a member of a team. It’s about demonstrating your involvement from the initial design phase to the final development and testing stages. This section allows you to showcase your commitment, skills, and collaborative spirit in bringing a project to fruition.

Collaboration Evidences

Here’s what to focus on to showcase your collaboration skills:

• Development Process (Agile Scrum):
  • Explain your iterative and revision-based process.
  • Design / Storyboard: Present your design and storyboard.
  • Prototype / Experiments: Explain how you developed your prototype.
  • Code Organization: Show how your code is organized.
  • Testing / Automation: Describe your testing process.
  • Iterative Changes: Highlight changes in your GitHub commits.
  • Feedback and Corrections: Talk about times you got feedback and made corrections.

These collaboration evidences focus on the Agile Scrum development process, a popular methodology for software development. Presenting your design and storyboard provides a visual representation of your project’s conceptual framework. Explaining how you developed your prototype highlights your experimental approach and problem-solving skills. Demonstrating your code organization showcases your ability to write clean and maintainable code. Describing your testing process emphasizes the importance of quality assurance. Highlighting iterative changes and feedback received underscores your commitment to continuous improvement.

Program Function and Purpose Evidences

To nail this section, make sure you cover:

• Program and User Interface:
  • Give an overview of your program and its UI.
  • Explain how the program changes with user interactions.
  • List key interactions and outputs.

This part is all about providing tangible evidence of your program’s functionality and user interface. Providing an overview of your program and its UI sets the context for understanding its capabilities. Explaining how the program changes with user interactions demonstrates its dynamic nature and responsiveness. Listing key interactions and outputs gives a clear picture of its functionality. This evidence helps demonstrate that you understand how your program works and how users will interact with it.

Night at the Museum (N@tM) Presentation Feedback

Time to think about your N@tM presentation! Gather feedback and reflect on how it went. This will help you make your project even better.

The Night at the Museum (N@tM) Presentation Feedback section is all about reflecting on your presentation experience and gathering feedback to improve your project. Presenting your work is an important skill, and this section encourages you to think critically about how you communicated your ideas and engaged with your audience. Gathering feedback from peers, teachers, and visitors provides valuable insights for future improvements.

Checklist

Here’s what you need to cover:

1. Presentation Overview:
   • Summarize your presentation.
   • Highlight the key points.
2. Audience Feedback:
   • Collect feedback from everyone.
   • Summarize the good and the bad.
3. Questions and Answers:
   • List the questions you were asked.
   • Provide your answers and any extra insights.
4. Demonstration and Interaction:
   • Describe how you showed off your project.
   • Highlight any interactive parts and how the audience engaged.
5. Reflections and Improvements:
   • Reflect on the feedback and your experience.
   • List areas for improvement and next steps.

This checklist provides a comprehensive guide to reflecting on your N@tM presentation. Presentation Overview ensures that you have a clear summary of your presentation’s content. Audience Feedback emphasizes the importance of gathering and summarizing feedback from various sources. Questions and Answers highlights the value of documenting audience inquiries and your responses. Demonstration and Interaction encourages you to reflect on how you showcased your project and engaged your audience. Reflections and Improvements focuses on identifying areas for growth and planning future steps.

Summary

To sum it up, make sure you include:

• Presentation Overview: A summary of your N@tM presentation.
• Audience Feedback: Feedback from everyone who saw your presentation.
• Questions and Answers: The questions you got and your answers.
• Demonstration and Interaction: How you demonstrated your project.
• Reflections and Improvements: What you learned and what you’ll do next.

This summary reinforces the key elements of the N@tM presentation feedback section. It’s a quick reminder of the main points you need to address to demonstrate that you’ve thoroughly reflected on your presentation experience. Covering each of these points will help you identify areas of strength and areas for improvement in your presentation skills and project development.

Live Reivew

Get ready for your live review! This is a short presentation summarizing your project, collaboration, and feedback.

The Live Review is your chance to shine and summarize your project accomplishments, collaboration efforts, and the feedback you received from the Night at the Museum presentation. This short presentation is a critical component of your evaluation as it demonstrates your ability to synthesize information, communicate effectively, and present your work in a concise and compelling manner. Think of it as your elevator pitch – a brief overview that captures the essence of your project and your contributions.

Key Points to Cover

Here’s what you should include in your live review:

1. Project Overview:
   • Briefly describe your project.
   • Highlight key features.
2. Collaboration Evidences:
   • Explain your Agile Scrum process.
   • Mention your design and prototype.
   • Describe code organization and testing.
   • Highlight changes and feedback.
3. Program Function and Purpose:
   • Overview of the program and UI.
   • Explain how it changes with user interactions.
   • List key interactions and outputs.
4. Night at the Museum (N@tM) Feedback:
   • Summarize feedback from the audience.
   • Document key questions and answers.
   • Reflect on feedback and improvements.

These key points provide a structured outline for your live review. Project Overview sets the context by briefly describing your project and its main features. Collaboration Evidences highlights your team’s development process, design, and testing efforts. Program Function and Purpose provides an overview of your program’s functionality and user interface. Night at the Museum (N@tM) Feedback summarizes the feedback you received and your reflections on it. Addressing each of these points will help you deliver a well-rounded and informative presentation.

Summary

To wrap things up, make sure you touch on:

• Project Overview: Describe your project and its main goals.
• Collaboration Evidences: Explain your development process and teamwork.
• Program Function and Purpose: Provide an overview of your program’s functionality.
• N@tM Feedback: Summarize feedback and your reflections.

This summary reinforces the essential elements of your live review. It’s a quick checklist to ensure that you’ve covered all the critical aspects of your project and your learning journey. By focusing on these points, you can deliver a compelling presentation that demonstrates your accomplishments and your understanding of the project’s significance.

So, there you have it! That’s the rundown on Sprint 3 evaluations and feedback. Make sure to use this guide to prepare your review tickets, team plans, and presentations. Good luck, guys, and let’s finish this sprint strong!