This Weekly Recap Template is designed for technical and engineering teams to efficiently summarize progress, highlight challenges, and plan for the upcoming week. It addresses the pain points of fragmented technical discussions and helps maintain a clear record of team activities, making onboarding smoother and decision-making more transparent.
Team & Reporting Period
Backend Services Team / Project Phoenix
Specify the team or project this recap pertains to.2023-10-23 to 2023-10-27
Indicate the start and end dates of the reporting week.Jane Doe (Lead Developer)
Enter the name and role of the person preparing the recap.Key Achievements & Progress
- Implemented user authentication service (JIRA-123)
- Deployed API Gateway v2 to staging
- Reviewed 5 pull requests for sprint 3
List major tasks, features, or tickets completed, including relevant ticket IDs.- Code coverage increased from 75% to 78%
- P99 latency reduced by 50ms for critical endpoints
- 99.95% uptime maintained for Production environment
Note any significant improvements in relevant metrics or KPIs.- Completed 15 PR reviews, averaging 2h turnaround time
- Updated API documentation for 'Order Management' service
- Drafted runbook for 'Database Migration' process
Summarize contributions to code reviews and documentation efforts.Challenges & Blockers
- Awaiting security review sign-off for new payment module
- Infrastructure provisioning delay for new Kafka cluster
- Unresolved merge conflict in 'feature/async-processing' branch
Detail any issues currently preventing progress, including who is responsible.- Legacy logging system needs refactoring
- Missing unit tests for 'Notification' service
- Outdated dependencies in 'Frontend UI' repository
List any significant technical debt discovered or prioritized.- Discovered a performance bottleneck in ORM queries
- Need to improve communication between Frontend and Backend teams during sprint planning
Document key lessons learned or points for process improvement.Upcoming Week & Action Items
- Begin integration testing for 'Search' microservice
- Finalize deployment strategy for new monitoring stack
- Participate in architectural review for 'Data Lake' expansion
Outline the primary objectives and tasks for the next reporting period.- Need SRE team to provision new database instances by EOD Tuesday
- Awaiting design mockups for 'User Dashboard' v2 from Product team
Specify any external dependencies or requests for other teams.- Risk: Potential delay in third-party API integration. Mitigation: Explore alternative API providers.
- Risk: High team burnout. Mitigation: Prioritize critical tasks, delay non-essential work.
Identify potential risks for the upcoming week and proposed mitigation strategies.Decisions & Action Items
- Decided to use Kubernetes for new service deployments (instead of ECS)
- Approved usage of Serverless functions for specific async tasks
Record any significant technical or architectural decisions made.- John D.: Research alternative caching solutions (due 2023-11-03)
- Sarah K.: Schedule a meeting with Security team for module review (due 2023-11-01)
List specific actions resulting from the recap, including owner and due date.How to Use This Template
- Create a new CraftNote document and select the 'Weekly Recap Template'.
- Fill in the 'Team & Reporting Period' details to set the context for your recap.
- Document 'Key Achievements & Progress', including specific tasks, metrics, and code review contributions from the past week.
- Clearly outline 'Challenges & Blockers', any identified technical debt, and team learnings to foster transparency and problem-solving.
- Plan for the 'Upcoming Week' by listing planned tasks, dependencies, and potential risks, then record 'Decisions & Action Items' for clear follow-through.
Customization Tips
- Add specific sections for different engineering disciplines, such as 'Data Pipeline Status' for data engineers or 'Infrastructure Changes' for DevOps teams.
- Integrate links to relevant JIRA tickets, GitHub pull requests, Confluence pages, or monitoring dashboards for easy reference and deeper context.
- Adjust the 'Metrics/KPIs Achieved' field to align with your team's specific sprint goals, OKRs, or service level objectives (SLOs).