How We Work
The waterfall development method seems to be ideal for the software development, as it gives the development team comprehensive and complete requirements before designing and coding. However, based on our past experience, changing in requirements is mostly common during the software development. Therefore, we have been an advocate for the agile software development method. We believe the agile method can bring great value to projects because it enables quick responses to changing requirements.
Agile methodology uses the incremental approach to both planning and development.
The initial requirements will be analyzed
and broken into "user stories". The development process will be divided into multiple phases, which are called as sprints.
The user stories will then be added to each sprint based on its priority, and they are expected to be completed in the sprint.
Once a sprint is finished, the sprint summary will be conducted and its user story accomplishment will be assessed.
If there is a requirement change, we will adjust this change to the "user stories" backlog; which means we might need to add, remove or modify the user stories. In this case, the priority of the leftover user stories in the backlog will be re-assessed. In a new sprint, the adjusted user stories will be added and the iteration starts again.
Upon the delivery of the project, you will receive:
Please click on each development stage below for more information about how we work and the outputs of each stage.