Organization of Reporting in Agile Processes: Requirements, Solutions and Challenges

2025 Vol. 2 No. 3 https://www.eujini.org.pl 11 ISSN 3071-9658 https://www.eujini.org.pl Organization of Reporting in Agile Processes: Requirements, Solutions and Challenges Kateryna Horshchar 1 * 1 National University of Water and Environmental Engineering, Rivne (Ukraine). QA Automation Engineer, SchoolDay Inc. *Corresponding Author, e-mail: [email protected] ARTICLE INFO ABSTRACT Research Article Received: 14 July 2025 Revised: 1 September 2025 Accepted: 21 September 2025 Published online: 15 October 2025 Copyright © 2025 by authors This is an open access journal and all published articles are licensed under a Creative Commons Attribution— NonCommercial 4.0 International (CC BY-NC 4.0) DOI: 10.5281/ zenodo.18023318 The article examines the features of reporting organizations in Agile processes with a focus on software quality assurance (QA). Reporting requirements, modern tool solutions and methodological approaches that promote transparency, effective communication and product quality maintenance in a dynamic Agile environment are analyzed. Key categories of stakeholders are considered – project managers, developers, business representatives and QA teams – and their information needs that require adaptation of formats and periodicity of reports. An author’s model of reporting organization is proposed, which integrates automation through CI/CD pipelines, adaptability of report formats to the needs of different audiences and transparency of processes through the use of monitoring systems such as Prometheus and Grafana. The strategic importance of differentiated reporting is justified in terms of the rapid implementation of sound decisions, helping to increase trust in the quality control team and developing a quality culture in the organization. The tools mentioned in this part with special attention are Allure, TestRail, Zephyr, Jenkins, GitHub Actions and GitLab CI, which help automate, visualize data, and predict quality risks using analytics and artificial intelligence. The study focuses on a flexible reporting system that takes into account the specifics of the project, its scale, and stakeholder requirements, as well as integrating with new technologies for processing large amounts of information. The proposed model creates a single reporting ecosystem that helps synchronize the efforts of all project participants, increases the efficiency of Agile processes, and supports the achievement of business goals. Challenges such as excessive bureaucracy or insufficient digital communication in distributed teams are overcome through a structured approach to identifying needs and using automated tools. The study results provide practical recommendations for implementing effective reporting that promotes transparency, efficiency, and quality in Agile development. KEYWORDS agile reporting, quality assurance (QA), CI/CD integration, stakeholders, test automation. Kateryna Horshchar , 2(3) https://www.eujini.org.pl 12 Introduction gile is becoming a modern software development methodology due to its flexible development methodology. These strategies include adaptation to change, iterative product development and teamwork. In such a dynamic environment, quality assurance (QA) and reporting on its results acquire special importance. Unlike the waterfall development model, where reporting is a typical formulated activity that occurs at the end of the cycle, in Agile processes it should be flexible, informative and implemented on an ongoing basis. The issue of effective reporting organization is one of the main issues for many teams, since an ineffective reporting system can contribute to a decrease in the transparency of processes, the quality of communication between stakeholders, etc., which, in turn, will also lead to a decrease in the overall quality of the final product. At the same time, excessive bureaucratization of reporting contradicts the principles of Agile, which involve reducing documentation to obtain a working product and quickly responding to any changes. Reporting in the context of QA is not only a tool for documenting test results, but also an important communication mechanism that ensures transparency of processes for all project participants. It acts as a connecting link between the technical team and other stakeholders, facilitating understanding of the current state of development and product quality. Traditional reporting approaches, characteristic of the waterfall model, often prove unsuitable for Agile environments due to excessive detail, which includes redundant information that is irrelevant for rapid iterations, and lack of efficiency, since formal reports prepared with a delay do not allow for timely response to changes. Different categories of stakeholders, such as developers, managers or customers, have different information needs and levels of technical competence, which requires adaptation of the format and content of reports to ensure effective communication. It is necessary to find a balance between the detail of technical reports for the development team and the generalization of information for management to ensure effective decision-making at all levels of the organization. In the context of rapid change and iterative development, reporting becomes a tool that helps teams adapt to changing requirements and priorities, providing data for making informed decisions about further development steps, resource allocation, and prioritization. Of particular importance is the ability of reporting to quickly reflect changes in product quality and process efficiency, which allows for timely response to emerging problems. Modern reporting automation tools integrated with continuous integration systems (Continuous Integration – CI) and Continuous Delivery (Continuous Delivery (CD) tools play a key role in supporting the fast pace of Agile processes by automatically collecting and visualizing data about product quality. It is important to ensure not only the technical integration of different tools, but also the meaningful consistency of data coming from different sources. Universal reporting solutions usually do not take into account the specifics of specific projects, which can lead to the formalization of reporting and the filtering of its practical value. Therefore, it is necessary to develop a flexible reporting system that can be adapted to a specific project, group of people and organization, although it is necessary to ensure compliance with the principles and requirements for quality. The growing complexity of software systems and the huge amount of data generated during their development and testing require new methods of analysis and presentation of information. The traditional way of analyzing and visualizing data is losing its relevance; therefore, to increase the informativeness and usefulness of reports, it is necessary to implement modern technologies such as data analysis, machine learning and artificial intelligence. In turn, these technologies help to process large amounts of information and identify certain hidden connections and trends, creating more accurate and useful reports. Literature Review uality reporting in a software quality assurance (QA) environment is a fundamental element in building trust between all project participants. This trust is based on transparency, reliability, and timeliness of the information provided. As noted by Petrukha et al. (2024), it is communication and transparency of processes that are critical factors in the success of implementing innovative approaches in IT projects using agile methodologies. A Q Kateryna Horshchar , 2(3) https://www.eujini.org.pl 13 The presence of high-quality reporting allows all stakeholders in the process to share a common view of the current state of the project, the presence of problems and risks. This prevents any transparency in the quality assurance process and provides the opportunity to make informed decisions based on objective data. Dugbartey & Kehinde (2025) write that the balance between development speed, collaboration and stakeholder involvement should be recognized as a key success factor in agile projects, where reporting is an important aspect of communication. That is why, when the reporting of the quality assurance team is high-quality, it performs a number of important tasks. First, it provides an objective picture of the state of product quality at the current moment. Second, it makes it possible to track the dynamics of changes and progress. Third, it allows you to identify problem areas and make timely decisions to eliminate them. In the context of Agile methodology, where transparency and collaboration are key principles, quality reporting plays a central role, especially in distributed teams that are becoming increasingly common in today’s IT environment. Simas & Chaves (2025) in their study emphasize that effective reporting is the basis of digital communication in agile projects. It provides transparency, coordination of work and creates a single information space, which is especially important in conditions of geographical dispersion of the team. This approach helps to build trust between participants, which is critical for the iterative development process. Problem Statement his article aims to systematize methods for organizing work reporting in the Agile spectrum against the background of quality assurance, requirements for such reporting and modern technological solutions to limit the corresponding challenges, formulate recommendations on the periphery of a specific issue. Special emphasis is placed on the conceptualization of a reporting model that simultaneously integrates automation, adaptability and transparency to form a single reporting ecosystem that ensures effective communication and promotes informed decision-making by all project stakeholders. Results and Discussion uality reporting from the QA team has a cascading effect on the entire organization, supporting agile values. First, well-structured data allows developers to see specific problems, which promotes close cooperation with the QA team. Second, reliable information allows management to make strategic decisions based on objective facts, not intuition. Third, it contributes to the formation of a quality culture, where each project participant is clearly aware of their role and responsibility, which is consistent with the principle of shared responsibility in the agile methodology. One of the challenges for distributed Agile teams is insufficient digital communication. Quality reporting acts as a tool to overcome this problem by creating a common language for technical specialists and management. It provides a single information space where stakeholders can track progress, identify risks and agree on actions, which contributes to effective iteration management and rapid response to change. Ensuring transparency of QA processes in modern Agile teams is impossible without the use of specialized tools that allow you to automate data collection, processing and visualization. To illustrate the variety of reporting tools, a comparative table 1 of their characteristics is provided. As can be seen from Table 1, each tool has its strengths and weaknesses. Choosing the optimal set of tools for organizing reporting depends on the specific needs of the project and team, while it is important to ensure the integration of the selected tools to form a single reporting ecosystem. For example, TestRail and ReportPortal are highly adaptable to different audiences, while Allure is optimal for technical teams due to its detailed visualization of test results. Special attention should be paid to tools such as Allure, dashboards Jira, CI documents and monitoring systems. Allure Report is a powerful tool for generating reports on the results of automated testing. Its advantage lies in the clarity of information presentation and the ability to analyze in detail the reasons for failed tests. As noted by Barua, C., Kabir, JUZ, Alam, KR, Nabil, AR, & Duman, S. (Barua et al., T Q Kateryna Horshchar , 2(3) https://www.eujini.org.pl 14 2025), the integration of reporting tools with artificial intelligence systems allows not only to display test results, but also to predict potential risks and propose solutions to mitigate them. Table 1. Comparison of Reporting Tools in Test Management Systems Tool Integration with Agile processes Adaptability to different audiences Reporting automation Data visualization CI/CD support Jira High Medium Medium Medium High TestRail High High High High Medium Zephyr High Medium High High High Allure Medium Low High High High Extent Low Medium High High Medium ReportPortal Medium High High High High Source: systematized by the author. Jira dashboards are also commonly used as a tool for visualizing testing progress and tracking defects in most Agile teams. They offer possibilities point different ways to view data for different interested parties. Research Tomaselli et al. (2025) shows that efficiency processes software quality, especially from the point of view of productivity and effectiveness, conducted tests when it comes to integration tools management requirements and tracking systems errors, significantly improves. CI documents (Continuous Integration), which are automatically created during code build and testing, provide timely information about the project status. This is especially important in DevOps scenarios, where the speed of feedback is crucial for success. Pavlenko et al. (2024) argue that automation of the reporting process helps to increase the efficiency of training and production processes. Monitoring tools such as Prometheus and Grafana can be used to monitor the performance and behavior of systems as they occur. This allows for the detection of problems that would otherwise harm end users. According to Afolalu & Tsoeu (2025), monitoring is becoming an integral component of optimizing network processes and ensuring quality of service. In a flexible environment, successful communication requires moving report forms to meet the needs of different users. The format of the report for the technical team is significantly different from the format intended for management, due to different information needs and levels of technical expertise. For a technical team that includes developers, testers, and DevOps engineers, reports should provide comprehensive technical information that enables rapid problem identification and resolution. In particular, call stacks included in reports allow developers to pinpoint errors in the code, pointing to specific lines and methods where the problem occurred. Detailed logs that include timestamps, log levels (such as ERROR or DEBUG), and execution context help testers reproduce the problem in a controlled environment and identify patterns that may indicate system failures. Environment configurations, such as software versions, server parameters (such as memory or CPU), or environment variables, allow DevOps engineers to assess the impact of external factors, such as incorrect database settings or network timeouts. The steps for reproducing the errors, clearly described in the report, provide clarity in the testing process, allowing teams to quickly test hypotheses and confirm fixes. As Zeng et al. (2025) emphasize, such reports should be as detailed and structured as possible to facilitate analysis and accelerate technical decision-making. Automating the generation of these reports using CI/CD tools such as Jenkins, GitLab CI, or GitHub Actions not only ensures consistency in format but also reduces the likelihood of missing critical data, such as performance metrics or test results. As a result, well-structured reports become the basis for effective collaboration between teams, reducing diagnostic time and increasing overall system reliability. For management, including project managers, product owners, and business stakeholders, reports should be high-level, focused on business metrics, project progress against plan, key risks, and their potential impact on achieving goals. Such reports should be concise, visually clear, and as Kateryna Horshchar , 2(3) https://www.eujini.org.pl 15 accessible as possible, avoiding technical jargon to ensure that information is quickly understood even by those without technical expertise. For example, business metrics such as time to key functions, user satisfaction, or product revenue should be presented in graphs or charts that clearly show trends and anomalies, such as declining productivity or increasing complaints. Project progress should be compared to planned milestones, highlighting deviations from schedule or budget so that managers can quickly adjust plans. Key risks, such as development delays or system instability, should be accompanied by an assessment of their impact on business objectives, such as customer loss or additional costs, and suggestions for minimizing them. Dugbartey & Kehinde (2025) point out, effective stakeholder engagement in Agile projects largely depends on the quality and format of communication, where clarity and relevance of information contribute to better understanding and faster decision-making. To this end, reports can include dashboards with KPIs, risk heat maps, or executive summaries (summaries), which provide an instant overview of the project status. This approach not only facilitates communication with business stakeholders but also strengthens trust in the team by demonstrating transparency and a focus on results. Below is a comparison of key report features for different audiences. Table 2. Comparison of Report Characteristics for Different Audiences in Agile Processes Characteristic Reports for the technical team Reports for management Level of detail High (technical details, code, configurations) Low (summary metrics, trends) Generation frequency High (daily/after each test run) Average (per sprint/iteration) Data format Text log, JSON, XML, detailed graphs Visualizations, dashboards, charts, infographics Focus of attention Technical issues, defects, codebase coverage Business risks, progress, and overall product quality Automation Fully automated Partially automated with elements of analytics Technical terminology Present in full Minimized or explained Source: Author’s own development. Analysis of the data in Table 2 shows that the key difference is not only in the amount of information, but also in the way it is presented and interpreted. The technical team needs data to solve specific problems, while management needs to understand the big picture to make strategic decisions. Effectively implementing reporting in Agile processes requires a series of sequential steps that ensure that the reports meet the needs of all stakeholders, promoting transparency and effective collaboration. The first step involves carefully identifying key stakeholders who will use the reporting information to make decisions and fulfill their responsibilities. These stakeholders typically include project managers, who are responsible for overall project management and need clear data on testing progress, identified issues, task deadlines, and potential risks that could impact the schedule or budget. Developers, in turn, depend on detailed technical information such as call stacks, automated test logs, and defect descriptions to quickly localize and fix problems in the code. Business representatives, including product owners, need high-level reports that reflect product quality, functionality meeting business requirements, and key metrics such as user satisfaction or system stability, in an accessible and understandable format. The QA team, in turn, needs detailed data on test results, including test coverage statistics, error rates, and recommendations for improving test scripts, to optimize quality assurance processes. To ensure the effectiveness of this stage, it is important to consult with all stakeholders to clearly define their needs for the format, frequency, and level of detail of the reports. This approach not only ensures the relevance of the reporting but also creates a basis for further automation and integration of reports into CI/CD processes, which increases the flexibility and adaptability of the Agile team to changes. Once key stakeholders have been identified, it is necessary to clarify their information needs through interviews, surveys and workshops, which will allow us to determine what information is most Kateryna Horshchar , 2(3) https://www.eujini.org.pl 16 important for each stakeholder category. The matrix of information needs of different stakeholder categories demonstrates a differentiated approach to reporting. To demonstrate the information needs of stakeholders, a matrix of their requirements is provided. Table 3 illustrates that different stakeholders have unique needs, which require a differentiated approach to reporting. For example, business representatives focus on compliance with requirements, while developers focus on the technical details of defects. Table 3. Stakeholder Information Needs Matrix Information type Project Manager Developers Business representatives QA team Testing progress ✓ ✓ ✓ ✓ Test coverage ✓ ✓ - ✓ Defect details - ✓ - ✓ Quality metrics ✓ - ✓ ✓ Risks ✓ ✓ ✓ ✓ Testing automation - ✓ - ✓ Regression testing ✓ ✓ - ✓ API Performance - ✓ - ✓ Compliance ✓ - ✓ ✓ Quality trends ✓ - ✓ ✓ Source: Author’s development. Reporting in the context of quality assurance in Agile processes performs not only a technical but also a reputational function. It is a kind of “face of the QA team” to other project participants and stakeholders. The lack of systematic and high-quality reporting creates the impression that the QA team is not working or is working inefficiently, even if in fact this is not the case. Malla (2025) notes that the quality of reporting directly affects the perception of the effectiveness of QA processes and their trust in them by other teams and stakeholders. The author emphasizes that even the best testing work can be underestimated if the results are not documented and communicated properly. The value of reporting as the “face of the QA team” is evident in several key aspects that highlight the team’s contribution to the project’s success and facilitate effective interaction with other participants. First, regular reports provide visibility into the QA team’s work, clearly demonstrating the scope and complexity of tasks performed, such as functional testing, requirements analysis, or test automation. This is especially important because preventive measures, such as early detection of potential problems in requirements or architecture, often remain invisible to developers, managers, or business stakeholders, but are critical to product quality. Second, reports serve to confirm the value of the QA team by clearly demonstrating how detected defects, prevented critical errors, or improved product stability contribute to the overall success of the project, such as reducing user complaints or saving resources on post-release bug fixes. Third, well-prepared reports that include analytical findings, trend visualizations, and specific recommendations for process improvement demonstrate the QA team’s high level of professionalism and expertise, building trust with other project participants. Finally, reports that provide specific data on quality trends, defect types, test coverage rates, or feature stability provide an excellent basis for team or management decisions, such as prioritizing tasks, planning releases, or allocating resources to critical modules. Thus, reporting defines the role of the QA team and provides a means of coordinating activities between all stakeholders, which improves communication and task execution in line with the project’s business goals. Kateryna Horshchar , 2(3) https://www.eujini.org.pl 17 Serrador & Zadeh (2025) note that, thus, in successful Agile projects, communication and reporting are taken seriously and are actually considered a strategic tool that will provide a common basis for understanding the project’s goals as well as the project challenges that affect the team. There is a wide variety of reports used in modern Agile processes, each with its own characteristics and purposes. Here are some key types of reports that provide transparency into quality assurance processes. CI reports generated during the build and test phases of continuous integration systems are important mechanisms for providing rapid feedback to development and testing teams, as well as DevOps teams, helping to quickly track and fix any defects in code quality. The key tools for developing such reports are the combination of capabilities and versatility of processing the results and streamlining the workflow within the team. An example of such a tool is Allure Report, which is flexible and powerful enough to generate comprehensive reports with a graphically rich interface, including graphs, charts, and failure details. According to Barua et al. (2025), Allure’s ability to integrate with any CI/CD system, such as Jenkins or GitLab CI, provides rapid feedback on code quality, allowing teams to immediately respond to regressions or instability in testing. Extent Report, in turn, provides the ability to create interactive and visually appealing reports with customizable design and branding options that meet project requirements, and also provides detailed information about each test, including screenshots, logs, metadata and execution time, which facilitates easier problem diagnosis. ReportPortal, as an analytical platform, is distinguished by its ability to aggregate test results from various sources, such as JUnit, TestNG, or Cucumber, providing centralized storage of test history, trend analysis (for example, an increase in the number of failed tests) and detection of unstable tests that may indicate systemic problems in the code or configuration. Using these tools in CI/CD processes not only increases the transparency of test results but also helps synchronize the efforts of the technical team, allowing you to achieve product stability faster and maintain a high level of quality in dynamic Agile projects. Dashboards with integration into project and test management systems play a key role in providing centralized access to up-to-date information on testing status and product quality, promoting transparency and effective communication between teams. Jira Dashboards, for example, allow you to create customized panels with widgets that display the status of tasks, the number of open and closed defects, sprint progress, or key project metrics such as the percentage of test cases completed, in an understandable graphical format. As Zeng et al. (2025) point out, the integration of reporting systems with project management tools such as Jira creates a single information space that facilitates monitoring and coordination between developers, testers, and managers, allowing for rapid response to changes or problems. TestRail, as a specialized test management system, offers powerful capabilities for creating detailed reports and dashboards that display testing progress, test coverage, defect statistics, and quality trends, such as the increase in the number of failed tests in a particular module. This helps the QA team identify weaknesses in the product and optimize testing processes. Zephyr, in turn, as a plugin for Jira, extends the functionality of test management by providing tools for tracing test case requirements, creating test execution schedules, and detailed quality status reports, which are especially useful for business stakeholders who need a high-level overview. Such integration of dashboards with management systems not only provides centralized access to data but also supports rapid, informed decision-making, increasing the efficiency of Agile processes and contributing to the achievement of project business goals. In addition to standard reports, Agile processes actively use specialized reports that focus on specific aspects of product quality, providing teams and stakeholders with a deep understanding of the development status and opportunities for improvement. Bug type reports analyze defects in detail by category (e.g., UI, API, database), priority (critical, medium, low), system components, or modules, allowing teams to identify problem areas, such as frequent failure of a certain functionality, and recognize patterns, such as repeated errors due to insufficient testing. This contributes to the pinpoint optimization of development and testing processes. Coverage reports, in turn, reflect the level of coverage of the code base by automated tests, including coverage metrics for functions, lines of code, branches, and scripts, which helps to assess how thoroughly the product is tested and whether there are gaps that could lead to undetected defects. As Tomaselli et al. (2025) emphasize, adequate test coverage is a critical factor in ensuring software quality, as it reduces the risk of regressions and Kateryna Horshchar , 2(3) https://www.eujini.org.pl 18 increases product reliability. Risk reports assess potential quality threats, such as key module instability or integration delays, indicating their probability and impact on business objectives, such as customer loss or additional costs. Such reports can include risk heat maps to visually represent priorities and specific recommendations for mitigating them, such as increasing testing resources or reviewing the architecture. Using these specialized reports in CI/CD processes and integrating them with management tools such as Jira or TestRail, enables teams to respond quickly to issues, optimize product quality, and maintain alignment with project goals, facilitating effective collaboration in an Agile environment. As shown in Fig . 1, there are relationships between the various elements of the reporting ecology in Agile QA processes. Software quality is the most important factor, and all reporting tools and processes revolve around it. The interaction between the different types of reports and tools gives all stakeholders a complete picture of the quality of the product. Figure 1. Reporting ecosystem in Agile QA processes Source: author’s development in PlantUML online editor To organize an effective reporting system in Agile QA processes, it is necessary to have a structured process and take into account the needs of all stakeholders. Let’s consider the main stages of this process. The first step in organizing an effective reporting system is to identify key stakeholders who will be the consumers of the information, which allows you to tailor the reports to their specific needs and ensure the relevance of the data for decision-making. As Dugbartey & Kehinde (2025) emphasize, effective stakeholder engagement is one of the key factors for the success of Agile projects, as it promotes transparent communication and alignment between teams and business goals. The main categories of stakeholders are project managers (PMs), who need high-level reports to track sprint progress, assess risks such as delays or budget overruns, and plan resources, such as reallocating QA or developers to critical tasks. Developers, in turn, are interested in detailed technical information, including defect descriptions with full call stacks, logs, automated test results, and code coverage metrics, which allow them to quickly localize and fix problems, such as regressions in a particular module. Business representatives, such as product owners or marketing teams, need clear information about the product’s compliance with business requirements, such as whether the functionality provides the expected value for users, as well as about potential risks, such as instability of key features that could affect the company’s revenue or reputation. In addition, they expect highlevel reports with visualizations, such as dashboards or graphs, that reflect the overall quality of the product and its impact on business goals. This approach to stakeholder identification lays the foundation for creating targeted reporting that not only meets information needs, but also helps synchronize the efforts of all project participants, increasing the effectiveness of Agile processes and trust in the team. Petrukha et al. (2024) note that identifying key stakeholders and understanding their information needs is critical for building an effective project communication system. After identifying key stakeholders, the next critical step is to gain a deep understanding of each group’s information needs to ensure that relevant and targeted reports are created that facilitate effective communication and support Agile processes. Simas & Chaves (2025) recommend conducting structured interviews and workshops with all stakeholder categories to accurately identify their expectations regarding the content, format, and frequency of reports, allowing for tailoring Kateryna Horshchar , 2(3) https://www.eujini.org.pl 19 reporting to the specific needs of the project. For project managers, key metrics include progress metrics such as sprint completion percentage or schedule compliance, defect statistics (e.g., number of critical and medium defects), and risk assessments that could impact the project’s schedule or budget, such as delays due to server instability. Such information, often presented in the form of dashboards or charts in Jira, helps managers effectively plan resources and coordinate the work of teams. Developers prioritize detailed technical information, including defect descriptions with full call stacks, logs, screenshots, automated test results (e.g., TestNG test failure rate), and code quality metrics such as test coverage or code smell count, which allow them to quickly isolate and fix issues. Business people, such as product owners or marketing teams, need high-level reports that clearly demonstrate how product quality impacts business goals, such as whether a feature is driving revenue or user satisfaction, as well as information about risks, such as instability in key features that could lead to customer churn. This data, presented through heat maps or KPIs in reports like Allure or TestRail, helps business stakeholders assess the commercial impact and prioritize improvements. This approach to identifying information needs through structured methods, such as interviews or workshops, ensures the creation of reports that not only meet stakeholder expectations but also contribute to the synchronization of efforts, increasing the transparency and efficiency of Agile projects. Tomaselli et al. (2025) note that regularly collecting feedback on the usefulness and understandability of reports allows for continuous improvement of the reporting system. Determining the optimal reporting frequency is a key aspect of organizing an effective reporting system that ensures timely information to stakeholders and supports the dynamics of the project in an Agile environment. As Malla (2025) emphasizes, the frequency of report generation should be balanced to match the pace of development, the information needs of stakeholders and not create an excessive burden on the team. Daily reports, which are commonly used in Scrum teams, are short overviews containing key information about the status of testing, identified critical defects and blockers that can stop the progress of the sprint, for example, API instability or errors in critical functions. Such reports allow teams to quickly respond to problems, providing transparency of daily operations and maintaining synchronization between developers, testers and managers. The tests performed and the results obtained at the end of each sprint are provided in the form of reports called sprint reports. They contain extensive data on test error rates and types of errors, coverage, and test execution, which allows you to see how the iteration is going and whether there are any systemic issues that can be observed (for example, the same error may appear again in the same module). Release reports, in turn, provide an overall assessment of the quality of the release, including regression analysis, product stability (for example, percentage of failed transactions), compliance with business requirements, and readiness for delivery, which is crucial for making decisions about releasing the product. The best setting for an appropriate frequency depends on the nature of the project, the methodology used (for example, Scrum or Kanban), and the needs of stakeholders, including managers who need higher-level reports or programmers who need detailed data. Automating report generation by integrating reports with CI/CD, such as Jenkins or GitLab CI, and management, such as Jira, increases efficiency and allows team members to focus on working on product quality, rather than the routine reporting process. Serrador & Zadeh (2025) emphasize that establishing a clear reporting frequency and adhering to these deadlines helps increase trust in the QA team and form a quality culture in the organization. The current ecosystem of tools for organizing reporting in Agile QA processes is extremely diverse and constantly evolving. Let’s consider the main categories of such tools and their applications. CI pipelines (Continuous Integration) is the foundation for automating build, testing, and reporting processes, ensuring fast feedback and high product quality in Agile processes. They allow development, testing, and DevOps teams to effectively coordinate efforts, minimizing manual work and the risk of errors. GitHub Actions, integrated with the GitHub platform, offers a flexible service for automating the full development cycle – from build and test to deployment, with the ability to configure workflows via YAML configurations. As Zeng et al. (2025) point out, the integration of CI/CD tools with version control systems such as GitHub significantly increases the efficiency of quality assurance, allowing you to automate test execution, generate reports (for example, via Allure) and quickly detect problems after each commit. Jenkins, as an open automation platform, is distinguished