Enter your email address to follow our blog with all the latest software engineering tricks, tips, and updates from the R&D team at KnowBe4!
By: Steve Abelow
Published: 2 Jun 2023
Last Updated: 2 Jun 2023
After reading part 1 of this series on War Room, you might be asking yourself some very important questions:
All of your questions will be answered in the next few parts of this series. This post is about the Bug Bar and how it’s used in the War Room process.
As you now know the purpose of War Room is to minimize code churn the closer we get to releasing a new product or feature. The Bug Bar will specify the criteria that must be met for a bug to be considered severe enough during War Room for the Release Manager to approve a check-in that will churn the code. That code churn is what we are trying to avoid, so the closer we get to release the more restrictive we want to be on approving bugs.
At the beginning of War Room the bug bar is set in the first war room meeting, it usually starts at a 3 based on the schedule and stability of the product. The closer we get to release the lower the bug bar gets. The bug bar should be at 1 when the code is released, this will ensure the code is only changed for the most critical bugs.
Bug Bar 1 (High or Highest)
Bug Bar 2 (Medium)
Bug Bar 3 (Low)
Bug Bar 4 (Product Enhancement)
Now that the Bug Bar has been defined for the War Room team the bugs can be set appropriately and if they meet the Bug Bar they will be reviewed by the Release Manager. The Release Manager will approve or reject the bugs during the daily meeting, if rejected the PM will prioritize the bug to be fixed after the release.
In the final part of this series, you will learn about the Rules of War Room, what is in the meeting minutes and how you will know when the product is ready to ship. At that point you should be able to run your own War Room and ship amazing products and features like we do here at Knowbe4.
KnowBe4 Engineering heavily uses On-Demand environments for quick iterations on native cloud-based…
How KnowBe4 solved the "It Works on My Machine" problem with a new approach to provisioning test…