Jira.

Where Jira fits on a long engagement.

The practical point for an outsourced arrangement is that work happens in your Jira, not in a parallel system. One backlog, one set of statuses and one place where progress is visible — a provider running its own tracker and reporting summaries is a warning sign rather than a convenience.

Defect quality is where a QA specialist shows up in Jira most visibly. A ticket with reproduction steps, environment, expected and actual behaviour is fixed once; a ticket saying the page is broken generates three messages before anyone can begin.

What an assigned team does with Jira.

Working in the client's tracker rather than a parallel one is a structural commitment, not a courtesy. It means progress is visible without a status report, and it removes the gap where a provider's summary and reality can diverge for a fortnight.

What makes it work day to day is a service delivery manager holding the board rather than the client chasing it — see how the delivery service works for where that responsibility actually sits.

What we use Jira for.

• One backlog everyone can see Assigned specialists working your board, with progress visible without asking for a report.
• Defects a developer can act on Reproduction steps and environment detail included as standard rather than requested.
• Workflow that reflects reality Statuses matching how the team actually works, so the board is trusted rather than worked around.

How Jira capacity is assigned.

Assumed on every assignment. Specialists work in your tools; see how the delivery service works for what that means in practice. What that figure covers is set out in how the monthly fee is built.