Practical research project management
- 1. Managing Research Projects: Tips, Lessons Learned, and Project Management 101 PDW Workshop (HR) http://www.slideshare.net/vbuenger/Practica l_Research_Project_Management 8/9/2013 1
- 2. Session Guide • Intro—Credentials and Caveats • Peculiarities of Research Projects • Project Essentials 1. What does done look like? 2. What could block our path? 3. How do we get to done? 4. Do we have what we need to get to done? 5. How do we know if we are making progress? • Lessons Learned • Q & A 8/9/2013 2
- 3. Projects: What’s in Your Thought Bubble? 8/9/2013 3
- 4. Managing a Typical Project? • Tasks • Task Relationships • Durations • Milestones • Resources • Risks • Quality • Conflict DELIVERABLE! 8/9/2013 4
- 5. What Does Done Look Like? 8/9/2013 5 Shared Work Processes The Team. . . The Objective(s). . . The Project Triangle… Let’s Do It! Early Decisions Who does what and how do we hold each other accountable? Work Towards Publication
- 6. What Could Block Our Path? • Fear • Avoidance • Confused Priorities • Technical Difficulties • Distractions • Inertia • No Map 8/9/2013 6
- 7. Avoiding Train Wrecks • Unclear end points/scope creep • Team members have different project goals • Members don’t pull their weight • Members don’t understand their roles • Poor information about progress • Unclear responsibilities and handoffs • Lack of ownership • Inertia and distractions • Use your imagination! • Use your experience! 8/9/2013 7
- 8. How Do We Get to Done? • Shared Understanding: o Problem/Opportunity/Research Question o Team Structure—skills, talent, engagement o Scope o Key Deliverable(s) • Agreed Processes/Practices o Meetings o Guiding Principals • Alignment on Work Packages and Workflow 8/9/2013 8
- 9. Project Workflow 8/9/2013 9 Ideas •Development •Design Data •Data Gathering •Analysis •Re-Analysis Writing •Drafting •Crafting R&R •Submit •Revise •Re-submit Celebrate!
- 10. Do We Have What We Need to Get to Done? • People o Delegate. Let the people doing the work do the work o Tools. Give them what they need to do the job (authority, access, software) o Recognition. You can’t say thank you too often or too sincerely o Expectations. Set clear boundaries. Roles, responsibilities, commitment • Tools o Meetings o Documentation o Productivity Tools 8/9/2013 10
- 11. How Do We Know If We Are Making Progress? • Scripted Status Meetings • RAIID Tool o Risks o Actions o Issues o Interdependencies o Decisions • Punch List 8/9/2013 11
- 12. Lessons Learned Do this • Get agreement on what done looks like • Plan to hold regular project calls • Spread the work • Trust each other • Document as you go • Be patient--it will take longer than you think • Say thank you, often • Remember, you can do it! Don’t do this • Get too frustrated because team members have different habits • Worry or get mad when team members have to balance their university work with the project work • Expect everyone to think or work the same way Consider • What processes and scripts you will follow • When are your team members’ busy times • How can you celebrate small victories/milestones • What could derail the project and how can you respond 8/9/2013 12
- 13. Resources Meeting Tools: Doodle.com—corrdinating schedules FreeConferenceCall.com—conference calls SKYPE—video conference calls and sharing large documents Google Hangout—video conference calls FreeScreenSharing.com—centrally controlled slide shows Webex.com—centrally controlled slide shows Documentation: http://people.tamu.edu/~v-buenger/Templates/Minutes-Template.docx (case sensitive)--Minutes http://people.tamu.edu/~v-buenger/Templates/Agenda--Template.pptx (case sensitive)--Agenda http://people.tamu.edu/~v-buenger/Templates/Template_RAIID_Tool.xlsx (case sensitive)--Management Tools Productivity Tools: Document Sharing: G Drive Lockbox Media Fire Planning and Collaboration: Wizehive.com Basecamp.com (with tip sheet: http://people.tamu.edu/~v-buenger/658/basecamp_tip_sheet.pdf) 8/9/2013 13