chapter three

3 Preparing the groundwork

 

This chapter covers

  • Deciding on the logistics of your bug bash
  • Expanding your timeline with potential bug bash activities
  • Beginning preparation of your working artifacts
  • Finalizing your plan by discussing it with leads

Now that you have an informal yes from your leadership, it’s time to start preparing for your event. There are multiple details to consider, and in this chapter, you’ll learn how to do the groundwork so that your bug bash goes as smoothly as possible.

3.1 The foundation of a bug bash: considering logistics

As tedious as good preparation and logistics may sound, the risk of failure for an event (and, in fact, for many other things in life) often stems from a combination of minor logistical shortcomings. You have to know what you’ll need to do before the event, so that during it, participants can do what they joined to do—test, as smoothly as possible, and not waste time waiting for the organizers to juggle the basic logistics.

3.1.1 First, define bug bash activities

How do we know what we should do to prepare for a bug bash? What are some example activities that we could consider? At this stage of a bug bash, it’s crucial to gather activities you will want to do. Check out table 3.1 to see a list of possible activities for your bug bash.

3.1.2 Next, expand the timeline

3.1.3 Decision time: onsite or remote?

3.2 Prepare working artifacts

3.2.1 Bug tracking system

3.2.2 The main working document

3.2.3 Set communication channel

3.3 Finalize your plan

3.3.1 Present the plan to the management

3.3.2 Possible changes and challenges to your timeline

3.3.3 Crystallize your working timeline

3.4 Summary