Recomendados
Recomendados
Más contenido relacionado
Similar a Managing Projects In Digital Humanities
Similar a Managing Projects In Digital Humanities (20)
Más de Jeremy Boggs
Más de Jeremy Boggs (11)
Último
Último (20)
Managing Projects In Digital Humanities
- 1. Managing Projects in the Digital Humanities Jeremy Boggs Creative Lead, Center for History and New Media
- 2. C Jeremy Boggs Digital Dialogues, February 10, 2009 Five Phases • Strategy - The big picture • Scope - Specific requires and goals • Content - The Stuff. • Design - How the Stuff looks and works • Development - How to get the Stuff to the user.
- 3. C Jeremy Boggs Digital Dialogues, February 10, 2009 No phase should finish until the previous phase is finished
- 4. C Jeremy Boggs Digital Dialogues, February 10, 2009 Timeline for Project Strategy Scope Content Design Front-End Dev Back-End Dev
- 5. C Jeremy Boggs Digital Dialogues, February 10, 2009 Areas of Responsibility Branding Aesthetic How users interact with content Design Data Structure Programming Front-end and Back-end Content Development Text, Images, Video Information Architecture What users will interact with
- 6. C Jeremy Boggs Digital Dialogues, February 10, 2009 Strategy and scope encompass content, design, and development
- 7. C Jeremy Boggs Digital Dialogues, February 10, 2009 Strategy
- 8. C Jeremy Boggs Digital Dialogues, February 10, 2009 Strategy • Usually comes in the form of a grant • What you’re building, broadly. • Why???
- 9. C Jeremy Boggs Digital Dialogues, February 10, 2009 Gulag: Many Days, Many Lives
- 10. C Jeremy Boggs Digital Dialogues, February 10, 2009 Strategy - Gulag • Create resource for teachers and students to learn more about the Soviet Gulag • Archive hard-to-access sources • Provide ways for the public to share stories.
- 11. C Jeremy Boggs Digital Dialogues, February 10, 2009 Scope
- 12. C Jeremy Boggs Digital Dialogues, February 10, 2009 Scope • Tangible components to realize Strategy • Outlines responsibilities for each person • Translates user needs and objective into specific requirements to build. • Make a Scope Document!!!
- 13. C Jeremy Boggs Digital Dialogues, February 10, 2009 Scope - Gulag • Upload ~300 primary sources, with Russian translation • Create exhibit with ~20 pages, organized by theme • Create plugin to let users follow a prisoner through exhibit • Create a form to allow for public contributions
- 14. C Jeremy Boggs Digital Dialogues, February 10, 2009 Content • Information Architecture • Content Inventories • Site Maps
- 15. C Jeremy Boggs Digital Dialogues, February 10, 2009 Content Inventory
- 16. C Jeremy Boggs Digital Dialogues, February 10, 2009 Site Map
- 17. C Jeremy Boggs Digital Dialogues, February 10, 2009 Content Outcomes • Sitemap with overall structure of the site, relationships among pages • Inventory of content; what gos on each page or “state” in your project.
- 18. C Jeremy Boggs Digital Dialogues, February 10, 2009 Design
- 19. C Jeremy Boggs Digital Dialogues, February 10, 2009 Design = Communication • What do you want to communicate? • What do you want users to remember? • How do you want users to respond?
- 20. C Jeremy Boggs Digital Dialogues, February 10, 2009 Wireframes
- 21. C Jeremy Boggs Digital Dialogues, February 10, 2009 Point of Wireframes • Make sure all content is accounted for on each page; A visual content inventory. • Display relative importance of content • Serve as basis for...
- 22. C Jeremy Boggs Digital Dialogues, February 10, 2009 Color Mockups
- 23. C Jeremy Boggs Digital Dialogues, February 10, 2009 Pre-Mockups • Talk to stakeholders about look and feel • Create mood boards, color palettes • Help people make informed design decisions
- 24. C Jeremy Boggs Digital Dialogues, February 10, 2009 Design Critique • Designers: Explain WHY you made specific decisions • Avoid talking about likes: “I like green,” or “I don’t like Garamond.” • Do the design choices work for the message you want to convey, the experience you want to provide?
- 25. C Jeremy Boggs Digital Dialogues, February 10, 2009 Development
- 26. C Jeremy Boggs Digital Dialogues, February 10, 2009 Front End Development - HTML, CSS
- 27. C Jeremy Boggs Digital Dialogues, February 10, 2009 Back End Development - PHP, MySQL
- 28. C Jeremy Boggs Digital Dialogues, February 10, 2009 Don’t Reinvent the Wheel • Create a starter kit. • Use a CMS: Drupal, Omeka, WordPress • Use Frameworks: Zend, CodeIgniter, CakePHP • Use Libraries: Yahoo UI, Prototype, jQuery
- 29. C Jeremy Boggs Digital Dialogues, February 10, 2009 Strategies for Success • Make responsibilities, deadlines clear. • Efficient communication • Create a hub for sharing information
- 30. C Jeremy Boggs Digital Dialogues, February 10, 2009 Milestones Strategy Scope Content Design Front-End Dev Back-End Dev
- 31. C Jeremy Boggs Digital Dialogues, February 10, 2009 Milestones Strategy Scope Content Design Front-End Dev Back-End Dev
- 32. C Jeremy Boggs Digital Dialogues, February 10, 2009 Clear communication • Responsibilities - Assign roles, tasks. • Expectations, goals - Scope is important to all. • Meetings • Have a purpose, agenda, specific timeframe • Someone leads. • Evaluate afterwards.
- 33. C Jeremy Boggs Digital Dialogues, February 10, 2009 Project Management Apps - Basecamp
- 34. C Jeremy Boggs Digital Dialogues, February 10, 2009 Project Management Apps - Trac
- 35. C Jeremy Boggs Digital Dialogues, February 10, 2009 Project Management Apps - PB Wiki
- 36. C Jeremy Boggs Digital Dialogues, February 10, 2009 Provide a central place for project team to share info, keep track of progress.
- 37. C Jeremy Boggs Digital Dialogues, February 10, 2009 Be a Cheerleader!