Dear Business Analysts.

I am required to create a benefits tracking for my project. I am just feeling that I have done this through requirements gathering and the justification of each requirement that links to a tangible expected benefit. I have also done the acceptance criteria and how the achievement of that requirement will be assessed. From that basis I feel that I have done a bit of benefits tracking.

An example of what I am talking about:

Requirement: The system must be able to transfer 100k files per day

Justification: To increase the daily capacity in processing applications automatically, and to reduce the waiting time for 40 applications by 24 hours each.

Acceptance Criteria:  Assurance that the received volumes of applications are up to the new maximum capacity of 140 applications.

Acceptance Method: Daily reviews of the number of applications received/ of total available applications. To be assured by a system generated report that include each application with its reference number.

MOSCOW: Must

Requirement Maturity Time: Instantly post system roll-out

My question was this an example of a benefit tracking too as much as it is a requirement documentation?

Many thanks

Hi Kimbo,

Thank you for the reply, I understand your point, which is useful. I just wonder when it comes to benefit tracking is the tracking tools I added here for the requirement can be used for the benefit as the same? 

Thanks,

Madi