As part of the acquisition process a first understanding of the project is gained. An initial design study helps to understand the scope and make realsitic estimations.

Project boundaries are set and the contract is signed.

This phase aims to prepare for a successful project start. Key tasks include procurement, defining stakeholders, setting up collaboration tools, establishing communication, refining timelines, planning initial meetings, and onboarding the team.

This phase aims to create a comprehensive understanding among stakeholders of project goals, requirements, user needs, and application content. It builds on existing client documentation, validated through interviews, research, and analysis.

This phase aims to create a concrete concept for the product's strategy, scope, and structure, demonstrating how it addresses key user scenarios. The resulting definition serves three purposes: internal stakeholder review, providing a reliable model for the development team, and offering a scope definition for project planning and prioritization.

This phase validates the product vision against project goals and constraints. It assesses concept feasibility and adjusts scope, timeline, and budget as needed. Client approval precedes the iterative design and development phase.

This phase involves iterative sprints where our team builds and tests the product incrementally. The goal is to deliver functional software after each sprint, with priorities set by the product owner and development team.

This phase prepares and deploys the product for public release. We test and optimize based on our quality model, assessing key aspects like usability, functionality, performance, and security. This ensures the product is error-free and meets project requirements.

This phase concludes the project by conducting a retrospective, celebrating achievements, documenting lessons learned, and planning the product's future roadmap.

This phase ensures secure, reliable application access for end-users, maintaining agreed service levels and support for internal staff. It may also involve ongoing product development through adaptive and perfective maintenance, following a defined roadmap for new releases.