-
Notifications
You must be signed in to change notification settings - Fork 2
URC 2025 Sprint Plan
This page outlines the sprint structure and timeline for the URC 2025 project. Each sprint focuses on specific goals to ensure steady progress throughout the academic year and successful preparation for the URC competition.
| Sprint | Start Date | Due Date | Description |
|---|---|---|---|
| Sprint 0: Pre-Semester Planning | June 1, 2024 | September 15, 2024 | Initial setup, planning, and defining goals for the upcoming semester. |
| Sprint 1: Core Development | September 16, 2024 | October 20, 2024 | Focus on implementing the primary features and laying the foundation. |
| Sprint 2: Testing and Refinement | October 21, 2024 | November 10, 2024 | Conduct testing, address bugs, and refine the work from earlier sprints. |
| Sprint 3: Feature Completion | November 11, 2024 | December 01, 2024 | Complete major features and stabilize the codebase before the semester ends. |
| Sprint 4: Performance and Optimization | December 02, 2024 | January 26, 2025 | Focus on performance improvements, bug fixes, and documentation. |
| Sprint 5: Simulator Integration and Testing | January 27, 2025 | February 23, 2025 | Integrate the simulator and conduct in-depth testing. |
| Sprint 6: Final Testing and Refinement | February 24, 2025 | April 27, 2025 | Perform final testing rounds and polish features. |
| Sprint 7: Final Polishing and Release Prep | April 28, 2025 | May 25, 2025 | Finalize all aspects and prepare for the release. |
| Sprint 8: Retrospective and Maintenance | May 26, 2025 | June 01, 2025 | Conduct a project retrospective and address any outstanding issues. |
- Start Date: June 1, 2024
- Due Date: September 15, 2024
Description:
The focus of Sprint 0 is on preparing for the upcoming academic year and ensuring that the team is ready to begin full development. This pre-semester phase involves setting up the development environment, including tools, repositories, and communication channels. Key project goals will be defined, and the team will create a high-level roadmap that outlines major milestones and deliverables for the entire year.
Additionally, the sprint will include team-wide discussions to establish the technical foundation for the project. This includes choosing core technologies, setting up GitHub workflows, and making architectural decisions that will influence the project moving forward. The objective is to have everything in place so that active development can begin immediately at the start of the semester.
- Start Date: September 16, 2024
- Due Date: October 20, 2024
Description:
Sprint 1 marks the beginning of active development. The primary focus will be on building the core components of the rover’s software. This sprint will lay the foundation for the project by implementing essential features such as the core algorithms for navigation, sensor integration, communication protocols, and initial testing frameworks.
The team will prioritize developing critical components that other features depend on, such as the state machine and basic rover control logic. This sprint also includes setting up initial data pipelines, ensuring that sensor data can be properly captured and processed. The goal is to ensure that by the end of this sprint, the rover's software has a basic level of functionality that can be expanded upon in subsequent sprints.
- Start Date: October 21, 2024
- Due Date: November 10, 2024
Description:
Sprint 2 focuses on testing and refining the work completed in Sprint 1. During this phase, the team will conduct extensive unit testing, integration testing, and initial field tests to validate that the core components are functioning as expected. Bugs and other issues that arise during testing will be identified, logged, and addressed.
This sprint is also an opportunity for early refinement of features based on feedback from testing. The team will assess areas of the code that may need improvement, such as performance bottlenecks, poorly performing algorithms, or unoptimized sensor integration. The goal is to ensure the code is stable and robust before moving on to more complex feature development.
- Start Date: November 11, 2024
- Due Date: December 01, 2024
Description:
Sprint 3 is dedicated to completing the major features planned for the first semester. This sprint will focus on the development of the remaining core functionalities that were not fully completed in earlier sprints. The aim is to ensure that all the planned features are implemented by the end of this sprint, and the rover is operational with its primary systems.
In this phase, the team will finalize critical features like autonomy, navigation, obstacle detection, and other essential capabilities. Sprint 3 also includes ensuring that all components are properly integrated and working together harmoniously. The codebase should be stable, with most of the core functionality complete by the end of this sprint.
- Start Date: December 02, 2024
- Due Date: January 26, 2025
Description:
During Sprint 4, the team will shift its focus from feature development to performance optimization. This sprint aims to refine the software's efficiency by reducing resource consumption, optimizing algorithms, and eliminating any performance bottlenecks that could affect the rover’s operations during competition.
Additionally, bug fixes from testing in earlier sprints will be addressed, and the team will focus on improving the responsiveness and reliability of the software. Documentation updates will also be prioritized to ensure that any changes or optimizations made are well-documented for future reference.
The goal by the end of this sprint is to have a highly optimized, efficient system that performs well under the constraints and demands of the competition environment.
- Start Date: January 27, 2025
- Due Date: February 23, 2025
Description:
Sprint 5 is all about integrating the simulator with the rover’s software. The team will work on linking the software to a simulated environment that mirrors real-world conditions. This will enable the team to perform in-depth testing without needing physical access to the rover, allowing for more efficient troubleshooting and experimentation.
The simulator will be used to validate the behavior of the autonomy software, navigation algorithms, and other core functionalities under various conditions. The primary goal is to ensure that the software performs correctly in the simulated environment and that any integration issues between the simulator and the software are resolved.
- Start Date: February 24, 2025
- Due Date: April 27, 2025
Description:
Sprint 6 focuses on performing the final rounds of testing and refinement. The team will conduct thorough end-to-end tests of the entire rover system to ensure that all features are functioning as expected. This sprint will involve rigorous field testing in real-world conditions, as well as stress testing to identify any potential failure points.
Any remaining bugs or issues will be addressed, and the team will work to polish the final product. The goal of this sprint is to finalize the software and ensure that it is competition-ready by the end of the semester.
- Start Date: April 28, 2025
- Due Date: May 25, 2025
Description: February 24, 2025 Sprint 7 is dedicated to finalizing the rover’s software and preparing for the release version that will be used in the URC competition. The team will work on any final polishing that is needed, including minor bug fixes and ensuring that all systems are fully functional.
This sprint will also involve preparing all final documentation, including user manuals, API documentation, and any materials required for the competition. The primary goal is to ensure that everything is ready for a smooth handoff to the competition phase.
- Start Date: May 26, 2025
- Due Date: June 01, 2025
Description:
Sprint 8 focuses on conducting a project retrospective. The team will meet to review the entire development process, identifying areas of success and opportunities for improvement. This sprint will also address any remaining maintenance tasks or last-minute fixes before the rover is finalized for competition.
The retrospective will help the team capture valuable lessons learned throughout the project, which can be applied to future competitions or development cycles. The goal of this sprint is to ensure that the team is well-prepared for the URC competition and future endeavors.