Business problem
Identify users, current bottlenecks, decision points, and expected artifacts. Turn abstract expectations such as good results into observable or measurable criteria.
Scope Clarification
Fix objectives, metrics, and boundaries before work begins
Replace vague calls to ‘start building and see’ with a one-page scope statement.
Answer
What we provide
The first step in New Horizon's Delivery Approach is requirements clarification: establish the business domain, acceptance metrics, input material, and classification and compliance boundaries. Produce a scope statement and risk list as the single agreed reference for subsequent reuse assessment and iteration.
Last updated: 2026-10-12 · New Horizon Digital Outsourcing Team
Key points
- 01Inspectable metrics
- 02Clear classification boundaries
- 03Verifiable input inventory
Outputs of this step
- 01Scope statement
- 02Metrics table
- 03Input checklist
- 04Risks and exclusions
Path
How it works
- 01 Interviews and written clarification
- 02 Draft the scope
- 03 Confirmation by both parties
- 04 Freeze the starting baseline
Frequently asked questions
Can work begin with incomplete material?
Yes. Start with a tailored baseline based on available inputs, explicitly documenting gaps and assumptions in the scope. Deepen the work after closing the gaps to avoid rework.
Other Delivery Approach topics
Engineering Notes
Requirements clarification establishes work boundaries that can be signed off
Material and assumptions
Classify material by geometry, parameters, data, interfaces, and standards, noting availability, owners, and expected provision dates. Explicitly record assumptions associated with missing material.
Confirm the baseline
Confirm inclusions, exclusions, milestones, the acceptance environment, and change procedures together. Begin implementation only after both parties have reviewed the same scope version.
Tie Acceptance Scope to Model Elements
During scope clarification, define model levels, element identifiers, interface boundaries, and verification methods. Walk through one requirement-to-model-to-evidence path, distinguishing conceptual representations from execution-verified behavior, and assign responsibility for outstanding inputs.
Include Data Exchange Boundaries in Scope
For requirements import or tool changes, agree on object identifiers, property types, relationship semantics, and attachment scope, listing content that cannot be preserved. Domain extensions also need concept and property definitions, checked with representative samples; matching field names do not establish matching meaning.
Further Reading and Technical References
Related standards and technical documentation for solution selection and implementation.
Align the collaboration through Requirements Clarification
Describe your phase objectives and constraints without classified details, and we will provide scope recommendations.