Open kaichih opened 7 years ago
Copied from Greg:
For this particular user story, what we can complete without problem are:
While the following features need experts:
From the information we collected, give suggestions to a group or individual users. Since we don't know how to determine what kind of indicates should trigger alarm, especially for individuals with special condition. Although for some basic indicates like air pollution we can survey public resources that should be available for everyone
For personal medical condition monitoring, and to remind taking pills or other necessary therapy, we can make it usable, technically. However, this heavily relies on whether user is willing and if user is able to keep the record accurate. For example, if user have a prescription for taking pills 3 times per day, our app only works if user keep tracking or input the correct data for tracking. I think this is kinda UX issue, but I have no idea about how to improve feature like this, to make it useful than a regular alarm app.
Rest parts are just solid enough to implement. Basically, just hard work for API, website, app, database, and other standard tech requirements. So we should have issues to raise our non-tech requirement and to see who can take some of them, as well as having some tech issues to solve for the same user story. Since we are using GitHub, that means we may use milestone for the whole single user story, and have tech and non-tech issues for requirements to complete the story.
No matter what features we would like to include, we need to have a place to reside and represent them to users. What's in our mind? Would it be an app? Thanks.
Define the user story for this milestone. To define a smaller scope based on a given user story helps us to focus on something concrete. Then, derive it to detailed items that we should work on as first few milestones. The benefits of smaller user stories include but not limited to,
We used to conduct a systematic way to summarize a very useful user story. That was done for 2016 London Work Week, and we put our proposal here, https://github.com/OpenIoMeT/Iomet-wiki/wiki/Meetup-and-Demo
Let me copy & paste here,
In order to identify most valuable user stories and include them into our first demo in the future, we collect most significant pain points, prioritize them, and then pick 4 of them based on technical evaluation and also the major concept of this project. We put all our meeting notes regarding to the demo online. 4 chosen user scenarios are:
Then, we proposed to have the following demo scripts to represent the main idea of the first 3 user scenarios:
I would suggest to review this user story, and maybe we need to break this big user story into smaller user stories, and start from here. How about this?