Your Statement of Work should contain a line-by-line itemization of all tasks that are outside the native functionality of WordPress, without using plugins. By thoroughly documenting the features and functionality of your site up front and getting this signed off by the client, expectations will be set at a level that will bring easy success to the project and avoid simple miscommunications. When defining this before you start working, you are helping to facilitate an open and pleasant working relationship with your client while avoiding possible scope creep, and outlining who is responsible for what and by when. This session will walk you through the steps you should take when starting a new project to protect yourself using good documentation practices, while meeting the requirements set by your client.

Below are the slides for my WordCamp Boston presentation, “Don’t Do Anything Without A Statement Of Work”.

Published by Suzette Franck

Suzette Franck has been in web development for over twenty years; she started making hand-coded HTML websites on geocities with font tags and tables back in 1995. Since then, she has taught herself CSS, Sass, PHP, MySQL, as well as becoming a Wordpress expert; evangelizing and presenting at over twenty-two WordCamps across the country and multiple WordPress meetups in Southern California where she resides, about all aspects of building and maintaining sites on WordPress. Suzette is passionate about WordPress the application as well as the WordPress Open Source Community, and loves to code and teach others the wonders of WordPress. She is a purveyor of lowbrow art, and when she is not WordPressing, she is painting or visiting Los Angeles art galleries to add more work to her growing art collection.

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.