Difference between revisions of "Talk:HowTo Request User Experience Assistance"
From Apache OpenOffice Wiki
Lutz Hoeger (Talk | contribs) m |
Lutz Hoeger (Talk | contribs) m |
||
Line 3: | Line 3: | ||
: done, at least for a first start; Whoever has a better idea for a short intro is welcome to change it. | : done, at least for a first start; Whoever has a better idea for a short intro is welcome to change it. | ||
* see spec project for feature classification - maybe re-use? | * see spec project for feature classification - maybe re-use? | ||
− | : done | + | : done, answer is no. Involving UX (as in user experience engineering) and writing a spec are two completely different actions within the feature development cycle. "Spec required" does not necessarily mean "UX required". However, "UX required" makes it very likely that a spec is required, too. For this reason, "UX required" needs it's own criteria, and cannot copy the "spec required" criteria. |
* replace "tools in place" by Issue Tracker and mailing-lists (is this all?) | * replace "tools in place" by Issue Tracker and mailing-lists (is this all?) | ||
− | : done | + | : done, see section "How to contact..." |
* change the name of the mailing-list for requesting assistance | * change the name of the mailing-list for requesting assistance | ||
− | : done | + | : done, it is request@ux |
* when in the development process should UX be included? | * when in the development process should UX be included? | ||
− | : done | + | : done, see last line of the intro |
Revision as of 15:48, 22 June 2007
ToDo:
- re-write or drop the intro ("Why..."), or at least introduce "HCI"
- done, at least for a first start; Whoever has a better idea for a short intro is welcome to change it.
- see spec project for feature classification - maybe re-use?
- done, answer is no. Involving UX (as in user experience engineering) and writing a spec are two completely different actions within the feature development cycle. "Spec required" does not necessarily mean "UX required". However, "UX required" makes it very likely that a spec is required, too. For this reason, "UX required" needs it's own criteria, and cannot copy the "spec required" criteria.
- replace "tools in place" by Issue Tracker and mailing-lists (is this all?)
- done, see section "How to contact..."
- change the name of the mailing-list for requesting assistance
- done, it is request@ux
- when in the development process should UX be included?
- done, see last line of the intro