I came in as Scrum Master expecting to mostly run standups and keep the backlog clean. What it turned into was my first real experience leading a project technically — making the architecture calls, owning how we shipped, and constantly weighing what would be fun to build against what a small organization with no engineers could actually keep running after we left.
WhatsApp was the clearest example. We could have stopped at a chat widget on the website and it would have looked good in a demo. But the people Housing Assembly serves are on their phones, and WhatsApp is what they already open every day, so we spent weeks getting it working properly there instead. That's the lesson I keep coming back to: the best decision usually isn't the most impressive one, it's the one that meets people where they already are. Same reason we built a way for staff to update the document library themselves — anything that needed a developer was going to quietly stop being used the day we flew home. The moment that stuck with me wasn't a deploy going green. It was watching Kenneth and Kashiefa move through the chatbot during testing without needing us to explain a thing.
Then there was Cape Town itself. I'd never been anywhere like it. Standing on top of Table Mountain looking out over the city, or walking through Robben Island and realizing how recent all of it is, gave me a kind of context you can't get from a classroom. Working with people whose day-to-day is shaped by that history, on something meant to actually help their community, changed how I think about what this work is for. I left with more than a project — a better sense of what it means to build something for someone other than yourself.
