QMetry organizes test assets into Projects, Releases, Cycles, and a Backlog. The Project is the main container and is the equivalent to your overall Agile Product/Project. Releases are equivalent to a shippable product, or milestone. Cycles are equivalent to a Sprint, increment, or iteration of software. The Backlog is the equivalent of the Backlog used in the Agile process and contains all Test Cases and Requirements that are not associated with a specific Cycle or Release - creation of the Backlog is an automatic process. All four terms (Project, Release, Cycle, and Backlog) can be renamed to match the nomenclature used by the organization.
Organizations that use an Agile development environment usually use the backlog to hold all potential features and move those features to a specific cycle/sprint when they are ready to deliver them. This process is easy to do with the Add to Current Scope button in QMetry. When you add something to the Current Scope you will automatically remove it from the backlog.
Test Cases and requirements can be shared across multiple cycles and releases. Test Suites are groups of Test Cases in a specific order (e.g. Smoke Test, BVT, Functional, or specific new feature or customer tests). Test Suites are part of a specific cycle; however, they can be copied quickly from one cycle to the next. This allows you to grow your Test Suites as the product grows.
Test Suites can also be executed against different Platforms or Configurations. With platforms you can quickly reuse the same Test Suites to record the results against different browser, mobile devices, set top boxes, etc. No need to recreate the Test Cases, or Test Suites. Simply add the platform and go.
Usually an Agile Cycle/Sprint ends with a specific build; however, many development groups will produce multiple builds within a cycle/sprint. These builds may be specific fixes of the previous build (e.g. the last build failed the smoke test and needed to be rebuilt), or in the development group wants to do functional testing throughout the current cycle/sprint. In either scenario QMetry allows QA groups to track test results against a specific build - whether it was the first, second or twentieth. This is done by using QMetry's unique drop feature. At the time of execution the tester can assign a specific drop/build to be tested against. They can make the drop default, or if they are doing testing on branched code they can just apply the drop and gather the results for comparison without changing the default drop. The term "drop" can also be renamed to match the nomenclature used by the organization (e.g. build, version, patch, etc.).
Using drops, combined with cycles, releases, and backlogs allows Agile teams to quickly manage and plan out their requirements and test scenarios with a minimum of overhead.