Software Project Readiness Checker

The problem, desired outcome, baseline, and measurable signals of success are defined.

Primary user groups, their highest-value tasks, and current workflow constraints are known.

The first-release scope, deferred capabilities, and explicit exclusions are written down.

Functional requirements, assumptions, open questions, and the people empowered to decide are identified.

Systems that exchange data, interface owners, API availability, and failure handling are documented.

Source data, quality issues, migration volume, retention, and system-of-record rules are understood.

Expected users, transaction volume, response targets, availability, and growth assumptions are quantified.

Hosting, cloud, browser, device, network, deployment, and technical ownership constraints are known.

Authentication, authorization, audit, threat, incident, and security-assurance needs are defined.

Personal or sensitive data, consent, residency, access, deletion, and privacy review needs are mapped.

The required accessibility standard, assistive-technology coverage, and validation method are stated.

Sector rules, records obligations, procurement constraints, and bilingual requirements are confirmed.

Acceptance criteria, test ownership, environments, evidence, and sign-off conditions are documented.

Release stages, approvals, rollback, training, communications, and operational transition are planned.

Service ownership, support hours, severity targets, maintenance, monitoring, and roadmap ownership are clear.

Available team, target dates, dependencies, procurement path, and working budget range are realistic.