← Back to team overview

gtg-contributors team mailing list archive

Re: Questions about User Stories


Hi Meg,

(1) I have to admit, that i can't say much about the backend-related user stroys, but i think most of them wouldn't pass acceptance tests. (2) + (3) Definitly! The current user storys are a bit insufficient. What do you think about a persona approach? We could create 2 or 3 different personas and split their needs and requirements down to simple tasks.

A simplified Example:

1. Greg (experienced user) is in a hurry and wants to add a task with 3 Tags, before he leaves the house. 2. Bob (inexperienced user) is in a hurry and wants to add a task with 3 Tags, before he leaves the house.

How would they solve this, and what would they do differently? While Greg (he probably knows the synthax) will use the Quick Entry Toolbar and type "Task @Tag1 @Tag2 @Tag3", Bob has to create an all new task, because the only way he knows to insert tags is by clicking the "add-tag" button in a open task. And so on...

While I'm at it: You may have noticed, that i also engage in the redesign of the GTG UI (currently mostly on the visal design). I have an idea how we could work on this together.

I will finish my design and try to fit the UI with the Gnome 3 HIG requirements. When I'm finished, we could evaluate the design based on the personas/user storys and eliminate possible usability flaws.

What do you think of that?


Am 18.03.2012 16:13, schrieb meg ford:

Bertrand has been answering questions for me related to gtg contribution and GSoC, but he suggested that it might be beneficial for me to ask on this list.

I am interested in refining the user stories and I want to ask:

(1) Do you feel that the stories that are currently documented on the wiki will pass acceptance tests that are written based on their requirements? (2) Do you feel that gtg could benefit from a more in-depth analysis of user stories, including step-by-step flowcharting that details which steps of a process pass/fail? (3) Do you think that the users stories would benefit from being more atomic? For example, do you think there would be benefit in analyzing "Dam wants to set a priority for his tasks" and "Dam wants to see his tasks sorted by priority" as two separate user stories?

Meg Ford

Mailing list: https://launchpad.net/~gtg-contributors
Post to     : gtg-contributors@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~gtg-contributors
More help   : https://help.launchpad.net/ListHelp

Follow ups