Hands-On DevOps: From Jira Sprint to Live Deployment on AWS EC2
In this assignment, I practiced a real DevOps workflow by running a mini Scrum sprint in Jira, implementing a small improvement to a portfolio website, and deploying the change to a live server on AWS EC2.
Rather than a big-bang release, the focus was on shipping small, incremental updates daily, tracking progress in Jira, and verifying each change on a public URL.
The improvement was simple but meaningful:
Pravin Mishra Portfolio v1.0 — Deployed on
This footer was added to the website and deployed live to an EC2 instance.
🎯 Sprint Goal
The sprint goal defined in Jira was:
Ship a visible "Pravin Mishra Portfolio" footer (version + deploy date + author) to EC2 and document progress daily in Jira.
This simulated how real engineering teams commit to a measurable outcome for each sprint.
🧩 Sprint Setup in Jira
The sprint was managed using the following workflow:
Create a Story in Jira
Break it into 5 daily subtasks
Track daily updates using Daily Scrum comments
Move tasks across the board
Track progress using the Burndown Chart
Subtasks created:
Day 1 — Implement footer & deploy
Day 2 — Make deploy date dynamic
Day 3 — Polish UI & improve accessibility
Day 4 — Update homepage tagline
Day 5 — Demo + retro + review burndown
This structure ensured that progress was visible and measurable every single day.
🏗️ DevOps Workflow Used
The workflow followed a typical DevOps pipeline:
Code changes locally
Commit using Git
Deploy to EC2
Verify on public website
Update Jira ticket
📊 Project Workflow Diagram
text
┌─────────────────────────┐
│ Jira Sprint │
│ Story + Subtasks │
│ Daily Scrum Updates │
└────────────┬────────────┘
│
▼
┌─────────────────────────┐
│ Local Development │
│ Edit HTML/CSS/JS │
│ Add Footer Feature │
└────────────┬────────────┘
│ Git Commit
▼
┌─────────────────────────┐
│ Git Repo │
│ Version Control │
│ Feature Branch │
└────────────┬────────────┘
│ Deploy via SCP
▼
┌─────────────────────────┐
│ AWS EC2 Server │
│ Nginx Web Server │
│ Portfolio Website │
└────────────┬────────────┘
│ Public Access
▼
┌─────────────────────────┐
│ Live Website │
│ Footer Version Visible │
│ Deploy Date + Author │
└─────────────────────────┘
⚙️ Day-by-Day Sprint Execution
Day 1 — Implement Footer and Deploy
The first task was to add a footer section to the HTML template:
html
Pravin Mishra Portfolio v1.0 — Deployed on 09 Mar 2026 — By Manjay
After implementing the footer:
Changes were committed using Git
The site was deployed to EC2
The footer appeared on the live website
This step validated the end-to-end delivery pipeline.
Day 2 — Make Deploy Date Dynamic
To improve the feature, the deploy date was generated automatically using JavaScript:
html
const d = new Date();
const options = { day: '2-digit', month: 'short', year: 'numeric' };
document.getElementById("deployDate").innerText =
d.toLocaleDateString('en-GB', options);
Now the footer automatically displays the current deployment date, eliminating manual updates.
Day 3 — UI Polish and Accessibility
The footer was enhanced for better usability and accessibility:
Improvements included:
Increased padding
Better font size and contrast
Responsive layout testing
The UI was verified on both desktop and mobile views using browser DevTools.
Day 4 — Update Homepage Tagline
The homepage text was updated to promote the DevOps learning community:
Join DMI Cohort 3 on Discord and start your DevOps journey
This change improved community visibility and engagement.
Day 5 — Demo, Retro, and Burndown Review
The final day focused on reviewing the sprint:
Activities included:
Recording a demo of the live website
Showing the footer with version, date, and author
Reviewing the burndown chart in Jira
Writing retrospective notes
Retrospective Example:
What went well What to improve
Daily incremental updates helped maintain momentum Automating deployment using CI/CD would improve efficiency
DevOps principle observed: Continuous Delivery
📈 Key DevOps Learnings
This assignment demonstrated several important DevOps practices:
1️⃣ Incremental Delivery
Instead of one large change, small improvements were delivered daily, reducing risk and enabling faster feedback.
2️⃣ Traceability
Every change was tracked in Jira and linked to the user story, creating a clear audit trail.
3️⃣ Deployment Proof
Each change was verified on a public EC2 URL, confirming that the feature worked in production.
4️⃣ Agile Collaboration
Using stories, subtasks, and daily scrum updates mirrors how real Scrum teams operate.
🌍 Final Result
By the end of the sprint:
✔ A visible footer was deployed
✔ The deploy date was automated with JavaScript
✔ UI was polished and accessibility improved
✔ The homepage tagline was updated
✔ All changes were tracked through Jira
✔ The website was live on EC2
This exercise demonstrated how Agile + DevOps workflows help teams ship reliable improvements quickly and consistently.
💡 Final Thoughts
This mini sprint highlighted a fundamental principle:
Small daily improvements with proof are better than one large delayed release.
By combining Jira sprint management, Git version control, and EC2 deployment, this assignment simulated a real-world DevOps delivery cycle — proving that even simple improvements can teach powerful lessons when executed with the right processes.
Top comments (0)