Facilitator’s Notes - Firstname Bunchofnumbers

This Agile Decision Game, Firstname Bunchofnumbers, takes its name from the naming convention some sites will use when generating a random username. It will simply pull the first name field and then assign a random string of numbers attached on the end. Its a quick way to spot when a random person has created a quick throwaway account to anonymously stir the pot in the comments. It can also happen that its the username of a bot account, similarly created quickly but not really contributing very much.

Success in Agile isn’t just about completing the sprint—it’s about delivering value while aligning with the broader product vision and addressing user needs responsibly.

This scenario highlights the tension between creativity, engagement, and operational security/integrity. As the Developer in this situation advocates for the fun and unique aspects of the username feature, the challenge lies in balancing the product's cultural identity with legitimate concerns around privacy, moderation, and compliance. The perspective of participants should, hopefully, consider the various tradeoffs around preserving the platform’s value proposition and its appeal to both users and streamers. The tension is that they have competing priorities raised by fellow teammates, the QA and Product Owner.

This situation also puts the Developer at the heart of a values-based conflict: user engagement versus platform integrity. In an Agile environment, Developers frequently face such trade-offs, as they’re expected to balance technical feasibility, user value, and stakeholder input.

This scenario is a learning opportunity to demonstrate how Agile teams use collaboration and iteration to resolve competing priorities without undermining the product’s vision.

Customer Collaboration over Contract Negotiation Agile values continuous feedback from end-users and adapting to their needs. The developer's focus on user engagement reflects this principle, but it must be balanced with concerns about potential user harm.

Responding to Change over Following a Plan The emergence of issues like impersonation and offensive usernames represents an evolving reality. Agile teams must adapt quickly while staying true to the product vision.

Cross-Functional Teams Agile thrives on diverse inputs. The perspectives of the QA, product owner, and developer illustrate how cross-functional collaboration can surface tensions but also lead to better solutions.

This Agile Decision Game wasn’t based on an actual scenario, so there is no real world decision to describe.

This scenario can play out over 30 minutes with a group.?

Avoid calling on anyone in a more experienced Developer role for some of the initial responses. If similar solutions are being suggested, try to prompt further discussion using these questions:

• How might a team iterate on this feature to address concerns without overcommitting resources in the short term?
• What is the threshold for acceptable risk regarding issues like impersonation and offensive usernames?
• How can the team proactively address potential scandals?
• What would you say to streamers or users if this feature were changed? How might they react? Would you give anyone a heads up or just update it one day?
• What metrics or feedback would indicate whether the chosen approach is successful?
• Are there other approaches to addressing the risks without losing the feature’s playful charm?

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.