Agile Approach works well for the projects with the incomplete requirements and requires evolutionary development and deployment.

Whether you build an aircraft or a new model of a spoon, you have to prepare the requirements to the end product. However, specifically in the software world you may not know exactly what your final product will look like and what it needs to be built. The requirements may change at any stage. If you do not have both a rigid plan and a detailed documentation, the Agile Approach or the Agile Requirements Management is what you need.


Ideal For


  1. Having simple rules and transparent process for all stakeholders
  2. Starting with incomplete requirements
  3. Unstable requirements that may change at any time during the project
  4. Delivering high-priority business features first
  5. High-level of continuous adaptation and innovation


How We Work


We work with the iterative and incremental development that focuses on the client collaboration, interaction, working software, and responding to change versus processes, tools, rigid plan and detailed documentation. For Agile approach we use Scrum.

We document all requirements, issues and defects in a system like Redmine or JIRA.

Agile Approach



  1. The development is split into the iterations (Sprints).
  2. Each iteration is 1-3 weeks long.
  3. The Client (Product Owner) prepares and maintains a list of features (Product Backlog) prioritized according to their business values.
  4. The Team uses the Product Backlog to plan Sprints. Sprint contains a subset of Product Backlog items.
  5. By the end of each iteration the project team rolls out a product build for testing and Product Owner’s review. It is based on the functionality defined in the Sprint Backlog.

Quality Assurance

The development team reserves some time during each Sprint for debugging and bug fixing activities. Such continuous testing and bug fixing process ensures the high quality of the released product.

Feedback, defects, and small enhancements found by the Product Owner will be added to the Product Backlog and implemented during the next iteration.

The project team provides the Product Owner with the latest build of the product after all the functionality of the project is implemented. The Product Owner conducts so called Acceptance testing. All the defects found at this stage are fixed on demand. The Product Owner accepts the project as completed.

Check out our Agile Requirements Management service.