Product Development

Experiment comparing two versions to measure impact.

Conditions that define when a feature is done.

Iterative product development approach emphasizing flexibility and feedback.

Application Programming Interface enabling systems to communicate.

High-level structure of software components and their interactions.

Prioritized list of product work items.

Continuous Integration/Continuous Deployment for automated testing and releases.

Shared checklist for when work is complete.

Reusable UI components, rules, and patterns.

Toggle to enable/disable features safely.

API query language allowing clients to request specific data.

Small independent services that communicate over APIs.

High-fidelity visual design of screens.

A single deployable application containing most features.

Ability to understand system health via logs, metrics, traces.

Product Requirements Document describing problem, solution, and requirements.

Improving code structure without changing external behavior.

Common API style using HTTP methods and resources.

A plan showing what product work is coming and when.

Ability to handle growth in users, data, or load efficiently.

Agile framework using sprints, roles, and ceremonies.

Time-boxed development cycle, often 1–2 weeks.

Future cost caused by quick fixes or suboptimal design choices.

A short requirement from the user’s perspective.

Low-fidelity layout showing structure and flow.