Loading...

/> Our Agile Web Development Process

1. Discovery and Ideation

We review your project goals and vision with you in detail to hash out the core set of requirements. In this phase, we ask a lot of detailed questions as your answers shape the scope of the project. Things discussed include technology requirements, features, deliverables, etc.

We love ideas, so expect us to bounce some off of you to expand upon your vision from our eyes. This helps us refine our specifications and increase your ROI.

This phase also helps us determine if we're a good fit for your project (and if your project is a good fit for us).

2. Analysis

Once we have uncovered all project specifications from you, we take the time to analyze your project with a fine-tooth comb.

Internally, we compile a detailed, itemized list of pages and page functionality required to complete the project in it's entirety. Large project features are broken apart into sub-features so that we can more accurately estimate time to completion.

This finalized list is included in our project proposal and contract to you as a means to indicate exactly what is to be delivered on project completion.

3. Agile Development

The development phase is where the bulk of our time is spent. We work in one-week blocks, called sprints, where we have a pre-determined set of features defined that we estimate will be completed by the end of the week. This process helps us to more accurately gauge our completion date.

At the end of each week, we deliver project status updates to our clients via their preferred method of contact: phone, Skype, screen sharing, etc.

We are preferential to using git as our version control system, but are open to using subversion upon request. Internally we use a deployment methodology based off of the original gitflow model.

4. QA & Testing

Upon completion of the development portion of your project, we perform rigorous testing of the use cases of your website to try and coax out any bugs. Likewise, we provide you with access to your site so that you may begin internally testing.

During this phase, you are also responsible for viewing the private copy of your project and notifying us of any issues you find or changes you would like implemented. You are expected to verify that all of the deliverables have been accounted for as indicated on the contractual agreement.

5. Project Delivery, Deployment, and Launch

The final phase is deployment, where we set up your hosting environment, deploy the project, and get the site up and running.

We use the term launch loosely, as you may simply want us to get your project up and running locally for you to continue development and testing internally before publicly launching.