

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.