User Stories

We created five user stories on a thoroughly odd website called PlanITpoker. We didn't quite understand how we could create user stories for this project, since almost all the improvements were to the backend--something the user never interacted with. It seems like any user stories we would have created would have been for Phase I or II.

In any case, since we did happen to make some improvements to our front-end in Phase III, we created the following user stories:

• Add features, such as sorting and searching, to the model tables. Estimated time: 10 hrs, allowing for research of JQuery. Actual time: 10 hrs.
• Allow the user to view live streams for a specific game. The user should have access to sort live streams by number of viewers, number of followers, language of stream, and streamer name. Estimated time: 1 hr after research into JQuery. Actual time: 5 hrs.
• Every user’s knowledge of video game genres will vary. It's essential that we provide information that is understood by expert and novice users. Estimated time: 2 hrs of planning the Genre instance pages' layout. Actual time: 10 hrs, accounting for moments of inspiration in the first two weeks that prompted us to change the displayed info.
• If a user wants to know information about a specific video game and view streams associated with that game, then he/she should be able to access that information. Estimated time: 2 hrs of planning the Game instance pages' layout. Actual time: 10 hrs, ditto.
• A user will likely be interested in a variety of streamers. Incorporate ~30 games and ~30 streamers. Estimated time: 10 hrs of data collection total. Actual time: Closer to 20, man.

PlanITpoker was hard to figure out in the amount of time we spent on it. It seems like a website in search of a problem; using index cards a la XP is pretty straightforward.