Lachlan will walk you through the entire process of a web project from start to finish. Everything from the initial quote, getting the right client fit, getting design signoff, all the way through to getting final payment and launching. I will share anecdotes from a range of real life projects from large and small clients, as well as pointing out: Where things that can go wrong How to stop things going wrong Things to look out for ahead of time. How to keep a project on time and running smoothly.
MANAGING A WEB PROJECT
(From Start to Finish)
WHO AM I?
Ø Co-Founder of Brisbane design & development agency Sennza
Ø Organiser of the WordPress Brisbane Meetup group
Ø We work with both small and large companies including a number of ASX listed.
ØYou need to make sure you have the right client ﬁt
Ø Learn how to spot red ﬂags
ØYou will both be working together for many weeks.
An example of a WordPress enquiry
listed on Craigslist
There are no bad clients, just bad client fit
Flag designed by Wybe Minnebo from The Noun Project
ØHourly vs. Fixed Quoting
ØDeﬁne the scope of the project
ØAsk for a Budget
ØA budget is only helpful if you understand the value you can bring.
“We have received your initial invoice for these
costs and note that a 40% deposit has been
requested. It is the policy of Company XYZ that
we do not pay deposits for goods or services so
would like to negotiate diﬀerent payment terms
A real email from a client
Ø Scope of Work (who is responsible for what)
ØThe Project Timeline
Ø The Payment Schedule
All good contracts/proposals should include the following:
Large contracts vs Small contracts
Defining scope is all about stating on paper what is
otherwise obvious to you.
No excuse for not having a contract:
Set deadlines on when the client must respond
Afterall, you are held to deadlines!
Ø You do this for living! Your client does not. Help them understand how to get to the ﬁnish
ØExplain when/how often they can expect to hear from you. (No I don’t work on
ØKeep the project moving forward: http://unlessiheardiﬀerently.com/
ØAlways email a summary of phone calls when discussing changes. (Clients have great
Have a Process
We are so passionate about our process we made a video
Make it easy for your client:
ØMaybe a little too easy ;)
ØClients will give feedback
no matter what.
ØMuch better than 30 emails
back and forth.
ØAll feedback in one place
ØMuch easier for signoﬀ
Stick to the Scope
Ø What do you do if the client changes their mind?
Ø Do these changes count as a new project or are they additional feature requests?
ØHow do you handle additional work in your contract?
Does the client know what they are responsible for
You get out what you put in:
Ø What must you have from the client before you can start?
ØRemember the scope of work from the contract?
Does the client know what
they are responsible for
Weight Lifting designed by Scott Lewis from The Noun Project
Understand what your client sees:
Not a replacement for browser testing :)
(Of the project)
Finalise the Project
ØFocus on getting approval for what is in scope. (What you have control over)
ØLaunch date ≠ Project complete date. (Hosting or transfer the ﬁles)
ØThe end of the project is not the time to be making feature changes
ØIt’s a CMS, expect content to change
ØTheme Unit Test: http://codex.wordpress.org/Theme_Unit_Test
What I learnt from Google
Remove all ambiguity
The 3 best questions to ask when getting feedback:
1. What steps will reproduce the problem?
2. What is the expected output?
3. What do you see instead?
Other things that can help:
1. Invoice the ﬁnal payment
2. Take the site live
And in case you forget: Ownership transfers on payment!
Ø Using a staging domain allows the client to see and test the site in full before taking
ØOwnership transfers on ﬁnal payment (ALWAYS)
There are 2 deﬁnite ways to get the client to really look at the site:
ØIs it really the end?
ØMake sure the the client understands when the project ends and new work starts