Structured chaos into a working system
When I joined, the team was using GitHub issues as the sole project tracking tool — adequate for dev but not for cross-functional visibility or client reporting. I migrated the entire workflow to Jira and implemented SCRUM: two-week sprints, daily standups, sprint reviews, and retrospectives.
This gave the team a shared source of truth, made blockers visible early, and created a rhythm the client could follow. The result: a project that stayed on schedule across a 5-month engagement with a six-person cross-functional team.
- Migrated project tracking from GitHub Issues to Jira
- Implemented SCRUM with 2-week sprints, standups, and retrospectives
- Managed 1 designer and 5 developers across the full project lifecycle
- Maintained sprint velocity and flagged scope risks before they became delays
Kept the client informed and in control
Fleo's stakeholders were non-technical, but they needed confidence in a technically complex migration. I owned the client relationship throughout: weekly status calls, structured progress reports, and clear escalation paths when decisions were needed.
Rather than shielding the client from complexity, I translated it — turning sprint updates into business-relevant milestones they could track and approve. This built trust and reduced scope creep caused by last-minute surprises.
- Ran weekly client calls with structured agendas and decision logs
- Produced clear progress reports tied to business milestones, not dev tasks
- Managed scope changes through a formal change request process
- Resolved client concerns before they escalated into project risks
