liveBook · Manning

Common ground

As explained in Bug Bash

Common ground is a shared basis of understanding, interests, or objectives that supports agreement and collaboration.

Common ground is the shared understanding of what people value, need, or want to achieve. It turns a request for support into a conversation about mutual benefit. For a bug bash, the aim is not merely to defend the event against objections, but to understand stakeholders’ priorities and show how the event can help them move toward their goals. section 2.4.2

Start by listening before making the case. Ask what quality means to the person, what their current goals are, and how you might support one another. Their answers provide a basis for connecting the bug bash to their interests. Before proposing the event, prepare a clear description, likely benefits for that person, and a draft timeline. section 2.4.2

Use common ground to build support in practical steps:

  • Map the people whose approval or help is needed, then learn their perspectives and priorities. section 2.4.2
  • Frame the initiative in terms of the other person’s goals rather than only your own need for agreement. section 2.4.2
  • Talk through details with organizing allies so they understand the success vision and can shape an approach that respects their priorities. section 4.1.1
  • Adjust involvement to each ally’s role, availability, and information needs; early practical details can enable timely preparation. section 4.1.1

An initially reluctant ally

An ally assigned to help organize a bug bash may not yet believe in it. Discuss what they value, emphasize the benefits that matter to them, and clarify how their contribution supports a success vision they can share. This can increase motivation and make participation a win-win rather than an obligation. section 4.1.1

Table 4.1 Bug bash organizer team
Bug bash ally
Their usual role
Activities they can help with
Benefits of being an ally
Delivery team contact(s)
Can be a product manager or a developer, anyone who knows their features well, and if needed, could offer tech support, too
·        Providing test scenarios (and requirements for environments) for their team
·        Acting as a contact person in case of questions: possible stand-by during the event
·        A chance to represent their team and increase awareness of the work that the team is doing
·        Clarified scenarios are a great way to contribute to the team’s current and future success
·        Extra efforts can be considered during an employee’s annual review cycle
Office support allies
Office manager/administrator, or anyone responsible for the event planning and space
·        Arranging the space for the event
·        Helping out with any on-the-spot errands like ordering snacks, preparing the space, and printing any materials if needed
·        Opportunity to increase awareness of available spaces to use in the office
·        Involvement may encourage future events to be hosted and supported
·        Increased visibility as a partner in the office may also be considered during annual reviews
Facilitator
Typically, one of the primary bug bash organizers. Someone familiar with testing processes, who is a clear communicator, a smooth presenter, and a capable guide for the participants.
·        Facilitating the event
·        Providing the main information and guidance for anyone participating
·        A very visible role that can showcase the person’s ability to coordinate the group and their ability to present
·        Great way to practice facilitating bigger events
·        Showcases proactivity as part of annual review
Tech support
DevOps, Operations, IT support, or equivalent
·        Providing the needed access
·        Setting up test environments
·        Supporting during the event in case of tech issues
·        Increases awareness of the work done in tech support
·        Could get testing for their system and possible new features. For example, testing multiple instances simultaneously is a built-in load test
·        Useful at the end-of-year performance reviews as an example of collaboration
Communication allies
Typically, stakeholders and team leads who are respected and listened to within the company
·        Promoting the event by sharing the message with others
·        Reaching out to the groups they are influencing and inviting them to participate
·        Allies who bridge groups, especially those in leadership roles, make a big impact on increased communication and cross-functional collaboration
·        Visibility as an example of how allies can help with such events

Compare organizer roles, contributions, and benefits to identify what may matter to each prospective ally. section 4.1.1

How Bug Bash covers it

How deep it goes
Provides listening questions, meeting preparation, benefit framing, and role-sensitive involvement guidance.
Examples
Uses stakeholder conversations, reluctant assigned allies, and office-support preparation for a face-to-face bug bash.
What it assumes
Assumes an identified bug-bash initiative and people whose approval or organizing help is needed.
What you can do after
Apply it by preparing conversations that link a bug bash to stakeholders’ and allies’ stated priorities.
How it connects
Connects stakeholder management, persuasion, quality, organizational readiness, and bug bash organization.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Bug Bash. The section links point to the parts of the book it draws on.