fosterlynn
commented
7 years ago User stories:
- As an OCP user, I can log in using my OCP credentials.
- As a project/group member, I can choose which of the projects/groups I am a member of to view. (Project/group member includes both participants and coordinators, any role with "member" behavior.)
- As a project/group member, I can view all the active plans for a project/group. (A plan contains a series or flow of processes that will create a deliverable or accomplish a goal.)
- As a project/group member, I can choose a plan to view the detail.
- As a project/group member, I can view the detail of one plan, including a "process flow" view and a "kanban" view, where each "card" is a process. (This view will depend on a recipe existing in OCP. Recipes will still be set up on the Admin App of OCP.)
- As a project/group member, I can create a new process.
- As a project/group member, I can update any process in that project/group.
- As a project/group member, I can create a new planned task, either assigned or unassigned.
- As a project/group member, I can update a planned task that I created.
- As a project/group member, I can log work I did for a planned task.
- As a project/group member, I can update work events that I have logged.
Some things to note that are missing from this proposed deliverable, that are included in OCP. They can and will be added in later Kamasi deliverables.
- Only work can be logged, no other inputs or outputs, so inventory will not be supported, and linking into bigger resource flows will not be supported.
- We are not providing the ability to assign work or to commit to planned work. (For discussion, is it Ok to leave this out for now?)
- There are not any notifications provided, any coordination features will be added later in conjunction with people using this initial deliverable.
This issue is to plan and design a minimal first prototype for use by one or a few FairCoop projects who want to start using OCP to coordinate their work, with the goal of distributing income from their budget, according to the new FC directions discussed at the recent summer camp.
We propose that it is two pages (see below), and covers the absolute minimum we can provide to support people planning and logging their work on a day-to-day basis. It will include adding and changing processes, commitments (planned tasks), and economic events (actual work done). We will target to complete this in one month, with interim deployment to the testocp server so we can get feedback earlier than that.
This is a much scaled down version of the original first planned epic. More would come after this first deliverable.
It is part of the discussion of if to charge ahead full speed with the Kamasi OCP interface or to use the OCP work app in the meantime.
User stories to follow.