Skip to content
Software DevelopmentCompany USA

Process Guide

The Software Development Process, Phase by Phase

Knowing how professional teams build software makes you a better buyer. This guide explains each phase of the software development lifecycle, what you should receive at each step, and where your input matters most.
  • Seven SDLC phases with deliverables
  • Agile vs. Waterfall in plain terms
  • Who does what on a delivery team
  • Where clients make or break a project

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

  1. 01

    Discovery1–4 weeks

    Understand the business problem, users, current workflows, systems and constraints. Define what success means in measurable terms.

  2. 02

    Planning1–2 weeks

    Turn findings into a prioritized backlog, release plan, architecture outline, risk list and estimate.

  3. 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.

  4. 04

    DevelopmentIterative sprints

    Engineers build features in short cycles with code review, automated tests and a demo at the end of each sprint.

  5. 05

    TestingContinuous

    Automated unit, integration and end-to-end tests run on every change; QA engineers add exploratory, performance and acceptance testing.

  6. 06

    Deployment1–3 weeks

    Release to production through automated pipelines, with staged rollout, monitoring and a rollback plan.

  7. 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.

PhaseKey artifactsYour role
DiscoveryProblem statement, user personas, process maps, requirements listProvide access to stakeholders, users and systems
PlanningProduct backlog, release roadmap, architecture diagram, estimate, risk registerPrioritize features and approve the plan
UX/UI designWireframes, clickable prototype, design system, usability findingsReview flows, involve real users, sign off designs
DevelopmentWorking increments, source code in your repository, sprint demosAttend demos, answer questions, reprioritize
TestingTest plans, automated test suites, defect reports, test resultsRun user acceptance testing
DeploymentCI/CD pipeline, infrastructure-as-code, release notes, runbooksApprove go-live and coordinate internal rollout
MaintenanceMonitoring dashboards, incident reports, update log, improvement roadmapReport issues and steer the roadmap

Agile vs. Waterfall: which fits your project?

AspectAgile (e.g. Scrum)Waterfall
StructureShort iterations of design, build and testSequential phases, each completed before the next
RequirementsEvolve as the team and users learnFixed and documented up front
Client visibilityWorking software every 1–2 weeksMostly at the end of major phases
Handling changeExpected; reprioritized each sprintFormal change requests
Budget modelOften time and materials or fixed budget with flexible scopeOften fixed price for fixed scope
Best forProducts with uncertainty or user-facing complexityWell-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

FAQ

Software Development Process: common questions

What are the stages of the software development process?

Most teams follow discovery, planning, UX/UI design, development, testing, deployment and maintenance. In Agile projects, design, development and testing repeat in short sprints rather than happening once.

Is Agile better than Waterfall?

Agile suits projects with uncertainty or evolving requirements because it delivers working software early and adapts to feedback. Waterfall can work for stable, heavily specified projects. Many teams use a hybrid with a fixed discovery phase followed by Agile development.

How involved does the client need to be?

Expect a few hours each week from a product owner for demos, questions and prioritization, plus time from end users for design reviews and acceptance testing. Fast decisions from the client side shorten timelines more than almost anything else.

How long is a sprint?

Usually two weeks. One-week sprints suit very early prototypes; three- or four-week sprints are less common because feedback slows down.

When does testing happen?

Continuously. Automated tests run on every code change, QA engineers test features within the sprint they are built, and broader regression, performance and acceptance testing happens before each release.

See how this process would apply to your project

Tell us what you want to build. We will outline the phases, team and timeline we would propose.