The Quality Engineering department helps facilitate the quad-planning process. This is the participation of Product Management, Development, UX, and the Quality team which aims to bring test planning as a topic before the development of any feature.
These 4 areas are the main pillars to ensure we can continue to ship features while ensuring optimal test coverage. Velocity is only productive when we don't incur test debt. We want to be nimble while shipping fewer bugs thus improving our own velocity. One can look at the metaphor of the 4 legs of the Tanuki, without either one of its legs the Tanuki isn't able to run as fast.
The quad planning has two aspects attached to it, which is as follows:
The DRIs collaboratively work on new features to ensure we ship quality software.
The SET owns the completion of the
Availability and Testing section in the Feature Proposal to complete the definition of done. As we grow to reach our desired ratio, we will only have the quad approach in groups where we have an assigned SET in place.
quad-planning::readylabel. If necessary, the SET will coordinate with the PM/EM to discuss specific issues as needed. Those issues satisfying the below conditions are considered for
quad-planning::readylabel is applied:
workflow:ready for development,
group::*(this corresponding to the product group to which the SET is aligned to.)
Next x releasesmilestones.
package and qaregression job
quad-planning::complete-actionlabel to the issue which marks the completion of quad-planning.
Availability and Testingsection, then the SET add the