Two weeks ago, we entered a phase of the Beta 2 product cycle we call “Tell Mode”. This is the point which marks the transition to the end game for Beta 2. Here’s what has happened so far, and an idea of what’s to come for Beta 2.
Tell Mode is when the Division begins to meet daily. Every team reports on the number of bugs fixed the previous day, with those fixes to be available in the current day’s build. The idea behind Tell Mode is to start the shut down process. Teams move into a centralized triage process, where every bug that comes into the product team is scrutinized as to whether or not is should be fixed for Beta, moved to the next milestone, or punted from the project completely. Over time, we start to look at samplings of bug fixes and begin to set the bar, ensuring that teams are fixing the right set of bugs and that we're positively affecting the quality of Beta 2. This additional process slows the churn on the product because the more fixes we take, the more chances of regressions or build breaks. Our goal is to slow the number of check-ins, stabilize, take the necessary fixes to meet our release quality criteria, give the product a little time to “bake”, and then ship it.
Tell Mode is scheduled to last three weeks, through 02/04. We expect to then move into Ask Mode, where every bug that we want to be fixed has to be approved by our centralized ship room. The first question we ask on every one of these bugs is “what is the customer scenario?” Every fix needs to have a positive, tangible, and critical customer impact or else we don’t take it in Beta 2 at that point. Once we are in Ask Mode, we’ll do another test pass and we’ll finish driving up our quality criteria such as our Stress pass rates.
So far, we’re doing pretty well. We’re running a little hotter than I would like, but all the right things are happening. The next week will really give us a good indication on how well we’re tracking towards our goals.