Sprint Goal: The purpose of the sprint is to complete the project report and analysis. Project housekeeping is also included with tasks such as refactoring, cleanup and release.
The sprint took two weeks instead of one. It was responsible of one larger task, and since I prefered each sprint to have a single, well-defined focus, I decided not to split it into two sprints.
Key Deliverables:
- Complete project report and documentation
- Project housekeeping tasks such as refactoring, cleanup and release
- Since the project is almost complete and the code is stable, the ArchUnit tests are finalized.
- The visualization analysis is finalized.
Task Board
Link to the main product backlog: Product Backlog
| SBI ID | Task Description | User Story | PBI ID | Est. Points | Status |
|---|---|---|---|---|---|
| TESTING & QUALITY ASSURANCE (15 Points) | |||||
| S5.1.1 | Implement testing strategy (ArchUnit, acceptance test) | Testing | E4 | 5 | ✓ (tests) |
| S5.1.3 | Define quality metrics (PCA, Pairwise) | Testing | E4 | 5 | ✓ (report) |
| VISUALIZATION & ANALYSIS (15 Points) | |||||
| S5.2.1 | Visualize code embeddings for quality analysis | Visualization | E5 | 5 | ✓ (scatter) |
| S5.2.2 | Provide metrics on search effectiveness | Visualization | E5 | 5 | ✓ (pair-wise) |
| S5.2.3 | Generate insights for documentation | Visualization | E5 | 5 | ✓ |
| DOCUMENTATION (15 Points) | |||||
| S5.3.1 | Create user documentation | Documentation | E6 | 5 | ✓ |
| S5.3.2 | Generate project report | Documentation | E6 | 5 | ✓ |
| S5.3.3 | Document architecture and design decisions | Documentation | E6 | 5 | ✓ |