Sprint 3: Sustained Capstone Teams and N@tM
Beginning in week 9, students establish or continue an OpenCS capstone that can grow across all three trimesters, rather than a project discarded at the sprint's end. Team portfolios include Gamification/Onboarding, Admin/Security, Communication/Design, and AI/Assignments. Students plan before coding, implement Java/Spring REST and MVC features with persistence and Web interfaces, integrate contributions, and test normal, boundary, and failure cases. Individual review tickets connect design, code, tests, and feedback to each student's role. Before week 13, every team completes two mentor reviews and a community N@tM presentation, focusing on the project, a working demonstration, and discussion of how it is made. This mentor-review and community-presentation cycle continues throughout the year, with feedback informing later iterations. The sprint closes with a working deployed feature, presentation, and reflection; later CSA2 and DS2 iterations deepen the same project's CS112/CS113 concepts. Project participation alone does not establish individual mastery or college credit.
Weeks
Trimester Final Evaluation
Use your personal review ticket to connect Sprint 1-3 accomplishments with team issues, code, integration tests, feedback, and reflection. Explain and demonstrate your individual contribution, not just the team’s finished product.
Grading Guideline
| Guideline | Description |
|---|---|
| 55% | Minimum per item |
| 77% | Mostly done |
| 88% | Complete |
| 90% | Maximum perfection |
Points
| Assignment | Points | Due |
|---|---|---|
| Beyond Perfunctory | 1 Bonus | Phase 1 |
| Sprint 1-2, CB Quiz Retro | 1 | Phase 1 |
| Sprint 3, Capstone/Kanban | 1 | Phase 1 - Team |
| CB Unit 1 x 2 best | 1 Auto Grade | Phase 2 |
| Project Phase: Ideate | 1 | Phase 2 - Team |
| Sprint 3, Personal Issue(s) | 1 | Phase 2 |
| CB Unit 2 x 2 best | 1 Auto Grade | Phase 3 |
| Collectables HW | 1 Auto Grade | Phase 3 |
| Project Phase: Prototype | 1 | Phase 3 - Team |
| Work Habits (Analytics) | 2 Auto Grade | Phase 4 |
| N@tM, Project Phase: Test | 2 | Phase 4 - Team |
Course Work - CS112 and CS113 Curriculum Alignment
Sprint 3 establishes the project, team practices, and lead-in skills. Formal CS112/CS113 curriculum alignment begins in Sprint 4. Use the outlines to plan an individual curriculum success path supported by your team.
| Connection | How to Use It |
|---|---|
| CS112 Foundations | Connect demonstrated Java/OOP, models, collections, persistence, and Web-interface work to the relevant outline topics as the formal alignment begins. |
| CS113 Extensions | Plan differentiated implementation and efficiency-analysis work when the relevant topics are introduced. Not every student is expected to complete every advanced CS113 layer. |
System Work - A Capstone That Continues Across Three Trimesters
Students enter CSA having built a community or nonprofit project in the prior year’s APCSP course. CSA extends that experience into sustained, system-level work: integrated OCS features become foundations for future cohorts to maintain and extend, rather than projects discarded at a sprint’s end.
| Stage | Project Role | Individual Evidence |
|---|---|---|
| CSA1 - Trimester 1 | Establish a team role, design a feature, and build an initial Java/Web implementation using the POJO, JPA, and API foundations already introduced. | Design plan, code contribution, integration tests, review ticket, and demonstration. |
| CSA2 - Trimester 2 | Beginning with Sprint 4, strengthen CS112 foundations and connect the CS112/CS113 outlines to the evolving project; introduce AP-aligned searching, sorting, and analysis as scheduled. | CodeRunner competence, tested feature extensions, and explanations of revised design choices. |
| DS2 - Trimester 3 | Extend the project through differentiated CS112/CS113 implementation layers or the ML/AI pathway. | Selected structure or algorithm implementations, correctness and efficiency evidence, presentations, and reflection. |
System Options - Sprint Teams and Feature Portfolios
Choose or continue a team role. Every student maintains an individual curriculum success plan, with team support. Some capstone features are live and others are proposals; distinguish planned or prototype work from work that has actually been integrated.
| Portfolio | Feature Examples | Design and Evidence Focus |
|---|---|---|
| Gamification / Onboarding | Gamified lessons, GameBuilder, AI NPCs, game analytics, wayfinding, and team-building games. | Plan, design, deploy, and test an interaction or progression feature; explain state, data flow, and quest achievements. |
| Admin / Security | OCS-in-a-kit, deployment, mentor management, code-builder UI, administration, table reduction, and the Cybersecurity Game. | Explain the API/POJO/JPA workflow, Admin UI, security configuration, deployment behavior, and schema-upgrade needs. |
| Communication / Design | UX, SASS, announcements, calendar, group/individual direct messages, and microblogging. | Design an interactive hub, connect its interface to services, and test both successful and failed user interactions. |
| AI / Assignments | Student/teacher dashboards, student-success insights, articulation evidence, analytics, and AI grading. | Plan the assignment and data flow; manage submitters, validation, feedback, requirement mapping, and histories. Explain class/year archiving and restart administration. |
Ideate = Communication and Wayfinding
Teacher and peer review support improvement. Keep a personal review ticket or blog that links your team issues, code, tests, and feedback.
| Wayfinding | What to Make Visible |
|---|---|
| Temporal | Compare progress and completed work with the calendar, announcements, and agreed timeline. |
| Social | Communicate your role and dependencies; support teammates inside and outside class. |
| Analytical | Use rubric feedback and artifacts to explain what you know, what improved, and what still needs work. Activity counts alone do not demonstrate competence. |
Prototype - Team Plan and Beginning-to-End Contribution
Create a team issue connecting ideation, design, development, integration, testing, and retrospective. A feature needs an explicit handoff path, not just an isolated implementation.
| Area | Evidence to Explain |
|---|---|
| Ideation and Scope | Identify the audience, problem, feature boundary, acceptance criteria, and your personal responsibility. |
| Design Before Coding | Show the user flow, data flow, interfaces, and important design decisions. |
| Implementation | Identify your code and explain how it supports the feature’s function and purpose. |
| Integration | Link the integration pull request and explain dependencies, contracts, and how your change fits the shared system. |
| Validation | Demonstrate normal, boundary, and failure cases, including the integrated Web result rather than only an isolated method. |
| N@tM, Feedback and Revision | Record feedback received, and the changes made or planned. Explain remaining limitations. |
| Maintenance Handoff | Document operation, setup, tests, and extension points for a future maintainer. |
Test - Demonstration and Reflection
Before beginning Sprint 4, every team completes two mentor reviews and a community N@tM presentation. Focus each review on the project, a working demonstration, and a discussion of how it is made.
| Review Element | Evidence |
|---|---|
| Project and Demonstration | Show the working feature and explain the audience, behavior, and individual contributions. |
| How It Is Made | Explain design choices, code, data flow, integration, and test evidence. |
| Mentor and Community Feedback | Connect the two mentor reviews and N@tM feedback to completed or planned revisions. |
| Continued Development | This mentor-review and community-presentation cycle continues throughout the year as the capstone evolves. Carry forward feedback and next-iteration plans. |
Retrospective - Curriculum Connections for Review
Use these references to plan and review evidence, not to claim skills that have not yet been implemented and demonstrated. Formal alignment starts in Sprint 4; the outlines are a planning reference, not an additional Sprint 3 submission.
| Reference | Connection |
|---|---|
| CSA2 Progression | Carry the established project and lead-in skills into the next stage. |
| CS112 Outline | Connect models, encapsulation, collections, persistence, Web interfaces, and hands-on project evidence to relevant topics. |
| CS113 Outline | Connect design-before-coding and testing evidence; claim deeper structures and efficiency analysis only when demonstrated. |
| Java Reference | Strengthen the Java concepts required by your feature. |