This week, I executed a complete Scrum Sprint lifecycle using Jira Cloud (team-managed project) — covering backlog refinement, sprint planning, delivery, deployment, reporting, and retrospective.
The focus was not on theory, but on end-to-end execution: planning work, shipping a production change, and providing verifiable proof.
Project Context
Project: Gotto Job (UI-only enhancements)
Methodology: Scrum (Team-managed, Solo execution)
Core Tools: Jira Cloud, Git, GitHub, EC2 (Ubuntu), Nginx
Scope: Small, high-impact UI improvements delivered incrementally
Scrum Roles & Ownership (Solo Execution)
To mirror real delivery accountability, I assumed all Scrum roles:
Product Owner: Prioritized UI changes with the highest user-perceived value
Scrum Master: Enforced Scrum cadence (refinement → planning → sprint → retro)
Dev Lead: Implemented UI changes with clear acceptance criteria
DevOps Lead: Deployed changes to a live environment and validated delivery
Outcome: Clear separation of concerns, even in solo mode.
Backlog Refinement & Estimation
I created a structured product backlog under a single Epic:
Epic: Improve Gotto Job UI discoverability & trust
6+ user stories
Clear acceptance criteria
Fibonacci estimation (1/2/3)
Ranked by business value
This ensured the sprint scope was predictable and executable.
Sprint Planning (Sprint 1)
Defined a clear Sprint Goal
Selected 3–4 small, deliverable stories
Broke stories into actionable subtasks:
Build
Verify
Deploy
Screenshot (proof)
Focus: Deliver visible value, not partial work.
Delivery & Deployment (DevOps Execution)
One story from Sprint 1 was fully implemented and shipped:
Code changes committed with meaningful Git messages
Repository deployed on EC2 using Nginx static hosting
Live URL verified
Jira issues transitioned across the workflow to Done
Deployment proof attached
This followed a real DevOps loop:
Plan → Build → Ship → Verify → Document
Reporting & Transparency
Enabled and reviewed the Burndown Chart
Used Jira reports to track sprint health and scope
Ensured delivery visibility at all stages
Sprint Retrospective
A structured retro was documented, covering:
What went well
What to improve
Scrum pillar observed: Transparency
Scrum value demonstrated: Commitment
This reinforced continuous improvement, not just delivery.
Why This Matters (DevOps Perspective)
This sprint demonstrated practical capability in:
Agile execution with Jira (not checkbox usage)
Backlog refinement and estimation discipline
Shipping small, safe increments
Infrastructure + deployment ownership
Evidence-based delivery (live URL + Jira + GitHub)
Links
Live Deployment:
GitHub Repository: https://github.com/Lucycloud2024/GOTTO-JOB-DEMO
Final Note
This assignment strengthened my ability to operate in a real delivery environment, where planning, execution, deployment, and visibility are equally important.
I’m now comfortable contributing to teams that value small batches, fast feedback, and measurable delivery.
Top comments (0)