Continue reading »]]>

Let’s face it.  No one creates a Digital Humanities project all on his or her own.  And personally, I like it that way.  DH is at its best when people from different backgrounds come together to solve problems, share research, create new knowledge, and improve teaching.  This exciting mix, however, leads to a particular set of challenges.  How do we keep inter-disciplinary, inter-generational teams working together in a reasonably harmonious fashion while also meeting the deadlines set by funding institutions?

To help answer (or at least start talking about) this question, I would like to propose a session on Project Management.  Some of us at THATCamp have served as official project managers, many more have been been unofficial managers, and almost everyone leaves a THATCamp with at least one idea for a new DH project they want to implement at their home institution.  I realize that there is a BootCamp already in the works on this topic.  But I think it could also work as a session with people of differing levels of experience with DH projects all pooling their knowledge.  So here are some questions we could discuss:

• What do people wish they had known before starting a DH project?
• For those contemplating their first DH project, are there pitfalls that can be easily avoided?
• What parts of a DH project end up taking the most time/using the most resources?
• How can projects scale up from a pilot project (often with only two or three people) to something longer term?

There is, of course, a large body of literature on Project Management, typically aimed at corporate managers and software development teams.  I wonder how useful those concepts would be in Higher Education.  If they are helpful, is there a way to make them more palatable to academics and alt-acs?

These are just some preliminary thoughts.  I look forward to discussing them (and so much more) come the weekend.