Stepping into an organization that runs purely on waterfall felt like walking into a library where everyone whispers — and then suddenly turning on loud music. 
But instead of chaos, I saw an opportunity: to build something fresh, dynamic, and collaborative with Agile. And so, the journey begins.
In just a month, I’ve made solid progress:
Scrum team structure set up (roles, sprint length, ceremonies)
Training materials prepared — light, visual, and practical
Agile boards built using Microsoft Lists for transparency (temporary solution until Jira is ready)
Metrics identified: velocity, burndown, cycle time
Collaborative conversations with internal teams and vendors
The biggest challenge so far? Shifting mindsets. Most teams are used to operating in silos — working quietly, independently, and by the book. Agile asks them to think openly, iterate often, and talk more. That takes time.
But we’re planting the seeds. And the small shifts are already visible — more questions in standups, more shared ownership, and even a few “This actually works!” moments.
Looking ahead, I’m gearing up for:
A fun, interactive Agile roadshow (games, quizzes, posters)
KPI dashboards to visualize progress and spark motivation
Internal buzz: Agile wins, weekly tips, and small wins celebrated
One month in, and it feels like we’re on the edge of something exciting. 
The journey’s just getting started.
