Mini UI Sprint on Gotto Job: Jira, Git, and AWS EC2 Deployment
In this post, I’ll walk you through how I executed a mini UI sprint for the Gotto Job platform. The project focused on UI-only improvements, Agile sprint execution using Jira, incremental delivery with Git, and deployment on AWS EC2.
This article is practical for beginners looking to understand real-world DevOps workflows and also recruiter-friendly for showcasing project experience.
Project Links
- Live EC2 URL: http://3.95.61.148/
- GitHub Repo: https://github.com/vivianokose/gotto_job-vivian-chiamaka-okose.git
Project Goal
Objective: Ship visible UI improvements to enhance clarity, discoverability, and trust on the platform.
Key improvements included:
- Hero tagline clarity
- Primary CTA button color update
- Footer trust links (About & Contact)
Roles & Mode Setup
Mode: Solo (played all Scrum roles)
| Role | Notes |
|---|---|
| Product Owner | Prioritized high-impact UI changes |
| Scrum Master | Ensured process via daily Jira updates |
| Dev Lead | Built UI-only edits (text, spacing, colors) |
| DevOps Lead | Shipped changes to EC2 and verified live |
Lesson Learned: Even in solo mode, clear role definitions improve accountability.
Jira Workflow
-
Create Team-managed Scrum project:
Gotto Job – Vivian Okose - Create Epic: "Improve Gotto Job UI discoverability & trust"
- Seed backlog with 6 key stories (1–3 story points each)
- Conduct Planning Poker for estimation
- Create Sprint 1 and assign 3–4 stories with subtasks: Build → Verify → Deploy
Lesson Learned: A well-organized backlog ensures clarity and prevents delivery chaos.
Story & Subtask Breakdown
Each story was split into subtasks for incremental delivery:
- Build
- Verify
- Deploy
Lesson Learned: Breaking work into smaller tasks simplifies tracking and deployment.
Git Workflow
Implemented changes in feature branches:
bash
git checkout -b feature/hero-tagline
git add .
git commit -m "feat(ui): update hero tagline for clarity"
git push origin feature/hero-tagline
Top comments (0)