commit d393007393e2d5a1abbf797596df4e7c4109ffc9
parent ea5f3e82379291ea22dd1b511e59d34aa11e7ae6
Author: Lynn Foster <foster.j.lynn@gmail.com>
Date: Mon, 11 Feb 2019 06:38:32 -0600
use case: buying club
Diffstat:
1 file changed, 13 insertions(+), 0 deletions(-)
diff --git a/use-cases/buying-club.md b/use-cases/buying-club.md
@@ -0,0 +1,13 @@
+# Buying Club (Driftless Co-Option)
+
+This use case is specifically to look at how this buying club thinks about flow times, but may have other uses too.
+
+The buying club runs on cycles of (usually) 4 weeks. Each cycle has a sequential number identifying it. Accounting takes place by cycle. Accounting is basically that every member needs to work 3 hours/cycle to order in a cycle. It doesn't need to be during the same month, and people can go negative, but people try to stay reasonably up to date.
+
+There are different ways of working.
+* Regularly scheduled work at specific times in the cycle: like splitting food, gathering orders, cashiering, cleaning up. People sign up every cycle on pre-planned jobs/shifts.
+* Work at home that has due dates, but otherwise doesn't matter when it is done, where the time is managed by the person doing the work: like updating catalogs, printing invoices and labels, ordering from suppliers, paying suppliers.
+
+People who signed up for specific shift work record the specific times worked.
+
+People who work at home record their time as hours per cycle on a spreadsheet.
