As part of the DevOps Micro Internship (DMI) Cohort 3 with Agentic AI, I had the opportunity to work through a series of hands-on assignments that helped me understand how Agile, Scrum, Jira, Git, AWS EC2, and DevOps practices come together in a real delivery workflow.
What started with simply setting up a Jira account gradually evolved into planning sprints, managing backlogs, deploying applications, tracking progress, and delivering working increments.
Getting Started with Jira
The journey began with setting up my Jira Software Cloud account and creating a professional Jira profile.
I explored Jira dashboards, projects, boards, and backlogs to understand how teams use Jira for Agile collaboration and work tracking.
This provided the foundation for the assignments that followed.
Building a Scrum Environment
The next step was to create a complete team-managed Scrum project for the DevOps Micro-Internship website.
I created:
A Jira Scrum Space
An Epic β βPolish DMI Website UI & Deployβ
Six user stories
Story-point estimates using Fibonacci values
Acceptance criteria using Gherkin
Frontend and DevOps labels
Sub-tasks for development, testing, deployment, and verification
Sprint 1 with a Sprint Goal
Filters and the Burndown Chart
This helped me understand how a requirement can move from a high-level Epic into smaller, actionable pieces of work.
Running a 5-Day Mini-Sprint
This took the learning from planning to actual delivery.
Over a five-day mini-Sprint, I worked on a portfolio website improvement and deployed the changes to an AWS EC2 environment.
The increment included:
Adding a portfolio footer with version, deployment date, and author
Making the deployment date dynamic
Improving spacing, readability, contrast, and mobile responsiveness
Adding a DMI call-to-action
Committing changes through Git
Deploying and verifying the changes on EC2
Maintaining Daily Scrum updates
Completing a retrospective
Tracking Sprint progress through the Jira Burndown Chart
I also created a demo video and published the work on LinkedIn as part of the delivery story.
Gotto Job β Backlog Refinement & Sprint 1
The fourth assignment introduced a more realistic product backlog refinement and Sprint planning exercise using the Gotto Job website.
I worked in Solo Mode, taking responsibility for the different Scrum roles:
Product Owner: Prioritized the highest-value UI improvements.
Scrum Master: Ensured the Sprint process, estimation, and tracking were followed.
Dev Lead: Implemented the selected UI improvement.
DevOps Lead: Managed Git, deployment, verification, and delivery.
I created an 8-story backlog with a total of 11 story points and estimated the stories using Fibonacci values of 1, 2, and 3.
The backlog included improvements such as:
Hero tagline
Button color
Job card typography
REMOTE badge
Posted-on date
Search labels
Apply Now button
Footer trust links
I then selected stories for Sprint 1, created Build, Verify, Deploy, and Screenshot sub-tasks, opened the Burndown Chart, and shipped a small UI-only increment to the live application.
π‘ What I Learned
The biggest learning from these assignments was that DevOps is much more than deployment and automation tools.
I experienced the complete flow:
Requirement β Backlog β Estimation β Sprint Planning β Development β Git β Deployment β Verification β Tracking β Retrospective
I also learned the importance of breaking large requirements into smaller deliverable pieces, estimating work realistically, maintaining transparency through Jira, and continuously verifying what has been delivered.
Most importantly, these exercises helped me understand how Agile and DevOps complement each other. Scrum provides the structure for planning and prioritization, while DevOps practices enable faster, repeatable, and reliable delivery.
π From Learning to Doing
The DMI Cohort 3 assignments gave me an opportunity to move beyond theoretical learning and actually build, track, deploy, verify, and communicate software delivery.
Working with Jira, Git/GitHub, AWS EC2, Nginx, Scrum, Sprint planning, Burndown Charts, and CI/CD-oriented practices has strengthened my understanding of end-to-end DevOps delivery.
This journey has reinforced one principle for me:
Plan the right work, deliver it incrementally, verify it continuously, and improve with every Sprint.
This post is part of the DevOps Micro Internship (DMI) with Agentic AI β Cohort 3 β by Pravin Mishra.
My graded progress is public: https://dmi.pravinmishra.com/s/DMI-C3-CharanTeja.html
Start your DevOps journey: https://dmi.pravinmishra.com/?utm_source=student&utm_medium=ps-blog&utm_campaign=cohort3
Top comments (0)