Binary Completion Criteria v3.1
Binary completion criteria replace the gameable "% complete" field with objective, evidence-based progress measurement.
The Problem
Traditional progress tracking asks "what percentage is this task complete?" The answer is subjective — a developer can say "80% done" when the task is barely started. This is the source of the "90% complete but nothing to show" problem.
The Solution: 0/100 Rule
In PM360, no task is "75% complete." Each task has 1-5 completion criteria, and each criterion is either met (with evidence) or not met. Progress = criteria met ÷ total criteria × 100%.
Evidence Types
Each criterion requires evidence of a specific type:
- test_run — automated test passes
- pr_merged — pull request merged to main branch
- uat_deployed — deployed to UAT environment
- demo_recorded — demo session recorded
- document_attached — supporting document uploaded
- review_approved — formal review completed
How It Works
- When creating a task, add 1-5 completion criteria (minimum 1 required)
- Each criterion has: description, evidence type, and mandatory/optional flag
- As work progresses, mark criteria as met and attach evidence
- Task cannot be marked "Done" until all mandatory criteria are met
- Skipping a criterion requires 20+ character justification (logged to audit trail)
AI Integration
The WBS Generator and AI Test Case Generator automatically suggest criteria for new tasks. The PM reviews and adjusts during task creation.