Agile or Waterfall? The answer is never quite that simple. Depending on the specifications, budgets and breadth of your project, Access Technologies may use either a more traditional waterfall process or an agile software model to develop your software. Like any method, each has its own benefits and limitations, but an experienced Access project manager will consult with you to see which model or combination of the two will be the best fit for your project, budget, and timeline.

Traditional Waterfall Development Model

At Access Technologies, we believe that the Waterfall Development Methodology works best for clients whose software specifications are relatively stable and where requirements are not volatile. Since development is done as per a specified scope, the process is relatively structured and works well if a fixed budget and a set turnaround time for the product are important to the client.

This process is beneficial as the time investment from the client is largest during the initial phase of the project, and exponentially reduced during the Design and Development phase to simply check points and approvals. For precisely the same reason, for larger and more loosely defined projects – this model can be risky as the client is unable to review and give feedback until the end of the project. However, at Access Technologies, we overcome this disadvantage in the Waterfall Development Methodology by dynamic wireframing.

  • Organized and stable development
  • Predetermined project specifications before design
  • Well-managed timetables
  • Cost-effective for the client

Agile Software Development Model

Agile Software Development works well for clients whose businesses are volatile and constantly evolving – so quickly that the business requirements change by the time the requirements gathering phase is complete!

At Access Technologies, this iterative methodology is frequently used, requiring intense collaboration and self-editing across several teams. Minimum product requirements are gathered by an assigned Project Manager or “Scrum Master” and move in parallel into development and testing. At Access Technologies, we use Agile for clients who need a more responsive process and are in need of shorter turnaround times.

The main limitation for the Agile Software Development model is that due to its flexible and responsive nature, project budgets and timelines are more uncertain as it is difficult to gauge the amount of work involved at the outset.

  • Project has no predetermined specs and will mostly likely evolve
  • Timetables are flexible and responsive to change
  • Budgets are open-ended with fewer restraints

Testing and Quality Assurance

At Access Technologies, every line of code is tested and retested by independent quality control teams to make sure that your software is functionally secure and will perform under pressure. We write test cases across several platforms — from browsers to mobile devices — making sure that your software will work as envisioned before the product even goes into User Acceptance Testing by the client.