From the client’s perspective, the phases of a software project are most critical during transitions: with each transition, the scope, budget, and risk are reassessed, often based on incomplete information. Those who are familiar with these transitions negotiate from a stronger position than someone who only realizes at go-live that the scope of functionality has expanded.
This article describes the seven phases from the perspective of senior management, IT leadership, and procurement, not from the perspective of the development team. It outlines which decisions must be made in each phase and the risks that arise if those decisions are not made.
From the client’s perspective, a software project goes through seven phases: requirements analysis, requirements specification, vendor selection, design, development with interim acceptance tests, testing phase, and go-live with handover to operations. In each phase, the decision rests with the client, not the development team. Those who understand these points can identify budget and schedule risks weeks earlier than someone who simply waits for the next status report.
Preparation: Needs Analysis and Requirements Specification
The first phase begins before a single vendor is contacted. The needs analysis clarifies which business problem the software is intended to solve and whether the expected benefits justify the costs. If this step is skipped, the resulting requirements specification will address technical details but leave unanswered the fundamental question of why the project exists in the first place.
The requirements specification translates the needs analysis into a list of mandatory, recommended, and optional requirements. The decision made here determines the scope of the core features: What belongs in the first version, and what should be included in a later one? The article provides detailed instructions along with a template. Write a Statement of Requirements. If you don't set this limit, you'll end up negotiating it later through change requests, usually at a higher cost.
Provider Selection and Contract Model
Once a robust requirements specification is in place, the vendor selection process begins. In practice, reference projects, team composition, and whether a vendor has already built comparable systems carry more weight than the lowest hourly rate. At the same time, a decision must be made regarding the contract model, which is usually a choice between a fixed price and a time-and-materials model.
Fixed-price contracts may seem safer to clients, but they merely shift the risk to the provider, who recoups it through buffer periods and expensive change request fees. For most individual software projects, a time-and-materials contract with clearly defined milestones is the more transparent model, even if it requires more ongoing oversight on the client’s part. Not all procurement departments share this view; they prefer a fixed cost cap for good reasons.
Concept and Development: When the Scope Starts to Move
During the design phase, the team defines the architecture, data model, and interfaces. The client decides on fundamental technical issues at this stage, such as whether to integrate an existing ERP system or create new master data. Once made, this decision can hardly be reversed during the development phase without incurring additional costs.
The development phase itself is the longest and, at the same time, the most prone to scope creep. After the 2026 "Pulse of the Profession" Survey According to the Project Management Institute, nearly one-third of complex projects completely fail to meet their originally agreed-upon goals, nearly twice the 13 percent failure rate seen across all projects. A regular, honest status report with clear approval for every change request is the most effective way to counter this trend.
A broad-based transformation study by NTT DATA Business Solutions and Natuvion confirms this pattern across industries: 82 percent of the companies surveyed exceeded their originally planned budget for IT projects in 2026, and 79.5 percent were also behind schedule.
According to an international transformation study, that many companies exceeded their originally planned budgets for IT projects in 2026, and 79.5 percent were also behind schedule.
NTT DATA Business Solutions and Natuvion, as cited by etailment, 08/2026
| Phase | A typical decision made by the client |
|---|---|
| Needs Assessment | Whether the business case justifies the budget |
| requirements specification | Which features are included in the core package |
| Selection of Providers | Fixed Price or Time and Materials, which partner? |
| Concept | Approval of Architecture and Interfaces |
| Development | Handling Change Requests and Additional Work |
| Trial Period | What Issues Are Preventing the Go-Live? |
| Go-live | Rollback Limit and Handover to Operations |
Testing and Acceptance Before Go-Live
The testing phase is the last opportunity to fix defects at a low cost. During this phase, clients decide which identified defects will prevent the go-live and which will be carried over into production as known limitations. Without pre-agreed acceptance criteria, this decision becomes a point of contention, often under time pressure shortly before the planned launch date. The article “Defining Acceptance Criteria” describes how this dispute can be avoided.
The go-live itself is not the finish line. It marks the beginning of the seventh phase: the operational transition. Determining under what conditions a rollback will take place and who is responsible for disruptions during the first few weeks significantly reduces the risk of a chaotic launch.
Why the Phases of a Software Project Rarely Proceed Linearly
The seven-phase model describes an ideal sequence. In practice, the design, development, and testing phases overlap, especially in agile and hybrid projects, where each sprint goes through its own condensed version of these phases. A requirements specification from Phase Two may already be outdated by Phase Five because the business unit’s requirements have changed.
The seven-phase model is a guide, not a schedule. None of the cited studies specifically tracks how many projects in practice actually proceed linearly through all seven phases; most measure success and failure regardless of the chosen process model. Clients should therefore view the model as a checklist for decision points and not as a guarantee that a project will follow this sequence exactly.
Clearly identify decision points before the project begins
Those who are familiar with the seven phases and the decisions involved in advance are in a better position to negotiate the requirements specification and contract. torck provides support with needs analysis and the technical evaluation of proposals.
Frequently asked questions
How long does a software project take, from requirements analysis to go-live?
The duration depends on the scope. A well-defined specialized module with a team of three to five developers often takes four to seven months from requirements analysis to go-live. Larger projects involving integration with ERP systems or multiple departments frequently take twelve to eighteen months. In practice, the vendor selection process alone takes four to eight weeks if multiple proposals are solicited and compared.
Who decides on change requests during development?
Formally, the client side makes the decision, usually through a steering committee or a designated individual with budget responsibility. Without a clear escalation process, this decision effectively shifts to the project team. A good requirements specification therefore defines in advance the threshold at which a change must be approved and who grants that approval. Without this rule, the scope of functionality gradually expands without anyone having consciously decided to do so. It is common to set a threshold of one to two person-days of additional effort, beyond which formal approval is mandatory.
What happens if a vendor changes in the middle of a project?
A change is possible at any stage, but becomes more expensive as the project progresses because knowledge about the architecture and previous decisions is lost. It is important to have a complete statement of requirements, documented source code, and a contract that governs access rights and handover. Without this foundation, the new provider’s onboarding period is often extended by several weeks before any new features can even be developed. Clients should include such handover provisions in the original contract, rather than negotiating them only in the event of a dispute.
torck guides clients through every phase of a software project, from requirements analysis to go-live, with a team that develops custom software for industry and commerce and openly identifies decision points rather than hiding them in the project plan. The development teams are based in Maxhütte-Haidhof, Vienna, and Rabat; the sole contractual partner is the German company torck GmbH, ensuring that clients have a single point of contact and a single contract, even when multiple locations are working on the project. Learn more about custom software development: Custom Software Development.