Agile Requirements Management allows you to add new features to the project at any stage adjusting the project planning on the way.

Agile Approach


In most of the projects of our customers the requirements can change at any stage, be that planning or development. Without proper handling of such situations the planning may disrupt, affecting all project teams, including the customer themselves. If this happens regularly, it will affect planning, quality, delivery, expectations, motivation and budget resulting in delays and dissatisfaction on all sides. Agile Requirements Management is what you need.


What You Get


You get your dedicated Product Owner if you are not able to take the following responsibilities:

  1. Defining the product
  2. Envisioning the product
  3. Identifying the target audience and the overall market
  4. Identifying the business needs: collecting, creating the User Stories and defining the Product Backlog
  5. Prioritizing the items in the product backlog
  6. Adequate planning
  7. Communicating to the project stakeholders, development team and the target audience
  8. Acceptance testing
  9. Customer satisfaction

You also get access to the Agile project management system, such as Redmine or JIRA.



Ideal For


  1. Customers unable to take the responsibilities of a Product Owner
  2. Projects with the Time & Material (pay-per-hour) business model
  3. Projects with unstable or frequently changing requirements (early stages, startups, etc.)


How It Works


Agile Approach


icon_mp icon_customer

Product Owner communicates to the project stakeholders and the target audience to get answers to the general business questions as well as to the more in-deep and technical ones.


Product Owner collects, creates and prioritizing the User Stories, forms and continuously maintains the Product Backlog. Product Backlog is a set of all features the end product would consist of. The User Story is a short and clear definition in the end user or business language of what user does or needs.


Product Owner plans a set of features to be implemented in the Release (shippable product) and communicates that to the stakeholders, the development team and possibly the target audience (end users).


Development Team plans the Sprint (the set of features to be implemented over a period of 2-4 weeks) and Daily Scrum (a set of features to be implemented during a day).


Product Owner tests, accepts or rejects the results of each sprint and each release. Product Owner also does overall product acceptance testing.

icon_mp icon_customer

Product Owner communicates to the project stakeholders and the target audience the results of acceptance testing and the next plans.





Part-time or full-time. It depends on a project, the goals, the needs of the customer, the stakeholders, the development team, etc. Availability is negotiable.


Working Conditions



We sign with you the Service-Level Agreement (SLA) for consulting services covering the expected results, types of works, deadlines, payment conditions, etc.


We sign with you the Non-Disclosure Agreement (NDA). This is optionally.


Payment Conditions


S Projects: 100% Pre-payment S Projects: 100% Pre-payment
M, L Projects: 50% Pre-payment, 50% After M, L Projects: 50% Pre-payment, 50% After