I was in a meeting last week where someone remarked that he thought web development has become too specialized. Meaning  that us agency types may be over complicating projects by having ultra-specialized roles that create awkward handoffs, increase project costs and result in less efficient processes.

I’m the first to agree with limiting the number of cooks in the kitchen, yet it’s hard to ignore the fact that building websites today does require more specialized skills (and processes that can effectively integrate them). In fact, when it comes to CMS implementations, I’ve found that many projects go off track when the wrong people do the wrong tasks (i.e. Developer doing information architecture).

This prompted the question of ‘how many people does it take to screw in a content management system?’ A cynical myth buster may say ‘you don’t screw them in, they screw you’ – but we’re staying positive here.

Project teams will certainly vary based on project size and complexity. However, we’ve found the following roles are critical for success:

The Core Project Team
Almost all CMS implementations will need these roles.

• Project Manager: Essential to keeping the project on track, on budget, coordinating all the people and setting the right expectations every step of the way.
• Information Architect: Perhaps the most critical role in determining the website’s structure, navigation and taxonomy. Don’t start a project without one.
• Copywriter/Editor: Even the most distributed organizations need an editor to ensure a consistent voice, strategy and approach to content across the entire site.
• Front End Developer: Handles the CSS, XHML and all front end display templates, modules and widgets.  Typically a different role and skill set than an application developer.
• Web Designer: Even if you’re not redesigning the site, a web designer is key to ensuring the site brand, UI and styles get translated effectively into the new CMS.
• Developer: Responsible for the core CMS integration, custom application development and the messy technical stuff nobody else knows how to do. Prior expertise with your flavor of CMS is critical.
• Quality Assurance Engineer: Tests, tests and then tests some more. The key is having this role separate from the core development team.
• Business Users: You can’t forget the end users that need to be involved with this process from start to finish. They need education, hands-on mentoring, kind words and perhaps alcohol to get them through the process. Remember, this is new to them and not likely in their job description.
  

The Extended Project Team
Larger and more strategic implementations likely need these roles as well.

• Business Analyst: Sifting through complex organizational workflow and business processes requires careful thinking and an experienced analyst.
• Content Specialist: Responsible for handling the important tasks around how content gets classified and migrated. Works hand in hand with the Information Architects.
• Search Engine Specialist: Getting SEO right out the gate is a business critical task. An SEO expert will ensure the CMS implementation is in alignment with the SEO strategy.
• Database Administrator: As the technical complexity increases, so does the need for roles like a database expert.
• Analytics Expert: Organizations committed to measurement will need an analytics guru working alongside the development team.
• Web Strategist: A high-level strategic thinker can help guide the overall web strategy and tie it to the overall business goals. This person can also help determine how and when to implement new tactics such as social media, rss, podcasts and video.
• Flash Developer: Sites that have rich content delivery will require some expert attention from a Flash developer and/or designer.

So, add them up, and that’s a lot of folks. It’s important to realize these are roles and not necessarily unique people. However, it’s harder and harder to find those ‘Swiss Army knife’ folks that can bring best of breed thinking to each of these areas given the depth of subject matter expertise required. 

The most critical part is to understand what your project needs to succeed. Then audit your current team and prioritize how you invest in resources. The good news is there are plenty of external agencies, consultants and contractors who can augment your existing team. 

Do you agree with the above roles? Did I miss any? Bonus points for any funny punch lines to “How many people does it take to screw in a CMS.”