When designing and developing web applications and larger projects, we are using iterative and agile development methodology - SCRUM. We have modified the rules for this methodology to suit our needs. Since we started to use the methodology, we see results - streamlining the development process and in particular the satisfaction of our clients.
Great advantage of this method is that the client actively participates in development. He knows just about every relevant moment of the design and development of the product. Another advantage is that this methodology focuses on quality of released services and very importantly, the functionality of the resulting product, where client gradually accepts component parts during the development. In this way, it minimizes the risk that the client receives the final stage of a product with functionality not matching customer requirements.
More informations:
This section will help you explain the basic pillars of the development methodology we use. In the classical development methodology such as RUP or UP procedure is as follows. The project is divided into phases: analysis (examination of the needs and requirements), design, implementation, testing. While in the iterative development methodology, the analysis, design, implementation and testing are repeated in smaller intervals. This can be useful especially if the client (project sponsor) is unable to identify all the needs and requirements for information system in the project beginning. Subsequently development proceeds continues in small steps (iterations), where process of analysis, design, implementation and testing is constantly repeated. Another advantage is that the client is constantly in contact with the project and monitors its development, that helps avoiding the wrong direction. Iterative process minimizes the loss when changing requests during the information system development. Agile approach rose from the iterative methods. Some agile methodologies such as SCRUM, integrate the client into the team, working on the project. Customer (product owner) is participating in the development particularly by setting the priorities of the development, setting requirements of the information system and the acceptance of individual development phases. After this incorporation of product owner into the development, work on the project is much more effective. Iterative and agile development methodology SCRUM emphasizes the quality of the work, in other words the project testing. Different phase of the project is considered completed, only when it is tested and accepted by the product owner. To increase quality and reduce errors in the development, agile methodologies tend to combine with the methodology of TDD (Test Driven Development). Efficiency is a fundamental pillar of these agile methodologies. To increase efficiency and compact development team to agile methodologies combined with XP (eXtreme Programming). There is often a situation that the project timetable is endangered. The classic methodology is postponing the deadline of the project. In the iterative methodologies, individual sections of the project, which fail to implement and test, will not be put into the release. In this way, only the part of implemented system is endangered, and not the whole release.Iterative development
Agile approach
Emphasis on quality
Emphasis on efficiency
Emphasis on deadlines