Sprint 3 - CSA Objectives
Software Development using Frontend and Spring Boot Backend
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).
- 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.
- Team Issue(s):
- To collaborate effectively, there should be issue(s) assigned to you from the team.
- These issues should show progression from ideation, development, integration (pull request), and how you validated tests.
- Preparation:
- It is best to go through checklists, but be aware these are guidelines.
- The teacher will want you to summarize information effectively.
- A significant part of your success will depend on how you present and self-evaluate.
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 Team Issue(s)/Plan | 2 | ||
Beginning-2-End Contribution | 2 | ||
N@tM Team Presentation | 2 | ||
Live Review Indi Demo | 1 | ||
Total | 10 |
Skills Evaluation
Skill | Points | Grade | Evidence |
---|---|---|---|
Work Habits (Analytics) | 1 | ||
Evidence of Role in Team | 1 | ||
Function / Purpose Design | 1 | ||
Live Review | 2 | ||
Total | 5 |
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 | | |a
Tri 1-3 Review Ticket
Show your teacher that you have chronicled your accomplishments for the trimester.
Checklist
- Tools Mastery:
- Demonstrate your proficiency with the tools you have used.
- Provide examples of how you have effectively utilized these tools in your projects.
- Programming Skills:
- Show your ability to work in the programming languages you have learned.
- Include code samples or project snippets that highlight your skills.
- College Board Requirements:
- Explain how your work aligns with the College Board requirements.
- Provide specific examples or projects that meet these standards.
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 College Board standards.
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).
- Provide examples of feedback and idea sharing among students/developers.
Program Function and Purpose
- Project Purpose:
- Describe the purpose of your project.
- Explain the category of innovation (e.g., productivity, game, social media).
- Understanding and Development:
- Describe how understanding the project improved the ability to develop it.
- Inputs: Describe how you defined inputs.
- Events: Describe the events generated from inputs.
- Outputs: Describe the outputs generated from inputs or events.
- User Interface Design: Show the design of the user interface.
- Data Definition: Show data definitions in the design.
- Individual Coding Knowledge:
- Explain personal coding contributions in terms of code segments, functions, and methods.
- Show the behavior of the program and how it behaves during execution.
- Frontend Coding: Explain how frontend code is organized and runs (inputs and events).
- Backend Coding: Explain how backend code is distinct from frontend (algorithms and storage).
Beginning-2-End Contribution
Program Design and Development by you as an Individual and working with a team.
Collaboration Evidences
- Development Process (Agile Scrum):
- Use an iterative and revision-based process.
- Design / Storyboard: Present your design and storyboard for the project.
- Prototype / Experiments: Explain how you isolated your experiments and developed a prototype.
- Code Organization: Demonstrate how your code is organized into functions, methods, and objects.
- Testing / Automation: Describe any automation of test cases and your testing process.
- Iterative Changes: Highlight iterative changes in your personal GitHub commits.
- Feedback and Corrections: Describe times you received feedback and made corrections.
Program Function and Purpose Evidences
- Program and User Interface:
- Provide an overview of the program and its user interface.
- Explain how the program will change with user interactions or algorithms.
- Include a list of key user interactions and intended outputs.
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
- Presentation Overview:
- Provide a brief summary of your N@tM presentation.
- Highlight the key points and features you presented.
- Audience Feedback:
- Collect feedback from the audience, including peers, teachers, and visitors.
- Summarize the positive feedback and areas for improvement mentioned by the audience.
- Questions and Answers:
- Document the questions asked by the audience during your presentation.
- Provide your answers to these questions and any additional insights gained.
- Demonstration and Interaction:
- Describe how you demonstrated your project to the audience.
- Highlight any interactive elements and how the audience engaged with your project.
- 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.
Live Reivew
Prepare a 1 to 2 minute live presentation summarizing your project accomplishments, collaboration efforts, and feedback from the Night at the Museum (N@tM) presentation.
Key Points to Cover
- Project Overview:
- Briefly describe your project and its main objectives.
- Highlight the key features and functionalities.
- Collaboration Evidences:
- Explain how you used an iterative and revision-based process (Agile Scrum).
- Mention the design, storyboard, and prototype development.
- Describe how you organized your code and automated testing.
- Highlight iterative changes and feedback received.
- Program Function and Purpose:
- Provide an overview of the program and its user interface.
- Explain how the program changes with user interactions or algorithms.
- List key user interactions and intended outputs.
- Night at the Museum (N@tM) Feedback:
- Summarize the feedback received from the audience, including positive feedback and areas for improvement.
- Document key questions asked by the audience and your responses.
- Reflect on the feedback and identify specific areas for improvement.
Summary
- Project Overview: Describe your project, objectives, and key features.
- Collaboration Evidences: Explain your development process, design, code organization, and feedback.
- Program Function and Purpose: Provide an overview of the program, user interactions, and outputs.
- N@tM Feedback: Summarize audience feedback, questions, and reflections.