GCP DevOps Project
Sprint 01
Sprint 01 review
Welcome to our Sprint 01 Review! In this lesson, we’ll recap the goals we set at the start of the sprint, highlight our achievements, share key insights, and outline next steps for our GCP DevOps project.
Note
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
| Goal | Description | Status |
|---|---|---|
| Initialize a GitHub repository | Create and configure a new repo on GitHub | ✅ Completed |
| Clone the repository locally & apply DevOps best practices | Set up branching strategy, CI/CD templates | ✅ Completed |
| Develop a simple Python Flask application | Scaffold a “Hello, World!” Flask web service | ✅ Completed |
| Test the application locally & resolve issues | Run unit tests, lint code, debug errors | ✅ Completed |
| Push the completed code back to GitHub | Commit changes and push to the main branch | ✅ Completed |
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
Warning
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.
Stay tuned for the next lesson, where we’ll dive into Dockerizing our Python Flask application and setting up a CI/CD pipeline on Google Cloud Platform.
References
Watch Video
Watch video content