Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
OneWeek|OneTool
An Experiment in Interdisciplinary, Rapid,
Open Source Software Development
Sponsor/Organizer
Center for H...
What it is
• “Digital Humanities Barn-Raising”
• 12 “digital humanists”
• 6 days in “isolation”
How it worked: Learning & planning
• Sunday night
Overview + Get-to-Know-You
• Monday morning
Brief seminars(Outreach/Open...
How it worked:
Doing/Testing/Refining/Launching
Tuesday afternoon - Saturday afternoon
= 4 days
Work in teams with BRIEF m...
Guiding Principles: Center for History
& New Media
• Build something that will be used
• Keep tool simple & focused
• Outr...
Team Outreach Approach/Reflections
• Illustrate a compelling story for potential
users/developers-why should they care?
• ...
Team UX Approach/Reflections
•ID’d real-world use case scenarios and built use cases
•Evaluated similar projects.
•The div...
Team Dev. Approach
• Forced parallel development
• Constant communication and trust
• Good-enough prototyping
• Decide and...
PLAY VIDEO
Results
• 6,000 downloads
since Aug. 3, 2010
• Active user & dev.
forums
• Press
• We learned a ton.
What worked
• Bringing together a group of do-ers
• Ratio of doing vs. planning
• Quick timeframe kept egos out
• Diversit...
What didn’t work
• More doing!
• More cross-learning
• Post-release, we have our
day-jobs
• Not enough time for UX
Future
• Continue to develop tool – Recent 0.5
alpha release (10/2010)
• Continue dissemination of software
with online ou...
How is it different than our environment?
• Ratio of Planning vs. Doing is flipped
• Minimal risk-taking
• We stay in our ...
One Week | One Tool http://oneweekonetool.org/
Anthologize http://anthologize.org
Center for History & New Media http://ch...
Upcoming SlideShare
Loading in …5
×

OneWeek|OneTool: An Experiment in Interdisciplinary, Rapid, Open Source Software Development

1,395 views

Published on

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

OneWeek|OneTool: An Experiment in Interdisciplinary, Rapid, Open Source Software Development

  1. 1. OneWeek|OneTool An Experiment in Interdisciplinary, Rapid, Open Source Software Development Sponsor/Organizer Center for History and New Media, George Mason University Funder The National Endowment for the Humanities, Office of Digital Humanities Effie Kapsalis digitaleffie@gmail.com Twitter: @digitaleffie
  2. 2. What it is • “Digital Humanities Barn-Raising” • 12 “digital humanists” • 6 days in “isolation”
  3. 3. How it worked: Learning & planning • Sunday night Overview + Get-to-Know-You • Monday morning Brief seminars(Outreach/Open Source Software Development, Digital Humanities) • Monday afternoon Brainstorming • Tuesday morning Team + Twitter voting, teams formed (Development, Outreach, UX) = 2 days
  4. 4. How it worked: Doing/Testing/Refining/Launching Tuesday afternoon - Saturday afternoon = 4 days Work in teams with BRIEF morning/ evening check-ins
  5. 5. Guiding Principles: Center for History & New Media • Build something that will be used • Keep tool simple & focused • Outreach and marketing are important for building user & developer community • Make decisions and move on (“Leadership is momentum- making,” Tom Scheinfeldt.) Jeremy Dan Sheila Tom Sharon Trevor Creative Lead Director Director of Public Projects Community Lead Assoc. Dir. of Public Projects Managing Director
  6. 6. Team Outreach Approach/Reflections • Illustrate a compelling story for potential users/developers-why should they care? • Create buzz where users are • Divide & conquer/Trust • Outreach doesn’t stop at release Project Mgt/ Copywriter/ Outreach/ Designer Copywriter/ Editor/ Grant Writer Design/Multi media Prod./ WP Site Builder Social Media Guru/ WP Site Builder/Writer Effie Doug Zach Jana
  7. 7. Team UX Approach/Reflections •ID’d real-world use case scenarios and built use cases •Evaluated similar projects. •The diversity of backgrounds in the OWOT crew was a benefit •2 days in, Jason & Scott moved to the dev team to pitch in on some UI/AJAX development. Kathie worked iteratively with the dev team to build wireframes and UI documentation. Kathie Jason Scott Project Mgt/ I.A I.A/ Java- Ajax Hijinx I.A/ Java- Ajax Hijinx
  8. 8. Team Dev. Approach • Forced parallel development • Constant communication and trust • Good-enough prototyping • Decide and go • Design software around technical strengths as well as our hypothetical users’ needs Metadata Badass Wordpress Guru XSLT Transfixor“Glue” Julie Steve Boone Patrick MJ Patrick R. pdf -Tamer
  9. 9. PLAY VIDEO
  10. 10. Results • 6,000 downloads since Aug. 3, 2010 • Active user & dev. forums • Press • We learned a ton.
  11. 11. What worked • Bringing together a group of do-ers • Ratio of doing vs. planning • Quick timeframe kept egos out • Diversity of skills on one team • Living & working together • Common goal
  12. 12. What didn’t work • More doing! • More cross-learning • Post-release, we have our day-jobs • Not enough time for UX
  13. 13. Future • Continue to develop tool – Recent 0.5 alpha release (10/2010) • Continue dissemination of software with online outreach and conferences • Apply for more grants
  14. 14. How is it different than our environment? • Ratio of Planning vs. Doing is flipped • Minimal risk-taking • We stay in our roles
  15. 15. One Week | One Tool http://oneweekonetool.org/ Anthologize http://anthologize.org Center for History & New Media http://chnm.gmu.edu/ Twitter #Anthologize Effie Kapsalis digitaleffie@gmail.com / @digitaleffie

×