Difference between revisions of "IS480 Team wiki: 2011T1 Aperture - Project Summary - UET"
Jump to navigation
Jump to search
Chchai.2009 (talk | contribs) |
Chchai.2009 (talk | contribs) |
||
Line 293: | Line 293: | ||
# Labels (8) | # Labels (8) | ||
<br /> | <br /> | ||
− | <div style="padding-left: | + | <div style="padding-left: 24px"> |
Based on the results of UET 1, Aperture will tackle the most occurring issues based on category to minimize such issues in future UETs. | Based on the results of UET 1, Aperture will tackle the most occurring issues based on category to minimize such issues in future UETs. | ||
<br /> | <br /> |
Revision as of 20:39, 13 November 2011
Contents
User Experience Testing
Progress Description
- For detailed documentation, see below
S/N | Comment | Category | Action to be Taken | Status |
1. | Long usernames become hidden above the user image | Layout | Edit CSS to fix layout | Pending |
2. | Difficulty in finding "start new project" | Presentation | Include start project in dashboard dropdown | Pending |
3. | "Find a project" does not mean much to an owner | Presentation | Include subtext or tooltip upon mouseover | Pending |
4. | "Find a developer" does not mean much to developer | Presentation | Include subtext or tooltip upon mouseover | Pending |
5. | Notification bar is in an awkward position | Presentation | Display on top of window | Pending |
6. | Notification bar was unnoticed despite color contrast | Presentation | Add animation to appearance of bar | Pending |
7. | Icons under user image is not intuitive | Presentation | Change icons/into labels | Pending |
8. | Column headers in newsfeed is confusing | Labels | N/A | Dismissed |
9. | Notification bar is not consistent in design | Layout | Edit graphic design | Pending |
10. | Budget does not indicate how much a developer can earn intuitively | Doc & Help | Do a JS calculation with display | Pending |
11. | "iteration" is technical jargon | Labels | Change to "Phase" | Pending |
12. | The duration of the iteration is unclear | Doc & Help | Add subtext to guide user | Pending |
13. | No back button (breadcrumb) | Navigation | Add back button | Pending |
14. | Sample description in iteration plan was mistaken as instructions | Doc & Help | Detailed instructions instead of example in box | Pending |
15. | Notification after bidding should be "new bid" instead of "update" | Labels | Change notification message | Pending |
16. | User was intimidated rather than assisted by the validation | Presentation | Change validation displayed | Pending |
17. | Tags field (eg: Ruby) may not mean much to non-technical users | Doc & Help | Provide links for tags to wiki | Pending |
18. | Text in iteration plan field in workroom did not seem like a description | Doc & Help | Insert label: "Description" | Pending |
19. | Owner does not know that he should start the iteration after bid acceptance | Doc & Help | Create notification to start project | Pending |
20. | Concept of budget is unclear, for entire project or iteration | Doc & Help | Add subtext to guide user | Pending |
21. | Owner does not know how the product would be delivered | Doc & Help | Add field for delivery method in project create | Pending |
22. | Developer does not know what "Iteration(s)" meant while bidding | Labels | Remove field, add "add iteration button" | Pending |
23. | Page reloads at times, while portions of the page load at others | Speed | Standardize the Angular reloading | Pending |
24. | Owner did not realize he could accept more than one bid per project | Doc & Help | Create accepted bids section in project manage | Pending |
25. | Iteration plan status should have different colored statuses | Presentation | Change color for tabs | Pending |
26. | Needs a proper step by step welcome page to guide new users upon login | Doc & Help | Include new user help | Completed |
27. | Dashboard is not intuitively understood as a "homepage" | Labels | Change label to "Home" | Pending |
28. | Budget does not indicate ceiling or floor price | Labels | N/A | Dismissed |
29. | Project create bid is not the same as "bid for this project" | Labels | N/A | Dismissed |
30 | Developer feels that bid price should be on top of bid page | Layout | Change order of fields | Pending |
31 | User tried clicking on newsfeed to go to relevant page | Navigation | Include link in newsfeed entry | Pending |
32 | Owner did not know that he will only be accepting the first iteration | Doc & Help | Tooltip | Pending |
33 | User thought headers in the Dashboard dropdown list were clickable | Presentation | Include downdown symbol | Pending |
34 | User prefers login screen to be in the centre | Layout | N/A | Dismissed |
35 | User does not know how detailed should description be | Doc & Help | Include help and instructions | Pending |
36 | Terms and conditions not displayed | Content | N/A | Dismissed |
37 | Iterations management require more guidance | Doc & Help | N/A | Dismissed |
38 | Delivery of work is not clear to both parties | Doc & Help | Include delivery method field | Pending |
39 | Give the owner a choice of delivery channel | Doc & Help | Include delivery method field | Pending |
40 | "Create a project" should be easily assessible | Navigation | Include start project in dashboard dropdown | Pending |
41 | Instead of "deliver", use "I've delivered" | Labels | N/A | Dismissed |
42 | Shortcut menu should go somewhere else | Layout | N/A | Dismissed |
43 | User profile viewing should be made readily available | Navigation | Include icons to view user profile | Pending |
Top 3 Areas for improvement
- Documentation & Help (15)
- Presentation (9)
- Labels (8)
Based on the results of UET 1, Aperture will tackle the most occurring issues based on category to minimize such issues in future UETs.
UET Deployment Screenshots
- // To be filled with deployed application screenshots
Categorical Classification
- Functionality refers to whether the functions are working purposefully, without errors and quintessential in the activities carried out by the user.
- Content focuses on providing the right information to the right user in the appropriate activity context.
- Labels should be appropriately named such that the user knows what each label is for to navigate the site.
- Presentation deals with the colors and shapes displayed on the website.
- Layout deals with where and how each detail on the page is displayed.
- Navigation ensures that the user needs as little clicks as possible to get where he or she wants to.
- Speed of response is the concern that the application processes pages and requests quickly.
- Documentation & Help ensures that the user intuitively understands the process flow, and functions of the website, with or without built in assistance.