Engagement
What to prepare before kickoff
Assessments move quickly when archives, owners, and decision questions arrive together. This guide is the checklist we send after a brief is accepted.
-
Export three release cycles
Provide CSV, JUnit XML, or equivalent exports for the last three release candidates or nightly windows you care about. Include environment and owner fields when available.
-
Name suite owners
List who can speak for each major pack. Without owners, flake and skip recommendations stall in the findings pack.
-
Share board questions
Write the exact questions your release board asks today—even if the current slides fail to answer them. We design the readiness narrative around those questions.
-
Agree read-only boundaries
Confirm which systems we may inspect and which remain untouched. Result analytics work should not alter runners until you choose follow-on engineering.
Remote and on-site
Most sessions run remotely. When travel helps—especially for kickoff with a large chapter—we can meet from our Chungcheongnam-do base. Travel days are scoped separately in the estimate.
After the pack
You keep the written findings, sample report layouts, and prioritized change list. Optional follow-ons include a release readiness readout or a flake pattern clinic.