Sprint Bazaar — Behind the scenes

From theory to reality — tips for a smoother adoption

Expect Resistance, lots of it

  • You mean I have to present 2 or 3 times now??? I only have to do it once last time!
  • If I have to mend a station, does that mean I don’t get to visit other stations!
  • Why can I only choose 2 stations to visit? What about the other 3 stations? Won’t I be missing out?
  • Can we go back to the old cadence (of silos sprint reviews in monologue), I don’t understand why we have to do something so complex

Expect to facilitate more

  • Get PO to recap sprint goal + welcome stakeholders
  • Get presenters (devs) to give a 1-liner of their station. A useful format to sell their stations is asking them “What you can learn from my station”. Also nudge presenter to share where is their station located.
  • Timeboxing is required and a bell will be useful to signal the need to rotate
  • Prepare sticky notes and sharpies for the stakeholders to solicit feedback
  • Gather all the disparate feedback and support the Product Owner in his debrief
  • Look out for important stakeholders to ask for their closing feedback!

Always Go back to Why

  1. To serve the Development Team by:
  • creating an environment for learning and mastery
  • embedding cross-squad learning
  • providing opportunities to facilitate and market their feature
  • Building flexible teams which can adapt to changing priorities — Flexible teams don’t happen overnight. They need to continuously learn from each other for both domain and technical knowledge.
  • Increasing rate and quality of feedback through smaller groups engagement — to build better products
  • a Sprint event that can scale with more teams
  • Our previous sprint reviews used to be Developers going through each and every acceptance criteria to prove that work is done and you can expect the reactions: Product Owners just “orh” and “okay”, no feedback!
  • POs now accept stories throughout the sprint and focus on making the bazaar an engaging one to solicit feedback for adapting the product

11 Sprints and 5.5 months of experiment

  • Teams are getting comfy in smaller groups discussions
  • Developers and business inspect and adapt increment closely together
  • We are excited to see how this can accommodate more squads as we ramp up
  • No more showing stories or acceptance criteria but instead…
Mamta showing her feature to other developers for feedback
Our intern Christopher showcasing his automation work to fellow BGPers, agile coaches and business.
David sharing with stakeholders and team members how he drastically reduced loading time

Was it worth it?



Be Happy, Be Awesome! We deliver high-quality digital services to citizens and businesses in Singapore 😊

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Nicholas Li

I enjoy agile ways of working, especially the more humanistic side of it.