Have you ever wondered what it really takes to move a single feature from a Jira ticket all the way into production?
That was exactly the challenge I faced in Week 3 of my DevOps Micro-Internship—a 5-day solo Scrum sprint where I had to plan, code, deploy, and troubleshoot on an AWS EC2 instance.
🎯 Sprint Goal: Deploy a visible footer showing version, date, and author details on the Mini-Finance app hosted on EC2.
🗓️ Sprint Breakdown
✅ Day 1 | The Launchpad
Jira was my mission control. I broke down one Epic into Stories and Subtasks.
First commit: created the footer’s HTML.
Provisioned an EC2 instance, installed Nginx, and configured the web root.
✅ Day 2 | The Polish
Fixed broken image paths and cleaned up CSS for proper rendering.
Transferred updated files to the server with SCP.
Learned the importance of nginx -t before reloading—saves headaches!
✅ Day 3 & 4 | Visibility + Reliability
Ensured the footer was responsive across devices.
Added a /healthz endpoint to check service availability.
Lesson learned: small, daily increments made testing smoother and reduced rollback risks.
✅ Day 5 | The Retrospective
Footer live and sprint goal achieved.
Captured burndown and demo deployed successfully.
📌 Reflections
What went well
Clear acceptance criteria
Incremental delivery
What needs improvement
Automating deployments with CI/CD in the next sprint
Scrum in action
Transparency. Focus. Commitment.
🔑 Key Takeaway
This week wasn’t just about shipping a footer. It was about end-to-end ownership—planning, fixing, configuring, deploying, monitoring, and improving. That, to me, is the essence of DevOps.
⚙️ Tech Stack
AWS EC2 • Ubuntu • Nginx • Jira • Git • SCP • HTML/CSS
A big thank you to Pravin Mishra for structuring such a practical internship, and to mentors like Praveen Pandey, Anisa Bibi, and the DMI community for their support.
I’m excited to carry this ship-to-production mindset forward as I grow in the Cloud & DevOps space.
Top comments (0)