A project needs a technical scope before development begins.
How the work progresses
Translate the proposed application into operating scenarios, constraints and unresolved decisions.
Map subsystem responsibilities and interfaces, then identify the smallest useful prototype.
Review the architecture and define the evidence needed at each development gate.
What to send first
Share the application, current platform or files, operating conditions, target date and intended acceptance criteria. Tell us which decisions are fixed and which need evaluation. Do not send confidential designs through the initial form.
An example of a project scope, based on supplied member experience. It is not a claim that this team has completed this project. Price, schedule, deliverables and responsibility require a project-specific agreement.
