Currently: Presentation – Final

Presentation:

Users:

Please Login

Login

Need an account? Click Here

Forgot your password? Click Here

Pueblo: A Group Project Management System

David Horm; Ryan Prins; Tho To; Anthony Trotter

Currently: Presentation – Final Logged in as Team Turtles (logout)

What’s the problem?

• We are all involved in group projects that involve multiple files of data

• One person or multiple people manage this data• Tracking versions and who has what version is

often difficult• Losing files by deletion, overwriting, or

misplacing can set the group’s progress way back

• Mainly, files float around between people with a group defined schema

• For example…

Currently: Presentation – Final Logged in as Team Turtles (logout)

How files are currently passed

Draft Passing via E-mail Send All Documents to WhiteySometimes Really Bad Things HappenManah manah!

Manah manah!

Manah manah?

Currently: Presentation – Final Logged in as Team Turtles (logout)

Problems with existing systems

• Sampling of Existing Systems– Jupiter

• Not available for download

– Basecamp• No file sharing in

free version

– dotProject• Cumbersome

• Goldilocks Syndrome– Other systems are too much or too little.

• So…

Currently: Presentation – Final Logged in as Team Turtles (logout)

Brainblast!!!

Just RightI’d like that not too big and not to small… to go.

Currently: Presentation – Final Logged in as Team Turtles (logout)

Process Overview

• Requirements– Method: Focus Group Analysis

• Design/Implementation– Method: Xtreme Programming

• Usability Testing– Method: Use Case Scenarios & Catalyst

Survey

Currently: Presentation – Final Logged in as Team Turtles (logout)

Our Solution

Currently: Presentation – Final Logged in as Team Turtles (logout)

Requirements Analysis

• Method: Focus Group Analysis– Why use the focus group technique?

• Not a large portion of our grade• Easy to complete in short amount of time• More robust replies from participants• You guys do most of the work… we just listen

– Who?• Informatics students

– How Many: 10– Why: They’re easily accessible

• CSE students– How Many: 5– Why: To get different group perspective

– How Long?• 45 minutes

Currently: Presentation – Final Logged in as Team Turtles (logout)

Requirements Analysis - Results

• Differences between the groups– Code vs. Papers/Artifacts– Group Size

• INFO: 4-6• CSE: 2 to 3 tops

– Project Duration• INFO: Half Quarter to Full Quarter• CSE: 2 to 3 Weeks

– Informatics students are pickier, and harder to please

• Overall, no big difference that stood out

Currently: Presentation – Final Logged in as Team Turtles (logout)

Requirements Analysis – Results [continued]

• Summary of Prioritized Results– Member/Project Management

• User accounts and authentication system• Project creation and management

– File Management• Cross between FTP, Windows Explorer, and CVS• Check-In/Check-Out system

– Deadline Management– Member Communication

• Some internal form of communication– E-Mail– Forum– Personal Message System

– Project History• Similar to MMC Event Viewer

– Professional/Visually Appealing– Privacy Issues

Currently: Presentation – Final Logged in as Team Turtles (logout)

Design/Implementation

• Method: Extreme Programming– Why extreme programming?

• Implementation goals• User input is readily available

– These guys are always in the group room…– But this guy leaves early…

Visit ileaveearly.com for more details!

Currently: Presentation – Final Logged in as Team Turtles (logout)

Design/Implementation – Process

• Create modular page design

• Brainstorm a database schema

• Watch these DVDs…

• Program our butts off

Currently: Presentation – Final Logged in as Team Turtles (logout)

Design/Implementation – Results [Modular Design]

• Module Interdependencies?• Sure, but check that module is active first.

• Default Modules?• Admin

• Why? You need a place to manage the site• Projects

• Why? What good is project management without projects?

Currently: Presentation – Final Logged in as Team Turtles (logout)

Design/Implementation – Results [Page Load Order]

Currently: Presentation – Final Logged in as Team Turtles (logout)

Design/Implementation – Results [Database Schema]

Currently: Presentation – Final Logged in as Team Turtles (logout)

Design/Implementation – Results [Prototype]

o We didn’t program anything, but we have pretty pictures…

Currently: Presentation – Final Logged in as Team Turtles (logout)

Usability Testing

• Method: Use Case Scenarios + Catalyst Survey– Why use-case scenarios?

• Easy to create scenarios• Everybody does it• Previous experience with the technique (INFO 440)

– How many scenarios?• 3 scenarios

– New User

– Project Manager

– Administrator

– How many tests• 4-5 tests per scenario

Currently: Presentation – Final Logged in as Team Turtles (logout)

Usability Testing – Results (so far…)

• 2 out of 7 had negative feedback– “I was logged in twice for some reason.”– “Anthony sucks.”

• How Intuitive are the Modules (1-5)– Projects = 5– Account = 4.67– File = 4.33– Admin = 4.14– Deadlines = 3.67

• How we can improve the system– Consistent Design– Educate users on metaphors– Minor GUI changes

Currently: Presentation – Final Logged in as Team Turtles (logout)

It’s peanut butter jelly demo time!!!

http://turtles.lazyi.net/dev/

Currently: Presentation – Final Logged in as Team Turtles (logout)

Questions/Comments/Insults?

o Goal: Make this guy angry…