Running a Scrum-lite process for a team that had never shipped software before — what worked and what I'd do differently.
Leading a student engineering team meant guiding people who had never shipped software before. The hardest part wasn't the code — it was building a process light enough to not scare anyone, but real enough to make progress visible.
We ran a stripped-down Scrum: short weekly goals, a simple board, and a quick standup. No ceremony for its own sake. The board did the heavy lifting by turning vague ambitions into small, claimable tasks.
If I did it again, I'd invest earlier in code review as a teaching tool rather than a gate. The reviews where we talked through 'why' were worth more than any lecture.
