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.

How to Rock the Planning Process for your Next Digital Library Web Project

1,602 views

Published on

Does thinking about web projects for digital libraries make you feel as though you're trapped between a rock and a hard place? You will need to engage digital library partners and stakeholders; collect and analyze diverse data streams to understand use of your current digital library; define the roles of project team members; develop a comprehensive communication plan that serves a diverse audience; produce and disseminate project plans; and that’s all before web development of the project even begins! Talk about a Sisyphean task! Instead of pushing that rock up the mountain only to have it tumble back down again, join us for a presentation that highlights effective strategies for planning digital library web projects. This presentation will describe the planning process for the University of Houston Digital Library Redesign Project. We’ll tell you how we rocked it and we’ll point out where things got rocky. No matter what web project you are hoping to initiate for your digital library, you can be the project planning rock star.

Published in: Education
  • Be the first to comment

How to Rock the Planning Process for your Next Digital Library Web Project

  1. 1. How to Rock thePlanning Processfor your Next Digital LibraryWeb ProjectRachel Vacek and R. Niccole WestbrookTCDL 2013
  2. 2. University of HoustonDigital LibraryRedesign Project
  3. 3. Create Buy-In
  4. 4. Define Roles andResponsibilities of Teams
  5. 5. Project TeamCoordinator of Digital OperationsWeb Services CoordinatorHead of Web ServicesHead of Digital Services
  6. 6. Project LeadsCoordinator of Digital OperationsWeb Services Coordinator
  7. 7. Project LeadsCoordinator of Digital OperationsWeb Services CoordinatorHead of Web Services
  8. 8. Usability TeamCoordinator of Digital OperationsWeb Services Coordinator
  9. 9. Development TeamWeb Projects ManagerWeb Developer 3Web Developer 2Web Designer
  10. 10. Dream TeamWeb Projects ExpertDigital Library ExpertCuratorial ExpertUsability ExpertMetadata Expert
  11. 11. Create a ProjectTimeline
  12. 12. UHDL Redesign Timeline
  13. 13. Revised UHDL Redesign Timeline
  14. 14. Create a ProjectTimelineTask List
  15. 15. Gather Data
  16. 16. Plans & Reports• Stakeholder Interview Report• Project Plan• Usability Plan• Feature Brainstorming Report• Data Report• Usability Testing Reports• Developer Proposal
  17. 17. Collaborate onDecision Making
  18. 18. Collaborative Decision Making• Cut apart parts of project request andprioritized features as mandatory and desired• Frequent emails• Meetings at major advancements or whenmore discussion was needed
  19. 19. Write aProject Plan
  20. 20. Project Plan Challengesand Lessons Learned• Each Project Lead was responsible fordifferent sections• Used Google Docs– Kept track of versions/changes– Utilized commenting features• Developer involvement• Balance between creativity and exactspecifications
  21. 21. Transition toDevelopment
  22. 22. Different Understandings• Audiences for Project Plan• Scrum and agile product development• CONTENTdm• Ongoing usability testing• Feedback• Deadlines
  23. 23. Take Aways
  24. 24. Take Aways• Define roles and responsibilities whenestablishing a project team• Communicate• Manage expectations• Be realistic about time estimates
  25. 25. Photo Credits1. John Rudolph http://www.flickr.com/photos/johnrudolph/5865618809/2. University of Houston Digital Library http://digital.lib.uh.edu/3. randallo http://www.flickr.com/photos/randallo/4833097511/4. Martin Burns http://www.flickr.com/photos/martinb/29121316/5. Chuck Coker http://www.flickr.com/photos/caveman_92223/2692883227/6. Ziggy Stardust [citation]7. Klaus Hiltscher http://www.flickr.com/photos/khiltscher/3209570557/8. Jim Summaria http://commons.wikimedia.org/wiki/File:Mick_Jagger_and_Ron_Wood_-_Rolling_Stones_-_1975.jpg9. Brent Pearson http://www.flickr.com/photos/brentbat/1557036097/10. Steve Lacy http://www.flickr.com/photos/steve_lacy/140153319/11. Dom W http://www.flickr.com/photos/dom_w/1508297891/
  26. 26. Rachel VacekHead of Web Servicesrevacek@uh.eduR. Niccole WestbrookCoordinator of Digital Operationsrnwestbrook@uh.eduUH Digital Library Redesignhttp://weblogs.lib.uh.edu/uhdlredesign/UH Digital Libraryhttp://digital.lib.uh.edu/(New design will go live in June 2013)TCDL 2013Thanks!

×
https://www.slideshare.net/vacekrae/rocking-rocks2
www.slideshare.net
crawl=CC-MAIN-2018-47
181958
application/http; msgtype=response
sha1:AAYUCFD32BSVTJ4ZKI7VN6IYC3RT5GDS
<urn:uuid:1756636b-9cdf-4cff-9f0d-d685c6545e1a>
2018-11-16T14:04:26Z
108.174.10.19
text/html
sha1:TCYIQ2UON54UBA4EPNWI3FCH3CIUNXMZ
<urn:uuid:5360a309-6990-4574-93b0-e6b17d1fbb14>
https://www.slideshare.net/vacekrae/rocking-rocks2
response
<urn:uuid:c85d32ce-fe10-40a4-8ed5-8aa8fc73ecf2>
isPartOf: CC-MAIN-2018-47
publisher: Common Crawl
description: Wide crawl of the web for November 2018
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-71-191-109.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/