Mission Tests

Definition

Mission tests are predetermined indicators—both qualitative and quantitative—that specify progress toward successful mission achievement. They are executed on scheduled dates and help teams and stakeholders examine assumptions and hypotheses about the work. Unlike general metrics, mission tests are deliberately limited to the critical few indicators that matter most to the mission, not to everything measurable.

In the Book

Larsen and Nies distinguish mission tests from vague progress measures by anchoring them to specific outcomes the mission is meant to create. The team and product manager execute mission tests together on scheduled dates, using the results as checkpoints for learning rather than judgment.

Internal mission tests measure what the team gains or learns as a result of the work: defect rates released into production, team members' job satisfaction, or stakeholder satisfaction with product demos. External mission tests measure outcomes beyond team authority: instances of the product in use, customer satisfaction rates, market penetration, or cost reductions.

In the System Tracking Project case study, the concern raised by support representatives ("We're evaluated on how many calls we can complete") became the catalyst for a mission test: the new system should be easy for support representatives to learn and use without slowing them down. This mission test gave the team explicit permission to spend effort on usability (not typically valued in their organization) and gave stakeholders a concrete way to assess whether that effort mattered.

Mission tests can measure productivity improvement, strengthened capabilities, reduced costs, or other contributions to organizational outcomes. They are distinct from "definition of done" criteria (which are at the feature level) and from sprint goals—they operate at the mission level and drive learning cycles lasting weeks or months.

Why It Matters

Mission tests convert abstract mission statements into executable hypotheses. They give the team concrete targets to aim for and early warning if the approach isn't working. They also convert the charter from a static document created once into a learning instrument used throughout the project. By examining results on predetermined dates, teams catch drift from their intended mission while there's time to course-correct, instead of discovering at the end that they optimized for the wrong things.