Meeting Date: Mon May 18 2026
Source: Google Doc Link
Summary
Sprint retrospective addressed process improvements and communication strategies while formalizing daily standup meetings for team alignment.
Sprint Successes and Standups
Team members identified successful project patterns for maintenance. Participants resolved to implement concise daily standups to improve consistent communication.
Documentation and Collaboration Standards
Process documentation is now mandatory to prevent burnout. The group established weekly sync meetings to enhance cross-team coordination.
Partnerships and Technical Protocols
Future agreements will include firmer cancellation clauses via email. Technical tasks must prioritize individual file uploads to ensure environment stability.
Rate this Summary: Helpful or Not Helpful
Suggested Next Steps
- [The group] Discuss Certificate: Discuss the certificate with Kentila after the meeting scheduled for tomorrow.
- [Menla Tsomo] Coordinate Tech Chats: Coordinate timely chats with the tech team to prevent working in isolation.
- [The group] Update GitHub: Ensure project status and research updates are documented on GitHub every 2 to 3 days. Use the comment section for issues and apply labels to categorize content.
- [The group] Schedule Weekly Sync: Schedule a weekly sync meeting between the course team and the masterclass team.
- [Norbu Tsering] Upload Videos: Upload video components one by one instead of in bulk.
- [Tenzin Palkyi] Update MOU Clauses: Update Memorandum of Understanding templates to include stern cancellation clauses for future partnerships.
Details
- Sprint Retrospective Introduction: Tenzin Palkyi initiated the first sprint retrospective by introducing the “calm model” to review the work completed over the previous two weeks. Participants were allocated 15 minutes to brainstorm and input their reflections into a shared document.
- Team Availability and Logistics: The team acknowledged that VA was unable to attend the meeting due to teaching commitments. Participants confirmed they were able to access the shared link to collaborate on the retrospective notes.
- Sprint Retrospective - “Keep” Section: The team identified successful work patterns to maintain, specifically the “Buddha moment” challenge and the professional execution of the personalization layout and clarification sessions. They also noted that the identification and testing of technical solutions for uploading interactive video components were successful accomplishments that should be maintained.
- Daily Standup Implementation: The team discussed the need for consistent communication, particularly through daily standups. They resolved to implement daily standups for the influencer and masterclass teams, noting that the course team already holds these meetings at 9:15. It was agreed that these meetings must remain concise, ideally lasting no longer than 15 minutes, to ensure efficiency.
- Documentation and Process Continuity: Tenzin Palkyi emphasized that team members should focus on refining work processes rather than focusing solely on individual task lists. To prevent burnout and ensure continuity when team members are absent, the group decided that all processes must be thoroughly documented and shared with the entire team.
- Collaboration with the Tech Team: Yash Dixit and Norbu Tsering highlighted the necessity of maintaining better communication with the tech team to avoid working in isolation. They discussed the importance of understanding the operating system and features, citing a recent voice interference issue on the app. The group decided to establish a consistent schedule for connecting with the tech team to ensure smoother collaboration.
- Weekly Team Synchronization: To improve cross-team coordination, the group decided to implement a weekly sync meeting involving both the course team and the masterclass team. This will allow members to update each other on progress and ensure that everyone is aligned on organizational goals.
- External Partnership Standards: Yash Dixit recommended that the team adopt a sterner approach when collaborating with external organizations to prevent being taken advantage of. The team agreed to include firmer cancellation clauses in future Memorandums of Understanding and to move away from making major partnership decisions over informal channels like WhatsApp, opting for email correspondence instead.
- Team-Building Activities: The group discussed the importance of interactive team-building activities to foster connections and strategic functioning. While they agreed these activities are beneficial, Abha Achal requested that the team avoid involving the Human Resources department in the planning of these sessions.
- GitHub Maintenance and Best Practices: Norbu Tsering admitted to a lapse in keeping GitHub updated during the previous sprint. Menla Tsomo provided guidance on best practices, suggesting that team members utilize the comment section on tickets to provide updates and apply specific labels, such as “research” or “feature,” to ensure transparency and ease of review for team leads.
- Reflection on Collaboration Philosophies: Tenzin Palkyi reflected on the difficulties experienced with partners like Tri Ratna, noting the need to balance firm boundaries with maintaining a positive reputation. Menla Tsomo reminded the team that their previous diligence in requesting information from coaches helped them establish a reputation for high-quality, hard work.
- Post-Meeting Technical Coordination: Following the retrospective, Menla Tsomo and Norbu Tsering coordinated on the technical execution of video uploads. They decided to upload content one by one rather than in bulk to ensure consistency and stability within the production environment.
How is the quality of these specific notes? Take a short survey to let us know your feedback, including how helpful the notes were for your needs.