A Sprint Review is conducted at the end of each sprint (weekly or bi-weekly) to demonstrate completed work, gather feedback, and update the backlog accordingly.
Sprint 01 Goals and Status
Sharing Insights
During the Sprint Review, teams should also discuss:- Blockers encountered during development
- Novel challenges or key learnings that can improve our DevOps pipeline
- Suggestions for refining workflows in upcoming sprints
If a blocker persists past the sprint boundary, raise it immediately in the backlog refinement meeting to avoid delays in future sprints.
Next Steps
With Sprint 01 wrapped up, our focus shifts to:- Sprint 02 Planning: Defining scope for containerizing the Flask app with Docker.
- CI/CD Integration: Configuring GCP Cloud Build triggers for automated deployments.
- Infrastructure as Code: Writing Terraform scripts to provision networking and compute resources on GCP.