Sticky Notes and Scrambled Nerves: The Retro That Launched My Agile Journey

I had just stepped into a completely new role, Scrum Master. New team, new expectations, and a craft I was still learning. I was still wrapping my head around the role, yet here I was expected to lead a team of seasoned professionals.

The team was a blend of experienced developers and sharp business minds people who had already acquired their craft and knew exactly what they wanted. Everyone, except me. I was still figuring out where the sticky notes were kept.

It was a retro day. The team had a culture of arriving early and so had most of them on this day. I was just about to swipe my card on the ground floor to summon the lift to the 5th when my phone rang. A new caller. I hesitated, then picked up. It was Stacy, my peer buddy. She casually said, “Nilikuwa nakuambia leo sikuji.” “Ni nani?” “Ni Stacy.” I froze. Of all days, why today?

I didn’t ask why she was absent. Empathy didn’t even cross my mind. All I could think was: “Retro is in minutes. I’ve never done one before. How do I even start?” The elevator seemed to double its speed, maybe it sensed my panic. I got to the 5th floor. The team was already seated. All eyes on me. My voice was the missing piece to get this running.

To make matters worse, I hadn’t even figured out where the sticky notes were stored. Yes, the very tools of the trade were missing in action. I stood there, clearly flustered, when one of the front-end engineer kind, observant, and probably a part-time mind reader, sensed my woes from a distance. He looked at me and asked, “Mwenzako hakuji?” I nodded, “No.” Without hesitation, he dashed to the lockers, pulled out a bunch of sticky notes and pens, and said, “Let’s use these.” That was my messiah of the moment. Or so I thought.

I stood there, heart racing, trying to remember everything I’d read about retrospectives. I didn’t have a script. I didn’t have a backup plan. But I had a team that was ready, a bunch of sticky notes, and a developer who had my back. So, I leaned in.

Truthfully, I can’t remember much about how the retrospective itself went. I doubt we had any structured format beyond the classic “What went well, what went wrong.” I fumbled. I made awkward jokes. No sugarcoating it. I was nervous, unsure, and probably said “let’s just go with the flow” more times than I should have.

But looking back, I’m glad I did it. That moment awkward, unpolished, and raw was necessary. It was the beginning of learning by doing. I didn’t need a perfect plan. I needed the experience. And that’s exactly what I got.

💡 Lessons Learned:

• Show up, even when you’re unsure. Leadership starts with presence, not perfection.
• Empathy is a muscle. I didn’t use it that day, but I’ve learned to since
• Lean on your team. Agile is collaborative help often comes from unexpected places.
• Don’t fear the fumble. Every misstep is a step toward mastery.
• Start simple. Even “What went well, what went wrong” can spark meaningful insights.
• Reflect often. Retrospectives aren’t just for the team they’re for you too.

That day taught me more than any Agile course ever could. It was messy, real, and transformative. I didn’t have all the answers honestly, I barely had the sticky notes, but I had the courage to show up, and the humility to learn in real time. And that, I’ve come to learn is the essence of Agile leadership.