The agile approach is called many different names – scrum, sprints, agile. They all have similar concepts and they all work differently for each individual team. While building any type of software, whether it’s a website, phone app, or some type of cloud based CRM, the agile approach is the best way to go. Why, you ask? I’ll tell you, but first….
For those of you who don’t know, there are essentially two different approaches to web projects – waterfall and agile. Waterfall is your traditional approach to a project. An RFP is given to an agency. That agency wins the RFP by writing a killer proposal or one that’s priced according to the client’s budget. And the project begins, usually with a kick off meeting discussing important core features and business objectives. A discovery then occurs where developers come in and get a feel for the client’s information architecture (content types, categories, etc.) and database structure (fields, fieldsets, etc.). The designs are started and shown to the client, either with a yay or nay. And then the build takes place. The critical part to remember is that the design comes before the build in this approach. That means that you have to build according to the design and not the other way around.
This approach can be tedious – relentlessly. What happens if that design you made doesn’t fit right over the build you’re architecting? What happens if that little tiny icon over that image breaks the navbar? What happens if newsletter signup gets cut off on a tablet or mobile device? What happens if, what happens if? These are the questions you’ll find while taking a traditional approach. So, what we do is change that approach to be agile. It’s a cool word, right?
Agile is the evolution of collaboration and iteration unveiling the right solution. And you do this by prototyping the build first. There are some great core values that the agile approach preaches and you can find them written in the agile manifesto. You do all the normal things you would do in an engagement like a kick off meeting and a discovery phase where you learn about the company, objectives, structure and architecture. But when it comes time to get down to the nitty gritty, you prototype and then you iterate. And you start the design while you’re prototyping. What does this give you? It gives you a working, clickable, browsable, some-what designless website – what we call a gray site. But then you keep iterating and things start to take shape. It’s a process that lets you build a site that works properly and doesn’t lock you in to a final technical spec.
And trust me, the design will look good, great in fact! But it needs to sit on top of a fully functional website. What will make a visitor leave your site quicker? Not having that cool icon sitting over the image the way you wanted it to or having a website that loads slow and doesn’t function properly across all platforms? Yeah, I thought you’d say that!! So, if you run a team of developers and are thinking about going agile, I strongly recommend it.