See the work. Know the next decision.
A maintainable project needs more than a feature list. We divide the work into stages with visible deliverables, named decision makers, and acceptance criteria that business and engineering teams can review together.
Explore the five stagesCONTENTSOn this page
Work, inputs, and review gates.
The detail and sequence can vary by project. Scope and review checkpoints are agreed before work begins.
Define the work before the features.
Start with the problem, the people, and today’s workflow. Separate what the first release needs from what can wait.
The work
- Map user roles, working journeys, integrations, and constraints around data or devices.
- Record what is in scope, what is excluded, assumptions, and questions that need investigation.
- Order work by necessity and risk, with initial acceptance criteria described as observable behavior.
What you prepare
- Examples of current documents or screens, with unnecessary personal data removed.
- A project contact, an approver, and the intended launch date with its business reason.
- Known information about existing systems, approximate workload, and constraints.
- Output
- A shared brief, initial scope, assumptions, and preliminary acceptance criteria.
- Review gate
- The stakeholders agree on the problem being solved and understand what the work does not yet include.
Make decisions while change is cheaper.
Review the experience and system boundaries before committing to details such as data models and access rules.
The work
- Define key journeys and screens, including empty states, errors, and permission restrictions.
- Map the data model, API contracts, and responsibilities of connected systems.
- Compare technical options, operating costs, and tradeoffs that matter to the project.
What you prepare
- Representative content, business rules, and available brand requirements.
- API documentation and authorized test accounts for connected systems.
- Timely answers and decisions from the agreed approvers.
- Output
- Screen direction, system structure, data model, and a record of consequential decisions.
- Review gate
- Key journeys and business rules have been reviewed, with the impact of later changes made explicit.
Build in reviewable increments.
Deliver visible pieces of the system, test alongside implementation, and bring blocked decisions back to the right people.
The work
- Implement the agreed priorities and connect data or external systems through defined boundaries.
- Review code, check types, and test important business rules and higher-risk behavior.
- Provide an agreed review environment and a clear list of completed, incomplete, and blocked work.
What you prepare
- Reviewers who understand the real workflow and can participate at the agreed checkpoints.
- Authorized test data and representative scenarios.
- Consolidated feedback that identifies the screen, reproduction steps, and expected result.
- Output
- Reviewable software increments, source code, and progress or constraint records.
- Review gate
- The increment meets its agreed criteria; defects are distinguished from requests that expand scope.
Test the difficult paths too.
One successful click is not acceptance. Review access restrictions, invalid data, unavailable dependencies, and users retracing their steps.
The work
- Run acceptance scenarios and integration checks against the agreed data and device scope.
- Review accessibility, rendering, performance, and failure behavior against the project criteria.
- Record test results, classify issues, and identify fixes required before launch.
What you prepare
- User representatives for acceptance testing and a named acceptance authority.
- Authorized data and an environment representative of the agreed production scope.
- Feedback with reproduction steps, observed behavior, and expected behavior.
- Output
- Test evidence, resolved or acknowledged issues, and a release-readiness checklist.
- Review gate
- Launch criteria are met, and any remaining limitations have been explicitly accepted.
Give the next operator a clear starting point.
Handover covers how to run and deploy the system, who owns the accounts, and how to respond to problems within the agreed scope.
The work
- Review the release plan, backups, and an appropriate rollback procedure.
- Transfer agreed code, documentation, and access through approved channels without embedding secrets in source.
- Explain ongoing operating tasks, items to monitor, and the terms of post-delivery support.
What you prepare
- Hosting, domain, and service accounts under the agreed account ownership.
- Business and technical recipients, with an appropriate way to store credentials.
- An agreed launch window and a decision maker who can authorize rollback.
- Output
- The contracted handover package, operating documentation, and acceptance record.
- Review gate
- Recipients can access the agreed deliverables and understand how to proceed or seek help when issues arise.
Keep decisions and changes visible.
- Change scope with the impact visible.
- New requests are recorded with their purpose and assessed for effects on timing, cost, and existing work. We then agree whether to add, reprioritize, or defer them. Providing feedback does not automatically approve an additional charge.
- Name the decision makers.
- Agree the main contact, approvers, and place where decisions are recorded. Meeting frequency and reporting format depend on the project. Open questions need an owner and a follow-up date.
- Separate acceptance from ongoing support.
- Acceptance criteria, correction periods, maintenance scope, and response arrangements belong in the project agreement. Delivering a project does not automatically include every form of ongoing support.
Plan the handover from day one.
- Source code and installation instructions within the agreed ownership and license terms.
- Required environment variables and a list of service dependencies.
- Agreed build, deployment, backup, and rollback procedures.
- Account ownership, access responsibilities, and recurring operating costs.
- Accepted limitations, outstanding work, and post-delivery support terms.
Have a problem to work on?
Use the brief guide, or share what you already know so the scope can be discussed.