1 / 1

Design: Make the right thing easy to do, make the wrong thing hard to do.

s ucks .Berkeley. Group 24. A conduit between Uservoice and Pivotal Tracker. Motivation:

orsen
Download Presentation

Design: Make the right thing easy to do, make the wrong thing hard to do.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. sucks.Berkeley Group 24 A conduit between Uservoice and Pivotal Tracker Motivation: To take IT error reports and turn them into an actionable user story so a programmer (Campus IT employee, hackathon group, CS169 student...) can begin to resolve the problem.Sucks.berkeley.edu structures the process of reporting an issue to begin gathering the pertinent information needed for a programmer to resolve the problem, and gives a platform for programmers to continue to communicate with problem reporters to resolve the issue. • Design: • Make the right thing easy to do, make the wrong thing hard to do. • Make the app as simple and quick to use as possible • Two main user groups: Frustrated Users, who report problems, and Developers, who work to solve problems • Frustrated Users are guided through a process of giving the information to create a User Story from their issue • Frustrated Users are encouraged to view and select existing issues rather than enter new issues • Developers can view the list of projects and issues and request to be added to the Pivotal Tracker Project • Developers can ask questions of users on Sucks.Berkeley to collect further information • Pivot: • Original design would collect error report info as well • Uservoice software, which fills the same role, is being adopted by campus organizations • We updated our design to integrate with Uservoice so as not to duplicate functionality • Challenges and Lessons: • Integrating with external APIs Lesson: APIs can be problematic, read and test the API, and design with that in mind. • Scoping and defining an open-ended projectLesson: It is important to have concrete goals and a detailed design from the beginning of a project. • Project PivotLesson: It is important to deal with a pivot swiftly and decisively so the project continues to have a concrete goal. Database Structure Poll data from Uservoice, push projects to Pivotal Tracker as well as accessing project progress

More Related