performing-technical-discovery

Technical discovery is the process of investigating an existing codebase to map relevant models, services, and data flows. It generates structured documentation that provides comprehensive context before implementing new features or system changes.

To map system interdependencies, trace data flows and identify integration points across controllers and services. This investigation produces a discovery document outlining constraints and affected code, which helps scope the proposed change accurately.

You need a discovery document when a proposed change impacts multiple existing systems or integration points. It captures relevant data structures and constraints, ensuring engineers understand the technical landscape before implementation begins.

Technical investigation should include identifying relevant models, controllers, services, and data structures. It also requires tracing data flows, mapping integration points, noting constraints, and documenting open questions to inform scoping decisions.

Trace data flows by investigating how existing systems interact across controllers, services, and models. Documenting these integration points and data structures yields comprehensive context that defines system constraints for the proposed change.