simple user stories per component, data and 2 levels of acceptance criteria (ISRIC)

soilwise-he / Project-management

This is a repository to capture and organize the project amangement related tasks of the SoilWise partners

0 stars 0 forks source link

simple user stories per component, data and 2 levels of acceptance criteria (ISRIC) #26

Open twoude opened 6 months ago

twoude commented 6 months ago

@fennyvanegmond @pvgenuchten

twoude commented 5 months ago

Per component (https://github.com/soilwise-he/Soilwise-Project-Backlog/issues) extract simple user stories, and make acceptance criteria.

User stories: https://github.com/soilwise-he/Soilwise-userstories/issues

@pvgenuchten is this still open? What should the acceptance criteria look like?

twoude commented 5 months ago

@fennyvanegmond

Options Knowledge management: Per component: write down scope + style. What question is asked and how to answer it?

Perspective from data: which questions can you answer? What do you think would be useful for you? Which other datasets are available that can be combined?

focus on Land managers: which questions can we answer based on the data available? Which we can't?

From sprint meeting: for the Marvic case: what parameters do we need to filter? Who will be the problem owner?

This is for iteration 2. Bring user stories groups together with Tuna -

fennyvanegmond commented 5 months ago

data transformation: simpler cases than the S4A case are welcome, eg. case where national soil monitoring data and LUCAS data need to be combined (eg to make a map of the country). point to endpoints/supply data: flanders, netherlands, italy, france

other option for the same is the data side of Maria's GSP salinity user story epic: which datasets does she use and can they be data transformed by the repository

fennyvanegmond commented 5 months ago

for Marvic: Fenny to ask Greet/Hui/Joost as problem owner or be the problem owner herself

for knowledge man. Fenny/Maria to list the questions and answers plus styles (in Vilnius?)