Back to the Playbook
DefineDefinitionDE-03

Estimate feature

Estimate effort, complexity, dependencies and delivery risk from the actual code, early enough to influence scope and priority.

Product statusAvailable now

Context in4 required inputsFeature brief or story · Relevant requirements · Codebase
TransformationArchitect + Architecture AgentEstimate Feature · Code Analysis · Atlassian
OutcomeEffort, complexity and risk estimate with the reason behind every number.Artifact: Estimate

Owner

Architect

Human + Agent

Participants · Agents

Product ManagerEngineerArchitecture Agent

Trigger

ManualAn opportunity is being prioritised, scoped or prepared for commitment.

Required context

JiraFeature brief or storyConfluenceRelevant requirementsCodeCodebaseArchitectureArchitecture context

Optional context

JiraHistorical estimatesJiraSimilar completed workFilesTeam constraints

Skills

Estimate FeatureCode AnalysisAtlassian

Methods used inside this Activity: Code-grounded complexity and coupling analysis · Uncertainty ranges instead of point estimates

Activity steps

  1. 1Inspect the affected areas of the code.
  2. 2Identify dependencies and risk drivers: API or schema changes, missing tests, coupling.
  3. 3Estimate complexity with uncertainty ranges.
  4. 4Propose scope cuts or spikes.

Output

Effort, complexity and risk estimate with the reason behind every number.

Artifacts

Creates: Estimate

Updates: Jira story

What good looks like

  • Uncertainty is explicit.
  • Dependencies and risk drivers are named.
  • Based on the code, not false precision.
  • Scope alternatives are offered.

Quality gate

Engineering reviews estimates for large commitments.

Destination

JiraConfluence

Usually next

People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.

Deep dives from the AI PM Lab

Articles that explain the thinking behind this Activity.

Show us exactly how product work happens today.

Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.