#USER STORIES
-
USER: I want it to be Web-based Mobile friendly useable on various devices.
WHY: Accessibility -
USER: I want the ability to setup a user account.
WHY: to save and personalize my own data. -
USER: I want the ability to edit images in an artistic way.
WHY: To provide entertainment and share my images. -
USER: I want the ability to have a friendList and share images with them.
WHY: To connect with user with similar interests. -
USER: I want the ability to share my image to various networks.
WHY: For seamless sharing between networks or websites. -
USER: I want to rate and comment on pictures.
WHY: To let others know what you think of the images. -
USER: I want send and receive messages.
WHY: To privately connect with other users.
## Story map These user stories do not seem to be the epic of the project, rather they belong to the first sprint.
https://railsfails.storiesonboard.com/m/cis272-agile-class I just did this, let me know if you can see it
Post client review
-
- Display on Phone.
- Display on tablet.
- P.C and laptop
- no changes
-
- Story for each design tool
- Story for each design tool
- Story for each design tool
- Story for each design tool
- Story for each design tool
- Story for each design tool
-
- Friendslist
- image sharing
- image share other social networks
-
- image rating
- image comments
- message delivery
Post meeting I have moved all stories to back log. We have stated that our sprint 1 will be 8 hours each. We talked with dave, and as a team we have 25 hours per week. This means each has 5, so we need to discuss if that stories can be made into smaller pieces and/or we must play another round or 3 of planning poker. Also we learned: example. If we each had a project that was 5 hours. And it took me 2 hours to complete, I would select a story from the backlog that i could do in as close to 3 hours as possible. If it took 2, thats great, but if it took 4 that would be ok as well. This would be the flex that dave was talking about.