It’s admirable how this illustration of the average web design project plan condenses the essentials. It shows the common sequence, level of involvement, milestones, priorities and phases of all in one infographic. A source of inspiration and a good reference to base a template on.
Read on for my comments and the full size plan.
The plan doesn’t show iterations which is often the case in smaller web projects, certainly if the back-end isn’t too complex you won’t be going back to a previous phase.
I find planning for iterations quite important so when constraints allow it, I make room for iterations at least inside the content, design and development phases respectively. If you’re adding buffer to your estimations, you’re already kind of doing this but it’s better to make it explicit. My guess is that they probably left the iteration part out of the illustration to keep it more coherent.
Also interesting to notice in the illustration is that they put the content phase before the design and development phase. Putting content first is not only smart, it’s the only way to do this kind of project properly. I’ve seen many projects where people insisted they wanted to do this the other way around, building the pretty box first and trying to fix stuff in it afterwards; bad order, costs a lot more too. And that’s a shame.
The infographic in full size … (right click on the links, save as … to download):
Web Design Project Plan in JPEG
I’m archiving this as inspiration for future project planning templates.
Social Widgets powered by AB-WebLog.com.