Becoming a high-performing, distributed Agile team is possible. Strong technical and communication skills blended with a sophisticated, Agile mindset enables predictable, steady, exemplary technical performance. A strong engineering culture is the heart of an Agile team, and the world is filled with talented, motivated people. An exceptional software development experience is possible when distributed Agile teams are actively engaged and managed using these best practices.

Project Roadmap

The development team works with you to develop a broad product roadmap, identifying the initial priorities and order of development. From this, the team defines the base architecture for the project (platforms, technology, services, integrations, etc.). We collaborate with you to define the life cycle methodology. Our most common life cycle processes are Scrum and Kanban.

Scrum Sprints

In Scrum, the project will be broken down into a series of sprints, usually two-week increments. The result of every sprint is a potentially deliverable product increment.

A planning meeting precedes each sprint, jointly with you, the client. Tasks for the sprint (taken from the Product Backlog) are identified, and an estimated commitment for the sprint goal is made (the Sprint Backlog). Clients are consulted on requirements interpretation and the preferred order of activities. Generally, highest value and highest technical risk items will be prioritized first.

Each day during the sprint, a brief meeting — the Daily Standup — is conducted. This meeting is limited to 15 minutes and sets the context for the work that will be completed each day. Client participation is welcome but not required.

When each user story is complete and passes unit testing, it is tested by QA. Our seven-component QA process ensures a high-quality product. Where applicable, we automate these tests for repeatability.

  • User Story review to confirm acceptance criteria is defined
  • Test plan development
  • Test case development
  • Developer unit testing
  • Functional testing
  • Code review, memory leak testing and application hardening
  • Product owner acceptance testing
  • Regression testing

Each user story is tested as it flows through the development process: developer unit testing, functional testing and acceptance testing.

When each story is completed, it is submitted to the product owner for acceptance. As the stories are accepted, they are available to review and approve. Bugs found in the sprint will be fixed immediately to preserve quality of the application at all times.

The Sprint Cycle is repeated until all requirements are completed. At that point, a final sprint is reserved for final hardening tests and bug cleanup.


Get a Free Consultation

Talk to a GAP Sales Engineer Today.

GAP offers far more than software development or QA services. We offer the collective wisdom gained from decades of building, growing and running successful businesses. We collaborate with customers to accelerate growth. We provide software solutions to meet business objectives. We operate with transparency and tenacity to deliver an exceptional experience as a continuous software delivery partner.

Contact Us

Once we got the right people on the project, they were excellent and have been on the project now for several years.

The Education Advisory Board, Distinguished Software Engineer, Architect and Manager

Geoff Howe

The Education Advisory Board, Distinguished Software Engineer, Architect and Manager