# Best Practices Evidenced for Software Development Based on DevOps and Scrum: A Literature Review
## 3 Results
### What Practices Are Common for Both Scrum and DevOps?  
Integrating Scrum and DevOps necessitates a holistic approach that leverages the practices common to both frameworks. Based on the literature review, the three practices that appear common to both frameworks are actively involved stakeholders, early and continuous feedback, and transparent communication channels, with each element contributing uniquely to the success and streamlining of the joint implementation according to the authors of [119; 120; 121].  
Table 10 presents the following common practices proposed by Scrum and DevOps for the software development process according  
Additionally, early and continuous feedback underscores the importance of providing timely and ongoing feedback throughout the project lifecycle. This practice ensures that adjustments can be made promptly, reducing risks and enhancing the quality of deliverables.  
The literature review results suggest that, in a Scrum and DevOps context, early feedback loops (e.g., from automated testing, continuous integration, and direct stakeholder involvement) are not merely about identifying defects; they represent a mechanism for ensuring that the software being built aligns with the actual requirements of the business and the end-users.  
Frequent integration and testing, which are hallmarks of DevOps, provide rapid insights into the impact of code changes. This allows developers to catch integration issues and performance bottlenecks before they escalate into major problems.  
Furthermore, incorporating feedback from stakeholders throughout the development process, which is a key principle of Scrum, ensures that the software meets their evolving requirements and expectations. This proactive approach minimizes the risk of producing the wrong product, reducing costly rework and ensuring that the final project result delivers maximum value. It allows stakeholders to play a part in project delivery. For this reason, integrating stakeholder feedback into each iteration and demonstrating working software frequently promotes transparency, alignment, and, ultimately, greater project success.  
Equally important, in both frameworks, namely Scrum and DevOps, transparent communication channels are not merely about relaying information. Rather, this practice fosters a shared understanding of project goals, progress, and challenges among all team members and stakeholders. Transparent communication is crucial because it makes stakeholders and development teams more aligned and closer to each other. Ultimately, transparent communication fosters trust and collaboration within the team, leading to faster problem-solving, improved decision-making, and a greater sense of shared ownership for the project's success. Moreover, transparent communication creates a supportive environment for continuous improvement through an open discussion of successes and failures, where the team can identify areas for improvement and implement changes to optimize processes.  
Additionally, some relevant findings to highlight are discussed in the following sections.