Freigeben über

Schedules

  • Artikel

More tips on how to go from 1-11 on the Test Test.

Test #2 on the Test is "The test team owns their own schedule". I like this test for a lot of reasons. One of the most obvious reasons is that it ensures that test time isn't sacrificed at the end of the cycle to make up for poor planning elsewhere (a certain recipe for disaster).

The subtle thing that comes out of this test is that teams that pass this test trust the test team, and know that their schedules and estimates were created with the same (or more) care as any other part of the product.

Gaining trust requires equal growth in credibility. Don't fake estimates and don't add massive amounts of fluff to the test schedule. Know what needs to be done and how it will be done. Explain the risk involved if the schedule is reduced or work eliminated. Once the rest of the team gains confidence that the test team knows what they're doing, they will stop trying to use test time to make up for other problems. An alternate version of passing this test is where test defines what "done" looks like for a sprint, milestone, or iteration, and the whole team holds to reaching that criteria before moving on. Either way, test teams worth working on don't try to eliminate test work  (or quality work) in order to reach a deadline.

Comments