Higher Ed Web Conference - Web Project Management

1,931 views

Published on

Presentation at Higher Ed Web in Milwaukee, WI in October 2009.

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

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

No notes for slide
  • Kanban wall
  • Higher Ed Web Conference - Web Project Management

    1. 1. Web Project Management<br />Strategies for chaotic web projects in Higher ed.<br />
    2. 2.
    3. 3.
    4. 4. A Project is… “a temporary endeavor undertaken to create a unique product, service, or result”<br /> – PMBOK Guide (2004)<br />
    5. 5. A Web Project is...<br />Building a few web pages for a department.<br />Developing a simple web application that collects student information.<br />Using Twitter/Facebook/Ning for whatever specific reason*<br />Extensive Content Management System.<br />
    6. 6.
    7. 7. A Project is… “ongoing, with many false starts and chronic scope creep. Governed by committee(s), success is not often tangible.”<br /> – Higher Ed.<br />
    8. 8. The Chaos<br />Developer comes in sometime after noon.<br />Designer that doesn’t answer email.<br />Department wants to see the term “pedagogy” on something aimed at parents.<br />Committees.<br />Never ending change requests.<br />
    9. 9. Learn a little from Software Engineering<br />Pick a dev strategy: understand clearly what you are doing<br />Version control<br />Issue tracking<br />
    10. 10. Project definition<br />First committee meeting needs a “memorandum of agreement”<br />Define the goals, objectives, and/or outcomes<br />Sign it.<br />
    11. 11. Follow a process, deliver a product.<br />
    12. 12.
    13. 13. Triple Constraint<br />Scope<br />Time<br />Cost<br />
    14. 14. Triple Constraint<br />What am I building?<br />How long will it take?<br />How much will it cost to develop?<br />
    15. 15. Dealing with the “what”<br />Project sponsor asks for something that needs to be built<br />Meet with committee and develop a clear scope along with timeline<br />Sketch out application<br />Call in resources you need<br />Develop application, get feedback, tweak, done.<br />
    16. 16. What really happens<br />“I would like a web site that looks like (insert newsworthy site of the week)”<br />“Next week would be perfect”<br />“Oh and can we have video?”<br />“And a live chat?”<br />“We want social media”<br />
    17. 17. Manage Resources<br />What are the skills and people available to this project<br />How much time do they have?<br />Is there a line of communication between you and your resources even when not working together in the same place?<br />
    18. 18. Identify risks<br />What could cause this project to be delayed or fail?<br />What will you do about them?<br />How much will it cost (time/money)?<br />
    19. 19. Break Project down<br />
    20. 20. Two week chunks<br />
    21. 21. Critical path<br />
    22. 22.
    23. 23.
    24. 24.
    25. 25. # S: (adj) agile, nimble, quick, spry (moving quickly and lightly) &quot;sleek and agile as a gymnast&quot;; &quot;as nimble as a deer&quot;; &quot;nimble fingers&quot;; &quot;quick of foot&quot;; &quot;the old dog was so spry it was halfway up the stairs before we could stop it&quot;<br />- http://wordnetweb.princeton.edu/perl/webwn?s=agile<br />
    26. 26. Image from http://www.flickr.com/photos/18091975@N00/<br />
    27. 27.
    28. 28. From http://www.flickr.com/photos/orcmid/3879384912/<br />
    29. 29.
    30. 30.
    31. 31. Agile process<br />
    32. 32. Agile process<br />
    33. 33. Get involved<br />Use Basecamp or excel or a word document<br />Break down the project for the sponsor (and you)<br />Provide time estimates for each phase<br />Follow-up with daily/weekly updates on progress<br />Share information.<br />
    34. 34. PM software?<br />Microsoft Project (larger teams)<br />OmniPlan (for the mac users)<br />Basecamp<br />
    35. 35.
    36. 36. Learn how to use version control software.<br />
    37. 37.
    38. 38.
    39. 39.
    40. 40. Version Control Software?<br />Github<br />Subversion (svn)<br />Team Foundation Server<br />CVS<br />Google Code (svn)<br />
    41. 41. Track the project.<br />
    42. 42. Issue tracking<br />Document milestones<br />Track conversations, changes, rationale<br />Generate reports (if you want)<br />Control your scope.<br />
    43. 43. Bugz<br />
    44. 44. Issue tracking software<br />Bugzilla<br />Trac<br />Team Foundation Server<br />Basecamp<br />
    45. 45. Use a process that works for you.<br />
    46. 46.
    47. 47. About me.<br />Jesse Rodgers<br />Associate Director, VeloCity -- University of Waterloo<br />Blog: http://whoyoucallingajesse.com <br />Twitter: http://twitter.com/jrodgers<br />Email: jrodgers@uwaterloo.ca<br />

    ×