Scope
Number of flows, screens, roles and states.
Before estimation we define the nearest output, integrations, constraints and acceptance criteria. If inputs are insufficient, discovery is estimated as a separate stage.
Share the inputsCost and timing change with scope, unknowns and handover requirements.
Number of flows, screens, roles and states.
External services, APIs, data and access.
How clearly requirements and architecture are defined.
Environments, documentation, acceptance and support.
These are not fixed packages. A format defines the boundary and basis of the nearest stage.
When the problem is clear but requirements and boundaries are not.
Possible scope
Estimation basis
Research scope and availability of source material.Output
Agreed diagram, requirements or prototype.
When a concrete output and acceptance criteria can be defined.
Possible scope
Estimation basis
Work composition, integrations and acceptance criteria.Output
Verifiable artifact or working version.
When a product develops through several agreed stages.
Possible scope
Estimation basis
The nearest stage; later stages are estimated separately.Output
A sequence of accepted outputs.
A fixed number without scope creates false certainty.
Without defined scope one price combines tasks of very different complexity and becomes misleading.
Yes, when the main flows, integrations and constraints are known. The range includes its assumptions.
A new flow, role, integration, state or requirement outside the agreed work.
Yes. Every stage can have a separate output, estimate and acceptance criteria.
We will confirm whether the inputs are sufficient or discovery should come first.