1 / 20

Streamlining Group Project Management: A Comprehensive Data Oversight System

This project presents an innovative group management system designed by David Horm, Ryan Prins, Tho To, and Anthony Trotter. It addresses common challenges in group projects, such as file version tracking and data management. Many existing systems fail due to cumbersome interfaces or lack of essential features, leading to disorganization and project delays. Our approach utilizes focus group analysis and extreme programming to develop a user-friendly solution that includes project creation, member communication, and deadline management. Join us as we redefine project management for better collaboration!

haracha
Télécharger la présentation

Streamlining Group Project Management: A Comprehensive Data Oversight System

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. Pueblo: A Group Project Management System David Horm; Ryan Prins; Tho To; Anthony Trotter

  2. 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…

  3. Manah manah! Manah manah! Manah manah? How files are currently passed Draft Passing via E-mail Send All Documents to Whitey Sometimes Really Bad Things Happen

  4. 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…

  5. Brainblast!!! Just Right I’d like that not too big and not to small… to go.

  6. Process Overview • Requirements • Method: Focus Group Analysis • Design/Implementation • Method: Xtreme Programming • Usability Testing • Method: Use Case Scenarios & Catalyst Survey

  7. Our Solution

  8. 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

  9. 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

  10. 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

  11. 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!

  12. Design/Implementation – Process • Create modular page design • Brainstorm a database schema • Watch these DVDs… • Program our butts off

  13. 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?

  14. Design/Implementation – Results [Page Load Order]

  15. Design/Implementation – Results [Database Schema]

  16. Design/Implementation – Results [Prototype] • We didn’t program anything, but we have pretty pictures…

  17. 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

  18. 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

  19. It’s peanut butter jelly demo time!!! http://turtles.lazyi.net/dev/

  20. Questions/Comments/Insults? • Goal: Make this guy angry…

More Related