Successful Website Development:
Applying CMMI^® Software Development Methodologies

by Victoria Scott, PMP, Project Manager
Steve Pahner, Web Developer/Technical Lead

Web design projects can be tricky: with an overwhelming amount of constantly changing information and competing priorities, scope creep and meeting project deadlines can become a management nightmare. By applying the CMMI^® Software Development Lifecycle model to website projects, ActioNet, Inc. has developed a standard Website Development lifecycle to manage these issues and bring winning results to our customers.

Involvement
A common misconception is that once a contractor is selected to perform work, customer involvement is over. In reality, customers hold all the knowledge needed to create a high-quality website – the contractor’s job is to “pick their brains” and pull out this information. Therefore, a dedicated and forward-thinking customer “Working Group” is essential to the success of any web project. In addition to Subject Matter Experts (SMEs) in each of the customer’s key business areas, it’s important to have a single site owner who will champion the site to the rest of the organization. The site owner has one of the most important roles – they must understand the organization’s “big picture” to bring together all the SMEs’ detailed information in a single coherent site. They help direct and unify both the SMEs and the organization’s executive management to create a common vision and buy-in to the effort.

Requirements
Gathering requirements is the first step in the lifecycle of both software and website projects. Instead of collecting data fields and security requirements, website projects collect information about site audiences, hierarchy, organization, and navigation. Customers can find this step challenging; not only are they getting used to working together and learning the lifecycle, but they are expected to divorce the site’s appearance from its organization. It is important to delay the site’s design until requirements are complete. If introduced prematurely, the creation of designs during this phase can be a major distraction and can actually end up delaying the project’s delivery date. Instead, focus on site organization and navigation, developing the site’s navigation in a logical and intuitive way with the organization’s target audience in mind as the most important task. This aspect may result in future savings for the customer. When the next web “refresh” comes up, the visual look of the site can be changed, but if organized effectively, the navigation won’t need to be.

Design
Many customers see the design phase as the most important aspect of the website, with good reason. Web pages are very aesthetic in nature. The design of the site acts as a virtual representation of the customer to their intended audience. If the site doesn’t appear to be professional and current, the audience may not trust its content. Several design options are typically presented; selecting one or marrying several to create the final design can be time-consuming. All design options should incorporate the customer’s general preferences for layout, color scheme, and navigation. Reducing the modifications needed to finalize design will help everyone focus on aspects of design that they have not already considered.

Testing
Another common misconception is that only minimal testing is required for websites in contrast to software. Various types of testing are required. For example, Federal websites need to comply with required policies and other regulations (such as Section 508), so a detailed test plan is critical. A series of Peer Reviews completed during the Design phase can reduce this testing cycle.

Implementation and Maintenance
One of the most common mistakes in web redesign is failing to plan for site maintenance. Without clearly documented maintenance protocols that define the expectations and tasks for site maintenance and the roles and responsibilities for all parties involved, the shiny new site will quickly become tarnished and underused. The site owner again plays a critical role in ensuring resources are available to perform these tasks and that all involved parties are invested in the site’s upkeep.

Conclusion
Web projects can be made manageable and highly successful by involving the right customers for the job and following a defined Website Development Lifecycle. Communicating this lifecycle to the customer and explaining what’s expected of them at every step provides them with the tools they need to provide the right feedback and take control of their website.