Right-sizing project management and tracking

1,181 views
1,064 views

Published on

UNC CAUSE 2010, Wilmington NC

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,181
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Right-sizing project management and tracking

  1. 1. Right-sizing project management and tracking Joel Dunn Gloria Thornton Laura Young UNC Greensboro November 10, 2010 1
  2. 2. Why is it hard to pick a project tracking/management system? Some methods are too small and simple Some methods are too big and complex You need to seek out a method that’s just right for the requirements and culture of your institution 2
  3. 3. History at UNCG... we’ll walk you through the steps No system First steps Comprehensive enterprise project management system Purpose-built system for UNCG 3
  4. 4. Why is it hard to pick a project tracking/management system? 4 It’s somewhat like the story of the 3 bears... Images from http://openclipart.org
  5. 5. But before the three bears... We had: No system Project management by intuition, guess and luck! 5
  6. 6. First steps: My porridge is too cold... Rudimentary project time tracking Some useful information for retrospective analysis Didn’t help with managing expectations on what we could do when So, let’s kick our game up a notch! 6
  7. 7. Comprehensive system: My porridge is too hot... Planview selected after careful review Capable and powerful ...yet complex and didn’t match business processes for project lifecycles Frustration! Not used in all work teams Incomplete data reinforced the frustration Client concerns, questions about value of tool and value of project management 7
  8. 8. Purpose-built system: My porridge is just right... Decision to look at business processes first How do we prioritize projects? How do we allocate resources? Work with existing IT governance, but seek to provide actionable data! Create a simple software system to support the vision 8
  9. 9. The result: 9
  10. 10. Sidebar: IT Governance at UNCG - committees 10
  11. 11. Sidebar: IT Governance at UNCG - committees 11 Administrative Systems Committee DSC ASUG ASTG ASSC •DSC = Data Standards Committee •ASUG = Administrative Systems Users Group •ASTG = Administrative Systems Technology Group •ASSC = Administrative Systems Security Committee Future direct reporting of ASSC to ASC
  12. 12. Timetrack methodology Focused on the reports we need to give our administrative computing governance groups to support their decisions Determine meaningful granularity of information Divide IT work efforts into modest number (15-20) of skill-sets relevant to clients Estimate hours that can be allocated to “scheduleable” projects (net of maintenance, patches, break/fix, etc.) Infrastructure project requirements reserved Institutional project requirements reserved 12
  13. 13. Timetrack methodology Don’t starve the small work efforts Hold some hours in “small project” reserve These work efforts <80 hours, only one or two skill-sets Don’t need full methodology or project manager 13
  14. 14. Timetrack methodology Don’t allocate all hours Hold contingency reserve Only allocate 1/2 to 3/4 of remaining hours; hold until mid- year review and “true up” 14
  15. 15. Results... Rationally predict what projects can be done in a given year Communicate in an open, transparent way with campus stakeholders (they can understand the methodology) Empowers UNCG to have productive discussions about opportunity costs of inevitable mid-year “must do” work efforts; resolve in a way that is clear and fair to all involved 15
  16. 16. Timetrack 16 Overall view of resources (skill- sets)
  17. 17. Timetrack 17 Project list, for use by divisional coordinator
  18. 18. Timetrack 18 Point-in-time view of individual project, for use by project manager, resource manager, or divisional project coordinator
  19. 19. Timetrack 19 Time entry, for use by project resource
  20. 20. Timetrack Demo and discussion 20

×