A Look Inside Regal’s Unique Website Development Process

written by: Andrew Martin | May 19, 2016

0100

After explaining our web design and development process to a client (or prospective client), we’re often greeted with “huh…interesting. I’ve never heard of anyone doing it like that before”. It’s true, our process is unique and sometimes takes someone a bit longer to wrap their head around, but we believe we’re justified in our decision to break away from the typical website development process in favor of an agile process (based on Jeff Sutherland’s SCRUM process), simply because we’ve seen some incredible gains in efficiency since making the switch. We started out doing the same way most other agencies do, the traditional waterfall method, so we’re well versed in its strengths and weaknesses.

The Standard Website Development Process

Although workflows and processes vary from agency to agency, the standard website build project usually goes something like this:

1. A sitemap is developed
2. Once the sitemap is approved, wireframes are created
3. Once wireframes are approved, design comps are created
4. Once comps are approved, the website is developed (coded)
5. Bugs are fixed and the website is eventually launched

Regal’s Agile Website Development Process

After experimenting with several slightly different versions of the above process, we decided it was time for a radical shift, not only in order to become more efficient but also to create a better client experience. Our agile website development process looks like this

1. We define client goals and the goals of their users
2. We prioritize the goals and simultaneously design, develop, and test complete components and features
3. Every 2-3 weeks, clients are presented with fully functional web experiences they can evaluate on any device
4. We gather feedback and repeat the process until the site is ready for launch

Key Benefits

Those processes sure do differ quite significantly. Here are the main points that we feel make our agile website development process superior to the industry standard “waterfall method”:

1. Improved communication - rather than a specific department finishing a phase of a project, then handing it off to a separate department, team members with all skill sets work on a project at all points in the timeline, helping to prevent communication lapses and things falling through the cracks.
2. UX from day one - instead of showing our clients static wireframes and design comps early in the project, we provide them a web link to fully responsive, functional web experiences that they can test on any device. This results in quicker identification (and elimination) of user paint points.
3. Priorities change? That’s OK - we focus on the most important goals of our clients and their users first. As a project progresses, we work our way down the list. Rather than attempt to predict every iota of a project, we understand that clients change their minds, and new information becomes available. We adjust our sails to give our clients maximum value.

Different - and Damn Proud of It

Since switching to an agile web development process, we’ve seen faster builds, fewer bugs, and improved communication (internally and, most importantly, with clients). We’re always looking to improve ourselves and our workflow, and we’re confident we’re on course to continue to do so. If you’d like to see our unique web development process first hand, drop us a line; we’d love to hear about your business and help you tell your story.