• YouTube - Division 1
  • Google Plus - Division 1
  • Twitter - Division 1
  • Facebook - Division 1

Our Web Development Process

At Division [1] we have helped complete hundreds of web-based projects and have developed a comprehensive development strategy over the years. This strategy helps us organize, use resources effectively, and stay focused on shipping a successful project at the end of the day. Sometimes developing a large project over a significant amount of time can seem daunting in scope. Our project management system with its milestones, to dos and message threads keep the project broken down into byte (ha) sized chunks that help everyone work as a team towards a successful end goal.

When we first started taking on projects, the tendency was to dive right into the project and start programming right away. This is the development equivalent to just nailing boards together and hoping it makes a house when you are finished. Any project worth applying oneself to is worth thinking about first. We also believe there is such a thing as too much planning and bureaucracy which can cause a project to stagnate and miss out on time sensitive launch advantages. We strive to find the appropriate balance between resisting the urge to impatiently jump the gun and getting tied up in over planning — losing the passion and excitement of a fresh project or idea.

Our Development Process

Strategy and Research

  • Together the development manager and client identify and define the project, goals and any special requests
  • The client and the developer list great examples of website and software products and explain what makes them outstanding.
  • The development manager and client separate core features the project cannot live without from later "nice to haves" and future feature sets
  • The client receives project management software orientation including an explanation of milestones, to do lists and message threads
back to top

Front End and GUI Design

  • The Graphic User Interface ( GUI ) is used to describe the visuals and layouts that allow a user to access and navigate a website or application
  • Samples of landing pages and content pages are designed as templates for further page development
  • The designer creates sample page layouts, typography, buttons, modal screens and data entry forms for the client to review
  • Any responsive scaling issues are identified and addressed
back to top

Wireframe and Page Layout

  • The project is laid out in a PDF based series of sketches
  • The wireframe shows the general functionality of all pages, forms, processes, and layouts as well as the general site architecture and how each page relates to the others
  • Using a wireframe document allows for dramatic changes in a short period of time; ideal for the brainstorming process
  • The client gives their feedback and approval and the document is used as a reference for page layout and programming
  • A blank beta site is launched with the approved framework according to the project type
  • The developer adds the page structure to the beta site according to the page hierarchy in the wireframe document
  • The developer adds all content, graphics, photos and effects to each page
back to top

Back End Programming

  • The hosting account and beta site CMS framework are created
  • The database(s) creation and connection to the framework
  • Programming of web forms and notifications according to the wireframe
  • Any approved external APIs or XML feeds are integrated
  • Completed programming is soft tested, repaired and sent to the Quality Assurance ( QA )
  • Testing script with permissions is prepared and posted
  • The developers work with the QA to fix bugs, solve issues and then re-test the programming
back to top

Quality Assurance Beta Testing

  • The tester reads and executes product testing script
  • The tester checks usability and double checks for formatting and design errors
  • The tester completes all forms, processes and checks all links in the project
  • The tester compares cross browser and cross device compatibility and functionality
  • All errors, bugs, omissions, screenshots and reproduction steps are recorded in a testing report
  • The QA team works with the programmer and front-end designer to re-test until all known issues are closed
back to top

Finalization and Project Launch

  • After the site is tested internally and externally, the beta site is presented to the client
  • The launch schedule is agreed upon by the client and developer
  • All profiles and passwords necessary for launch are prepared and tested
  • The client submits their feedback and works together with the development team to finalize any last minute issues
  • The final sign off from the client and approval to launch is given
  • The project is finalized and a back-up is created
  • Heightened awareness from the development team during launch allows any post launch issues to be resolved quickly
  • A follow up plan for future developments and improvements is created during the final meeting between client and developer
back to top

We do modify our development process from time to time. Our industry, like many others, is constantly changing and new tools and processes sometimes emerge allowing us to modify the way we work in order to save time, materials and money. We believe in always looking for a better way to launch successful projects for all of our clients. Division [1] strives for long term working relationships in every project we take on.