project-goals

You can track binary business outcomes by defining high-level objectives that are either achieved or missed, preventing scope creep and vague success metrics. This distinction clarifies project progress by separating measurable milestones from ongoing development tasks.

Defining project milestones as binary goals is the best way to prevent scope creep. By forcing a distinction between business outcomes and feature delivery, you ensure success criteria are clearly achieved or missed, avoiding vague metrics and unmeasurable targets.

You can link high-level business goals to specific roadmap items through contextual linking. This ensures active development work is always tied to a measurable business outcome, maintaining alignment between your project strategy and feature execution.

Yes, you need integration with existing artifact storage to maintain persistent state and historical records of project outcomes. This integration is required to store the status updates and historical data of your binary business milestones.

Yes, binary goal tracking is designed for product strategy milestones like acquiring your first paying customer. You can define this milestone, set its success criteria, and track its status directly alongside your active development roadmap.

To create a new business milestone and set its success criteria, run the project-goals new command. This initiates the definition process for your binary business outcome, allowing you to track its status within the project lifecycle.