Digital Project Success


Published on

A few hints and tips for groups and individuals carrying out digital projects

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

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Digital Project Success

  1. 1. Digital Project Success: TurningVision into Execution ! Shawn Day Digital Humanities and the Study of Literature
 8 May 2014
  2. 2. Objectives of this Talk ‣ You’ve Got a Great Idea ‣ You’ve Just Got Funded ‣ So …What do you do next?
  3. 3. Shape of this Talk ! 12 Observations/Reflections on Digital Project Success ‣ Planning Projects ‣ Setting Goals ‣ Managing the Digital Challenge ‣ Tools
  4. 4. Who has taken a course or
 training in Project Management?
  5. 5. Project management as a whole is iterative Evaluate Design ImplementMonitor
  6. 6. Considering the User in order to in order to Study /Consider the likely Audience
 for your Research Product - Potential Users Set Project Goals and Create a Project Plan Manage the Project and Achieve those Goals
  7. 7. #1 : Why the End belongs at the Beginning ‣ The importance of finishing ‣ The importance of finishing well ‣ The importance of knowing what finishing means ‣ The importance of planning for what happens 'after you finish' ! ‣ Build into Budget / Funding
  8. 8. #2 : Set Project Goals & Create a Project Plan ‣ It’s important to define exactly what the project aims to achieve: ‣ What will be achieved? ‣ Under what conditions? and; ‣ With what partnerships will it succeed? ‣ Rank your goals in terms of importance. ‣ In case time, money, or both run out, what is most important?
  9. 9. The Project Plan Should Contain: ‣ Project phases ‣ In case limited resources prevent you from accomplishing all that you plan to, the most important and/or easiest work (in the earliest stages) will still get accomplished - remember our priorities? ‣ A timeline showing how things come together: ‣ What and when, including dependencies ‣ —> The GANTT Chart
  10. 10. GANTT
  11. 11. #3 : Establish a Project Charter ‣ Put it on paper; ‣ A Formal statement of work: ‣ Objectives ‣ Possibly values in a forward thinking project; ‣ Where will the project be at the end?; ‣ Allow for change as project progresses; ‣ ideally should be organic and fluid
  12. 12. #4 : Don’t Reinvent theWheel ‣ Again before you start... ‣ Take a good look around - Environmental Scan ‣ Good digital project managers don’t re-invent ‣ They adapt and innovate ‣ They Learn from others experience ! ‣ Steve Jobs: ! "Good Artists Copy - Great Artists Steal!"
  13. 13. #5 : Write it down - Document! ‣ Not everyone interprets or recalls the same initial or subsequent project discussions in the same way! ‣ When groups involved, it’s crucial to have memos of understanding ‣ > but these make great sense for individuals too! ‣ Write out your objectives and turn to them throughout; ‣ Revise and document why revised; ‣ As simple as a project or group blog/wiki.
  14. 14. #6 : Make Steps Small and Achievable ‣ Divide the project into discreet and manageable tasks; ‣ Identify all tasks that need to be performed for a particular activity: ‣ divide tasks into component parts; ‣ Be realistic about the time an activity will take; ‣ Break down tasks into reasonable time-units; ‣ no point in setting unrealistic goals ‣ Leverage the Tools
  15. 15. #7 : Stay Fluid andWork the Plan ‣ Perhaps the most crucial part of project management is an ongoing process involving: ‣ Flexibility: know when to stop and change plans; ‣ Adherence: know when to stick to the plan; ‣ Communication: know who needs to know what when; ‣ Damage Limitation: when things go wrong how to fix them.
  16. 16. #8: Have a Plan B (and C…) Things GoWrong ‣ Delays often arise because time estimates are too short. That’s why you plan for project phases. ‣ On the other hand, internal deadlines are useful for keeping forward momentum, especially on any long-term project. ‣ Revisit the project plan often and decide when to revise the plan and when to stick to it. ‣ Remember that Project planning is iterative … just like user testing!
  17. 17. #9 : Release Early, Release Often ‣ Learn from your users; ‣ Catch the unanticipated; ‣ "Many eyes make all bugs shallow" ‣ Late release with late discovery can leave no Plan B
  18. 18. #10 : Tear Up the Funding Proposal ‣ Make the Plan fit the purpose ‣ Not to diminish the initial effort in putting it together ‣ There’s a reason funding agencies ask for particular bits of info ‣ Make them work for all purposes ‣ But don’t mistake one tool for another
  19. 19. #11 : Communicate ‣ Regularly ‣ Routinely ‣ Transparently ‣ Emerging Tools ‣ Slack ‣ Trello ‣ Use the ones people actual use
  20. 20. People have different communication styles and preferences Asynchronous (delayed) Synchronous (instantaneous) in writing ‘live’ does not necessarily break concentration requires interruption from work allows time for reflection easier to keep track of discussions Find an appropriate mix of the two and appropriate tools for each.
  21. 21. Some simple communication tools Asynchronous (delayed) Some of both Synchronous (instantaneous) Email! Online forums! Word Docs! Wikis Google Docs! Google +! PiratePad Instant Messaging! VoIP (like Skype)! Meetings! Chatting at someone’s desk Over the phone
  22. 22. Trello
  23. 23. Slack
  24. 24. # 12 : Keep an Eye on the Big Picture ‣ All the projects you will be working on will reside in a larger context of digital projects worldwide ‣ What is the current expectation by potential users? ‣ What new communities may benefit from your resource? ‣ What other projects will yours be in dialogue with? ‣ Digital arts and humanities projects in Ireland and the UK ‣ how will these projects fit together? ‣ what interoperability and synergies can be achieved? ‣ In the rapidly changing environment of the web ‣ how do new technologies affect your project plan? ‣ changing expectations of users?
  25. 25. ThankYou Shawn Day - - @iridium ! The Library/Institute for Collaborative
 Research in the Humanities
  26. 26. The Conceptualisation
 (re)process after Funding ‣ Take a look at process at TAPoR2 ‣ Why? A very robust Digital Humanities Project … and an exercise in User-Centred Design ! ‣ Objective -> Scan -> Stories -> Scenarios -> Use Cases -> Wireframes -> Prototype -> Test -> Iterate -> Document -> Release -> Repeat!
  27. 27. Digital Project Management Tools ‣ Defining ‣ Planning/Documenting ‣ Compiling ‣ Managing ‣ Executing ‣ Learning/Reviewing