Project management
Our software development methodology is tuned to deliver the highest possible quality, on time, and at the best possible price for our clients. We call our methodology of analysis, software creation, and project management the iQuest Way.
Agile development
Agile is a flexible software development methodology. The team does not have precisely defined stages, they are all interconnected and repeated. The project is divided into iterations - cycles. Each of them includes planning, analysis, design, development and testing.
Design and development method using the Agile method
- Before programming, a less detailed project is created. Individual system modules are tentatively priced and timed.
- Implementation begins very quickly and the first functionality of the system is seen and presented very quickly.
- The created functionality is presented at regular meetings and further steps are agreed upon. The time already spent is continuously compared with the originally estimated time so that the customer is best informed about the development of the ongoing and overall complexity.
- The first versions are simple, but cover the maximum of 'must have' functionality. In subsequent rounds, 'nice to have' features are implemented.
- Invoicing is based on the developers' detailed time reports.
When to use Agile development?
- When customer needs and requirements change frequently or when the complete required functionality is not fully known in advance.
- Unlike the 'Waterfall' model, a fully detailed project is not required to start a project in the agile model.
Advantages and disadvantages Agile development
Advantages
- Very fast start of the development itself.
- Detailed design of individual parts only during the development of the first version.
- The first version reaches the client as soon as possible.
- The client participates in the development during ongoing meetings and can continuously influence the assignment and development.
- The software can be tested with users during development and adapted to their needs.
- Billing is ongoing, so there is no one-time burden on the client's cash flow.
- The intensity of development can be adjusted to the client's current financial capabilities after agreement between both parties.
Disadvantages
- The final price for development is not known in advance. However, it is possible to set an estimate and continuously refine it.
- The final deployment date is not known in advance. The customer himself influences what is developed and when.
Method Waterfall
This is a traditional method. It involves the gradual development of complete stages, each of which must be fully completed before the next one can begin. The Waterfall model makes it easy to manage a project. Development is fast, costs and duration are predefined. However, there is a downside. The Waterfall model will only provide excellent results in projects with clear and predefined requirements and ways to implement them. There is no way to take a step back, testing only begins after development is complete or almost complete.
Waterfall design and development method
- Before the actual development, an extensive system project is created.
- The design usually proceeds up to the prototype level.
- We test the prototype on selected users (user testing) and incorporate any observations before the actual programming of the application logic.
- The system is created exactly according to the project, the customer does not have to participate directly during the development.
When to use the Waterfall model?
- Only when the requirements are known, clear and firmly established. There are no conflicting requirements.
- There are no problems with the availability of programmers with the necessary qualifications.
Advantages and disadvantages Waterfall methods
Advantages
- Full documentation of each phase.
- Clear planning of development deadlines and costs.
- Transparency of processes for the customer.
Disadvantages
- Need to approve the full scope of requirements in the first phase.
- Increased costs and time in case of requirements changes.
- The project phase is relatively long (weeks to months).
