PlanKit
Book a strategy call

The phases of a software project from idea to launch

Web DevelopmentPlanKit team8 min read

The phases of a software project from idea to launch

From the client's side, a software project has seven phases: discovery, requirements, UX design, building in iterations, testing and user acceptance, launch with data migration, and support. Each phase ends with something you can read or try with your own hands, and you sign it off before the next one starts.

Most writing on the software development life cycle is aimed at developers and explains what the team does. This article is for the owner who pays and decides. For each phase you get what you should receive, what you review, and the sign that the phase was skipped. There is no single mandatory split. The international standard ISO/IEC/IEEE 12207 sets a framework for software life cycle processes from conception through retirement and leaves each project to build its own model from them. The split here is a practitioner's one.

The software development phases on one page

Keep this table in front of you in every meeting with the development team. The last column matters more than the first.

PhaseWhat you receiveWhat you sign offSign it was skipped
1. DiscoveryA two or three page scope documentThe problem, the success measure and what is out of scopeA fixed price after one meeting
2. RequirementsA requirements list with acceptance criteria per itemThe list, after the people who do the work have read itCoding starts with the requirements in the developer's head
3. DesignA clickable prototype of the screensEach user's path from start to finishYou first see the screens after they are built
4. BuildA working version at the end of each iterationWhat was finished, and any change requestProgress percentages with nothing to try
5. TestingA bug log and a test environment with realistic dataThe user acceptance recordYou are asked to test after launch
6. LaunchA launch plan, a trial migration and a rollback planOld and new data reconciledData is migrated for the first time on launch night
7. SupportA written support agreement, with every account in your nameThe handover listNobody is named as responsible for outages

Phase 1: discovery defines the problem before the solution

Discovery gives you a short scope document that describes the problem in the language of your business. It should name who will use the system, which process it will change, and the measure you will judge it by, such as the time it takes to issue a quote. The most useful section is "out of scope", because it settles later arguments about what was agreed.

Review it with one question: could a new employee understand the problem from it without asking you? Expect the estimate at this stage to be a range, since the details are not settled yet.

The warning sign is a fixed price after one meeting. It means nobody studied your problem, and the gap will come back as change requests. If you have not yet decided that your problem needs software at all, start with the tests in when your company needs custom software. If discovery shows that a ready product covers most of what you need, compare the two routes in off-the-shelf or custom software.

Phase 2: the written requirements are what you hold the team to

Here you receive the requirements list, the reference you will compare the delivered system against. A common format is the user story: "As a sales rep, I want to create a quote from the customer's saved details." Each story carries acceptance criteria that say when the item counts as done.

Check that the list covers what usually gets forgotten:

  • Roles and permissions: who sees what, and who approves what.
  • The reports management needs, with their columns and filters.
  • Connections to other systems, such as your accounting software or payment gateway.
  • The data that will move over from spreadsheets or the old system.
  • Exceptions: cancellations, returns, special discounts, partial orders.

Do not sign the list alone. Give it to the employee who runs the process every day, because they know the cases that never come up in meetings. The warning sign is coding that starts while the requirements live in scattered messages or in the developer's memory.

Phase 3: you see and try the design before it is coded

UX design gives you a clickable prototype: you press buttons and move between screens with no code behind them. Changing a screen at this point costs far less than changing it after it is built.

Review the prototype with real tasks. Ask two employees to create an order or issue an invoice on it, and watch where they hesitate. Ask for one page of technical design alongside it, saying where the system will be hosted, which programming language it uses, and who owns the hosting accounts. The warning sign is seeing the screens for the first time after they are coded.

Phase 4: building in short iterations

During the build you receive a working version at the end of each iteration, and you try it yourself on a staging environment kept apart from the live system. Scrum calls this iteration a sprint, and the Scrum Guide sets it at one month or less, ending with a review where the team shows what was finished.

With every iteration, ask for three things: a list of what was finished against the requirements, a link to the staging version, and the code pushed to a repository your company owns. Any new change request is written down, with its effect on time and cost stated before work starts. That protects you and the team.

The warning sign is weeks of "70% complete" reports with no version you can open. A percentage is the team's estimate. A version that runs is the only evidence.

Phase 5: testing and user acceptance before go-live

Testing is two separate jobs with different owners. The development team tests that each item works as written. User acceptance testing (UAT) is run by your own staff, to confirm the system fits the way they actually work.

What you should receive:

  1. Written test scenarios built from the acceptance criteria in the requirements.
  2. A test environment holding realistic data, rather than three made-up customers.
  3. A bug log that ranks each bug by severity and shows what was fixed and what was deferred.
  4. A clear answer on how security and permissions were tested.

Sign the acceptance record when the important scenarios pass, even if small bugs remain logged with a fix date. The warning sign is "try it after launch and we will fix what comes up". It means your customers and staff become the test team.

Phase 6: launch and data migration follow a written plan

Before launch you receive a plan that sets the go-live day, who does what on that day, and how you return to the old way if a serious problem appears. That last part is the rollback plan, and having it in writing shows someone thought about the bad case.

Data migration needs a rehearsal before launch day, because old data usually holds duplicates and gaps that only show up when you move it. Ask for a trial migration well before the date, then reconcile the figures yourself: customer count, open account balances and stock quantities, old system against new. Ask for user training and a short guide for each role.

If the data includes personal data about customers or staff, find out where it will be stored and who can reach it. Egypt has Personal Data Protection Law No. 151 of 2020, and Saudi Arabia has its Personal Data Protection Law, and their rules differ. Check what applies to you with your legal adviser; this is not legal advice. The warning sign here is data migrated for the first time on launch night.

What must be in your company's name at handover

At handover your company should hold everything needed to run and change the system without going back to the team that built it. Code ownership terms in the contract are covered in the custom software article. This is the list to check on handover day:

  • The code repository with its full history. Transferring a repository on a platform such as GitHub keeps the commit history and the logged issues, which is far better than a zip file of the last version.
  • Hosting and cloud accounts in your company's name, paid with your company's card.
  • The domain and its DNS settings, the settings that point your address to the server.
  • Connected service accounts, such as the payment gateway, the SMS and email services, and the app store if there is a mobile app.
  • Passwords and API keys in a password manager you own, changed after handover.
  • A backup you have actually restored, since a backup never restored is a guess.
  • Documentation: how to run and deploy the system, the libraries it uses, and what another team needs to carry on.

If a single item on this list sits in the developer's name, you stay tied to them after the contract ends.

Phase 7: support starts on launch day

This phase gives you a written support agreement: the warranty period for fixing bugs at no extra charge, response times by severity, and the line between fixing a bug and building a new feature. It should also say who updates the libraries and the server, and who checks the backups.

The warning sign is no named person to call when the system stops. The first weeks after go-live expose cases testing missed, so book the team's time for them from the start.

Your next step

If you have a quote for a software project now, put it next to the first table and write, against each phase, the document or version you will receive. Wherever a phase has nothing to receive, ask the team for it in writing before you sign. If you are starting from an idea, commission discovery on its own first and decide after it. You can also hold PlanKit's custom software development service to this list before you choose.

Custom SoftwareProject Management