How the Software Development Lifecycle Relates to Website Redesigns

The general model for the software development lifecycle (SDLC) follows the same processes as a website redesign. As businesses embark on a website redesign, they can take tips from successful software development models in order to maximize the efficiency of their business processes. In both software development and website redesign, it the relationship between the roles, needs, and expectations  of the “team members”—ie.  the customers (stakeholders), the development team, design team, and the project management team–which can make or break the success of the project.

Both SDLC and website redesigns follow this general process:

Requirements gathering

Discussion with business owners/stakeholders on the desired functionality of the site along with big picture goals of what the site should be able to accomplish for the business. Sometimes, business owners will put forth a requirements doc that a project manager will craft into a scope document as a project plan for the team to follow.

Design

The designers work up wireframes. This is the first time architecture and site usability is addressed. In site redesigns, designers have to be in touch with the requirements document to know the desired “look and feel” of the site.

Implementation

This is where the developers get to code the site/software. In some iterative, development models testing works concurrently with implementation to  address issues as they arise before they become bigger, expensive problems.

Testing

Front end and back end testing is performed on other developers, customers, team members for bugs or other functionality issues and to QA the site/software for launch. Bug tracking software is good to keep track of all bug progress

Deployment (Launch)

The site is released to the customer. Maintenance issues are still tracked in bug tracking software, and training for the customers occur at this phase so they know how the front end works.

Audits

This is the area that most models fall apart, in my opinion. There is no on-going quality assurance about site functionality or analysis of overall impact of the project on the business.

• QA: Make sure that all the above elements remain intact for the life of the project. For example, six months after a redesign, ensure that the site’s design remains intact without too many additions and that proper code is maintained. If not, education is necessary at the customer level.

• Analysis: Analyze the impact of the project on the company in terms of time, resources, financial investment, and overall client satisfaction. Use project management software to identify where the project fell behind and target more training or resources toward that part of the project.

This is the first time I have ever thought about comparing  the software development lifecycle with website redesigns. I think traditional models do not account for the importance of the roles involved with the project and how each team interacts with one another. These processes take for granted that developers are effective at communicating with clients and that clients understand their needs well enough to communicate them to developers. In addition, many traditional models do not take a look at the project after it is completed and take note of where the challenges were and what can be done to address the needs and communicate learning from one team to the next.

Related Articles:

Does Your Business Have Online Intelligence?