Web Project Management

1,589 views
1,500 views

Published on

Presentation from HighedWeb Regional conference

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

No Downloads
Views
Total views
1,589
On SlideShare
0
From Embeds
0
Number of Embeds
53
Actions
Shares
0
Downloads
60
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Web Project Management

  1. 1. Web Project Management <ul><li>Strategies for chaotic web projects in Higher ed. </li></ul>
  2. 4. <ul><li>A Project is… “a temporary endeavor undertaken to create a unique product, service, or result” </li></ul><ul><li> – PMBOK Guide (2004) </li></ul>
  3. 5. A Web Project is... <ul><li>Building a few web pages for a department. </li></ul><ul><li>Developing a simple web application that collects student information. </li></ul><ul><li>Extensive Content Management System. </li></ul>
  4. 7. <ul><li>A Project is… ongoing, with many false starts and chronic scope creep. Governed by committee, success is not often tangible. </li></ul><ul><li> – Higher Ed. </li></ul>
  5. 8. The Chaos <ul><li>Developer comes in sometime after noon. </li></ul><ul><li>Designer that doesn’t answer email. </li></ul><ul><li>Department wants to see the “pedagogy” on something aimed at parents. </li></ul><ul><li>Committees. </li></ul><ul><li>Never ending change requests. </li></ul>
  6. 10. Learn a little from Software Engineering <ul><li>Pick a dev strategy: understand clearly what you are doing </li></ul><ul><li>Version control </li></ul><ul><li>Issue tracking </li></ul>
  7. 11. Triple Constraint <ul><li>Scope </li></ul><ul><li>Time </li></ul><ul><li>Cost </li></ul>
  8. 12. Triple Constraint <ul><li>What am I building? </li></ul><ul><li>How long will it take? </li></ul><ul><li>How much will it cost to develop? </li></ul>
  9. 13. Manage Resources <ul><li>What are skills and people available to this project </li></ul><ul><li>How much time do they have? </li></ul><ul><li>Is there a line of communication between you and your resources even when not working together in the same place? </li></ul>
  10. 14. Dealing with the “what” <ul><li>Project sponsor asks for something that needs to be built </li></ul><ul><li>Meet with committee and develop a clear scope along with timeline </li></ul><ul><li>Sketch out application </li></ul><ul><li>Call in resources you need </li></ul><ul><li>Develop application, get feedback, tweak, done. </li></ul>
  11. 15. What really happens <ul><li>“I would like a web site that looks like (insert newsworthy site of the week)” </li></ul><ul><li>“Next week would be perfect” </li></ul><ul><li>“Oh and can we have video?” </li></ul><ul><li>“And a live chat?” </li></ul><ul><li>“We want social media” </li></ul>
  12. 16. Identify risks <ul><li>What could cause this project to be delayed or fail? </li></ul><ul><li>What will you do about them? </li></ul><ul><li>How much will it cost (time/money)? </li></ul>
  13. 17. Break Project down
  14. 18. Two week chunks
  15. 19. Critical path
  16. 23. <ul><li># 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; </li></ul><ul><li>- http://wordnetweb.princeton.edu/perl/webwn?s=agile </li></ul>
  17. 26. Agile process
  18. 27. Agile process
  19. 28. Get involved <ul><li>Use Basecamp or excel or a word document </li></ul><ul><li>Break down the project for the sponsor (and you) </li></ul><ul><li>Provide time estimates for each phase </li></ul><ul><li>Follow-up with daily/weekly updates on progress </li></ul><ul><li>Share information. </li></ul>
  20. 29. <ul><li>Learn how to use version control software. </li></ul>
  21. 33. <ul><li>Track the project. </li></ul>
  22. 34. Issue tracking <ul><li>Document milestones </li></ul><ul><li>Track conversations, changes, rationale </li></ul><ul><li>Generate reports (if you want) </li></ul><ul><li>Control your scope. </li></ul>
  23. 35. Bugz
  24. 36. <ul><li>Use a process that works for you. </li></ul>
  25. 38. About me. <ul><li>Jesse Rodgers </li></ul><ul><li>Associate Director, VeloCity -- University of Waterloo </li></ul><ul><li>Blog: http://whoyoucallingajesse.com </li></ul><ul><li>Twitter: http://twitter.com/jrodgers </li></ul><ul><li>Email: [email_address] </li></ul>

×