Usage Based

The usage-based model offers a flexible and adaptable approach to engaging QA cyber services. In this model, the QA Cyber team is compensated based on the time and effort invested in delivering project functionality.

How does it work

This method is typically used in Day-0 and Day-1 service offerings due to its ease of use and ability to accommodate changes.

However, it's important to note that actual costs may differ from the initial plan. Payments are typically made on a monthly basis or based on milestones, reflecting the completion of work.s

Define Requirements

Tasks, deliverables or user stories are defined.

Divide and Conquer

Work is divided into sprints or milestones, prioritised based on dependencies and time frames.

Delivery

At the end of each sprint, there are demo, retrospective, and sprint planning meetings or milestone presentations.

Invoicing

Payments are based on the time spent working on the project, either after each sprint or milestone or monthly, depending on the terms and length of engagement.

When should the time and materials model be used?

For projects with an unclear scope, where additional expertise is needed to determine the best approach.
When adaptability to changing needs and workloads is crucial for your organisation.
When working with tight deadlines and desiring greater transparency and control over your project or outcome.
For complex projects that require multiple sprints to be delivered.
When the focus is on the work that needs to be done to ensure success, rather than adhering strictly to estimates or initial project specifications.