Skip to content

Dev Item Lifecycle

Every dev item moves through a lifecycle of five statuses. Each status determines what actions are available.

graph LR
    A[Planning] --> B[Development]
    B --> C[Measuring]
    C --> D[Complete]
    A --> C
    D --> E[Archived]
    A --> E
    B --> E
    C --> E
StatusWhat it meansBaseline metricsPost-release metricsMark as released
PlanningDefining the feature and gathering requirementsAdd, edit, deleteNot availableAvailable
DevelopmentFeature is being builtAdd, edit, deleteNot availableAvailable
MeasuringFeature is live, collecting dataAdd, edit, delete (dates before release)Add, edit, deleteAlready released
CompleteMeasurement period is overNot availableAdd, edit, deleteAlready released
ArchivedNo longer actively trackedNot availableNot availableNot available

Planning/Development → Measuring (Mark as Released)

Section titled “Planning/Development → Measuring (Mark as Released)”

This is the most important transition. When you mark a dev item as released:

  • Status changes to Measuring
  • An actual release date is recorded
  • Post-release metrics become available
  • The release date becomes the dividing line between “before” and “after”

Requirements: You must provide a release date that isn’t in the future and isn’t before your earliest baseline data point.

Move to Complete when you’ve collected enough post-release data to draw conclusions. You can still add post-release metrics after completing — this just signals that the active measurement period is over.

Archiving freezes the dev item. No further changes are allowed. Use this when you’re done with a dev item and want to keep your active list clean.

ActionPlanningDevelopmentMeasuringCompleteArchived
Edit dev item fieldsYesYesYesYesNo
Add baseline metricsYesYesYes (pre-release dates)NoNo
Add post-release metricsNoNoYesYesNo
Mark as releasedYesYesNo
Change statusYesYesYesYesNo
View resultsYesYesYes