User story
As a farmer I want to be able to easily document all the sources of revenue* coming into the farm so that I have a complete picture of my financial situation
* Note that not all sources of revenue need come from the farm. It is very common for farmers to have income from jobs outside the farm.
Why?
We know that for many farmers, especially smaller scale and family run farms that there are typically many sources of revenue beyond just selling raw produce that keep the operation afloat. Without providing enough flexibility to document this, we fail to:
Give users the tools they need to accurately manage their operations and financial situation
Fail to capture the true picture with regards to small scale agriculture
Fail to provide implicit guidance on ways of generating revenues that farmers might be able to take advantage of to increase their financial success
Assumptions
Functional Requirements:
Must-have:
Maintain or expand the ability to document a crop sale
Several common categories of incomes / revenues
Crop sales
A standard flow for adding a new instance of revenue that covers at least the following attributes:
Description (optional)
Date of income (required)
Category (required)
Attributable to (optional)
User should be able to select any number of crop plans
Revenue location
“On farm”, “Off farm”, null
Customer(s) (optional)
Notes (optional)
Ability to easily add several revenues back to back (but not within the same flow)
Saved revenues must correctly attribute revenue categories and crop types
Nice-to-have:
Ability to add several revenues in the same flow
Ability to mark a revenue as repeating
Ability to attribute revenues to particular crop(s)
Non-functional Requirements:
Must-have:
Most basic revenue flow shouldn’t take more than 10 seconds to complete
Nice-to-have:
User interaction and design
Questions and answers
Question | Answer | Date Answered |
|---|---|---|
Should we call money coming into the farm “Revenues” or “Income”? | Revenues |
|