1.
Web Project Management Strategies for chaotic web projects

2.
A Web Project… <ul><li>Building a few web pages for a client in town </li></ul><ul><li>Developing a simple web application that collects client information </li></ul><ul><li>Extensive Content Management System </li></ul>

3.
The Chaos <ul><li>Developer working out of their basement from 12-7am </li></ul><ul><li>Designer that doesn’t answer email </li></ul><ul><li>Client that wants to change something every other day </li></ul><ul><li>Content that hasn’t been written </li></ul><ul><li>Server hosting that is unreliable at the moment due to twitter outage </li></ul>

4.
A Project is… “a temporary endeavor undertaken to create a unique product, service, or result” – PMBOK Guide (2004)

5.
Triple Constraint <ul><li>Scope </li></ul><ul><li>Time </li></ul><ul><li>Cost </li></ul>

6.
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? How much do I charge for it? </li></ul>

7.
Dealing with the “what” <ul><li>Project sponsor (client) asks for something that needs to be built </li></ul><ul><li>Meet with client 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>

8.
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 month 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 would also like our users to sign in and have customizable features.” </li></ul>

9.
Learn a little from software engineering <ul><li>Understand clearly what you are doing </li></ul><ul><li>Risk management </li></ul><ul><li>Client management </li></ul><ul><li>Version control </li></ul>

10.
Define what you are doing.

11.
Break the project into manageable blocks

12.
What is the critical path?

13.
Clarity

16.
Developers

17.
Identify resources <ul><li>Who do you sub-contract with? </li></ul><ul><li>What can they do? </li></ul><ul><ul><li>Did you ask them? </li></ul></ul><ul><ul><li>Do you know or have you seen? </li></ul></ul><ul><li>Is there a line of communication between you and your resources even when not working together? </li></ul>

18.
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>

20.
Get the project sponsor 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>

21.
Learn how to use version control software.

25.
Use a process that works for you.

26.
Other methods? <ul><li>GTD </li></ul><ul><li>Waterfall </li></ul><ul><li>Agile/Extreme </li></ul>

27.
About me <ul><li>Jesse Rodgers </li></ul><ul><li>Member of the Special Projects Group at the University of Waterloo </li></ul><ul><li>Blog: http://whoyoucallingajesse.com </li></ul><ul><li>Email: [email_address] </li></ul>