You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a data manager I need information about the required storage class and backup requirements so that I can make sure that the data is safe and can be accessed as required
#33
Open
jludwig1 opened this issue
Nov 12, 2017
· 4 comments
Similiar to my comment in #60. There are more than enough user stories about volume but I think additional information about how the storage is managed might be necessary in a DMP. Do you think a rephrased user story about documenting storage procedures would be out of scope too?
We actually noticed the problem that currently the user stories with #volume and #storage overlap. In my opinion we would need to provide some more information on storage type: cloud, backup-policy, geographical location, jurisdiction, etc. However, none of the user stories specifies this. I cannot rewrite any of them to make it fit my understanding - this wouldn't be a sound methodological approach. But please feel free to modify your's so that we could include it.
jludwig1
changed the title
As a data manager I want to plan storage and backup procedures so that backups will be made and no data gets lost
As a data manager I need information about the required storage class and backup requirements so that the data is safe and can be accessed as required
Feb 9, 2018
jludwig1
changed the title
As a data manager I need information about the required storage class and backup requirements so that the data is safe and can be accessed as required
As a data manager I need information about the required storage class and backup requirements so that I can make sure that the data is safe and can be accessed as required
Feb 9, 2018
How granular do you want the user stories? This user stories could be split in two separate stories, one about storage class (e.g. fast/hot vs. slow/cold) and one about reliability.
No description provided.
The text was updated successfully, but these errors were encountered: