Sprint 7-8 Report: July 14 - July 24

Link to project board

Executive Summary

As we conclude Sprints 7 and 8, our primary focus has been on the final steps to close out Phase 1. A critical part of this effort is testing the automation pipeline from Claude to AWS deployment. Finalizing this process is a key dependency for its full implementation into our workflow, which will enable us to achieve our goal of rapid development and feature fulfillment.

Team contributions this sprint were significant and aligned with our core objectives:

Maka is continuing development on the 'learning objective agent,' the highest priority application for VIDA. Her work continues to evolve based on insightful feedback from Dena, ensuring the final product meets its strategic goal of engaging with Instructional Designers (IDs).

Eric is making steady progress in familiarizing himself with the VIDA development process. His integration into the team workflow is expanding our overall resource capacity for application development.

Kenny continues to maintain and share the project's status with the team. A priority for him is mirroring our GitHub repository with Monday.com to help automate status reporting and maintain a single source of truth. Kenny is also leading the vision and design for the future landing pages of vidahub.io.

In an effort to improve our internal processes, we have successfully implemented a weekly Show and Tell meeting at the end of each sprint. This new forum has already proven beneficial for our review process, allowing the team to collaborate more effectively on features and celebrate progress.

Additionally, we have identified that our sprint planning and check-in meetings require more time. The current one-hour slot is often fully consumed by reviewing, prioritizing, and planning, leaving little room for deeper work-related discussions. To address this, Kenny will propose extending these meetings at the start, ensuring we can cover all necessary topics while respecting everyone's time.

Looking forward, we are evaluating a potential shift from Claude to VS Code Copilot for our 'natural language to code' feature. This would represent a significant change in our toolset, and initial documentation will need to be created to explore and manage this transition.