Agile Implementation Issues: Your Questions Answered

Agile transformations bring both opportunities and challenges. In our recent webinar, “Challenges and Successes in Agile Implementation,” participants asked a wide range of questions about how to make Agile work in practice. Afterwards, we spoke further with Greg Burns and Ron Ben Yosef from BlackLine to address some of the most pressing topics. Their experience offers practical guidance for teams looking to improve delivery speed while protecting software quality.

Agile Implementation Challenges: Common Issues and Expert Solutions

The questions we received reflected common pain points: aligning stakeholders, managing quality at scale, integrating QA earlier in the process, and making metrics meaningful. Greg and Ron’s answers underscored a core truth about Agile — the methodology only works if it is adapted to the organisation’s needs and rigorously supported by everyone involved.

The Importance of Collaborative Reviews

One question stood out for its focus on daily collaboration: How important is it to have a developer, business analyst, product owner, and tester review the solution for a user story right at the developer’s workstation?

Greg and Ron agree that this practice is crucial. Bringing these perspectives together in real time ensures that the intended solution is validated before it moves further along the process. Issues can be caught and corrected immediately.

When feedback is instant, there are fewer misunderstandings, less rework, and a shorter path to production. This setup accelerates delivery by reducing delays, improves communication by resolving questions face to face, and strengthens quality by incorporating all viewpoints before a feature is considered complete.

The Evolving Role of QA and Test Managers in Agile

Another frequently asked question was whether a QA or Test Manager still has a role in Agile, given that QA engineers and testers are embedded in sprint work.

Greg and Ron’s answer is clear: the role remains important, particularly as an organisation grows. In small teams, quality management often happens within the team itself. At scale, someone must ensure consistency across teams, set testing standards, manage resources, and oversee recruitment.

At XBOSoft, we support this through a matrix organisation. Each Agile team has a manager, and functional “domain leads” oversee areas such as QA, backend, and frontend. The QA domain lead, in particular, works across teams to ensure that quality standards remain consistent and aligned with business objectives.

Strategic oversight like this provides process standardisation, balances workloads, and safeguards quality as delivery scales.

Addressing Common Agile Implementation Challenges

While collaborative reviews and QA leadership were two of the most common questions, other topics from the webinar are equally significant. We will cover them in future posts, including:

• Developer-to-tester ratios in short sprints, and how to ensure testing keeps pace with development.
• The role of clear acceptance criteria in user stories, and how they improve planning and prevent scope drift.

Each of these issues has a direct impact on Agile team performance and product quality.

Integrating Agile Metrics for Continuous Improvement

Agile success is not only about delivering quickly — it is about delivering better over time. To improve, teams need to measure their progress in a way that reflects both productivity and quality.

Greg and Ron highlight key metrics such as defect patterns, customer support volumes, and team velocity. Tracking how many defects are deferred or reopened helps assess process quality. Monitoring support tickets against related defects reveals how well the product performs in real-world use. Reviewing velocity trends shows whether the team is increasing output without sacrificing quality.

At XBOSoft, we encourage teams to balance these measures. Data without context does little; its value comes from regular review, discussion in retrospectives, and turning insights into concrete changes.

Best Practices for Overcoming Agile Implementation Issues

From Greg and Ron’s discussion, several consistent practices emerge:

• Collaborative reviews and real-time feedback. Encourage developers, analysts, product owners, and testers to work closely together, ideally in the same physical or virtual space. This keeps feedback immediate and actionable.
• Strategic oversight for scaling teams. As team numbers grow, introduce a matrix structure with domain leads to maintain consistent quality and guide improvement.
• Clarity in requirements. Make robust acceptance criteria part of every story to reduce ambiguity and rework.
• Metrics that matter. Set clear measurement goals and align them with business objectives. Review and adapt them regularly as projects evolve.

Real-World Impact: Turning Metrics into Success

Greg and Ron shared an example of a team struggling with rising defect rates and unclear communication. By introducing workstation-level cross-functional reviews and adding a QA oversight role, the team reduced production defects, improved customer satisfaction, and increased sprint velocity.

In another case, a team that implemented continuous code reviews and reduced hand-offs saw a 20% increase in velocity and a significant drop in customer support calls. These outcomes show that targeted process changes, backed by meaningful metrics, deliver tangible results.