Key takeaway
The software development process — often called the software development lifecycle (SDLC) — typically moves through discovery, planning, UX/UI design, development, testing, deployment and maintenance. Most modern teams run design, development and testing in short iterative cycles (Agile) rather than one long sequence (Waterfall), so clients see working software every one to two weeks and can adjust priorities as they learn.
The seven phases of the software development lifecycle
- 01
Discovery1–4 weeks
Understand the business problem, users, current workflows, systems and constraints. Define what success means in measurable terms.
- 02
Planning1–2 weeks
Turn findings into a prioritized backlog, release plan, architecture outline, risk list and estimate.
- 03
UX/UI design2–6 weeks
Map user journeys, build wireframes and clickable prototypes, test them with real users and create the visual design system.
- 04
DevelopmentIterative sprints
Engineers build features in short cycles with code review, automated tests and a demo at the end of each sprint.
- 05
TestingContinuous
Automated unit, integration and end-to-end tests run on every change; QA engineers add exploratory, performance and acceptance testing.
- 06
Deployment1–3 weeks
Release to production through automated pipelines, with staged rollout, monitoring and a rollback plan.
- 07
MaintenanceOngoing
Monitor, fix, patch dependencies, improve performance and evolve features based on real usage.
What each phase should produce
If a vendor cannot show you these artifacts, ask why.
| Phase | Key artifacts | Your role |
|---|---|---|
| Discovery | Problem statement, user personas, process maps, requirements list | Provide access to stakeholders, users and systems |
| Planning | Product backlog, release roadmap, architecture diagram, estimate, risk register | Prioritize features and approve the plan |
| UX/UI design | Wireframes, clickable prototype, design system, usability findings | Review flows, involve real users, sign off designs |
| Development | Working increments, source code in your repository, sprint demos | Attend demos, answer questions, reprioritize |
| Testing | Test plans, automated test suites, defect reports, test results | Run user acceptance testing |
| Deployment | CI/CD pipeline, infrastructure-as-code, release notes, runbooks | Approve go-live and coordinate internal rollout |
| Maintenance | Monitoring dashboards, incident reports, update log, improvement roadmap | Report issues and steer the roadmap |
Agile vs. Waterfall: which fits your project?
| Aspect | Agile (e.g. Scrum) | Waterfall |
|---|---|---|
| Structure | Short iterations of design, build and test | Sequential phases, each completed before the next |
| Requirements | Evolve as the team and users learn | Fixed and documented up front |
| Client visibility | Working software every 1–2 weeks | Mostly at the end of major phases |
| Handling change | Expected; reprioritized each sprint | Formal change requests |
| Budget model | Often time and materials or fixed budget with flexible scope | Often fixed price for fixed scope |
| Best for | Products with uncertainty or user-facing complexity | Well-understood, stable, heavily specified work |
Many teams use a hybrid: a fixed discovery and design phase, followed by Agile development within an agreed budget.
How a two-week sprint actually works
Each sprint starts with planning: the team pulls the highest-priority items from the backlog and commits to what it can finish. Developers work through those items with daily check-ins to surface blockers early. Code is reviewed by another engineer and covered by automated tests before it is merged.
At the end of the sprint, the team demonstrates working features to you — not slides. A short retrospective follows, where the team agrees on one or two things to improve. Then the cycle repeats, informed by your feedback.
Who is on a typical delivery team
Product owner
Usually on your side. Owns priorities and makes the business decisions the team needs.
Project or delivery manager
Runs the process, tracks budget and timeline, removes blockers and reports progress.
Solution architect
Designs the system structure, integrations and technical standards.
UX/UI designer
Researches users, designs flows and interfaces, and validates them with testing.
Software engineers
Build frontend, backend and mobile features, write tests and review each other’s code.
QA and DevOps engineers
Own test strategy and automation, and the pipelines and infrastructure that ship the software.
What clients can do to keep a project on track
- Name one product owner with authority to make decisions
- Answer team questions within one business day
- Attend every sprint demo and give specific feedback
- Involve real end users early, not just managers
- Treat new ideas as backlog items, not mid-sprint changes
- Plan time for user acceptance testing before launch
Content last reviewed