Scrum Updated SAFe-SASM Exam Questions and Answers by kaja

Relentless Improvement:This principle is a cornerstone of Agile and SAFe. It encourages teams to continuously seek ways to improve their processes, quality, and performance.

Scrum Master Role:The Scrum Master supports the team by fostering a culture of continuous improvement. This involves facilitating retrospectives, encouraging experimentation, and helping the team reflect on their practices and outcomes.

Taking Responsibility:By promoting relentless improvement, the Scrum Master helps the team take ownership of their actions and outcomes, driving self-management and accountability.

SAFe Scrum Master References:

SAFe emphasizes the role of the Scrum Master in supporting continuous improvement initiatives and helping teams develop a mindset of ongoing learning and development.

Continuous Integration (CI) is a practice where code changes are automatically built, tested, and merged into a shared repository multiple times a day. The main purpose of CI is to ensure that the codebase is always in a state that could be potentially deployable. This means that any integration issues are identified and addressed as soon as possible, reducing the chances of bugs slipping into production.

Frequent Integration:Developers frequently integrate their code changes into the main repository, often several times a day.

Automated Builds:Each integration is verified by an automated build to detect integration errors as quickly as possible.

Automated Testing:Along with building, automated tests are run to ensure new changes do not break existing functionality.

Feedback Loop:Quick feedback is provided to the development team, allowing them to fix issues promptly.

By maintaining a potentially deployable codebase, teams can deliver high-quality software more rapidly and with greater confidence.

SAFe Scrum Master References:

SAFe Advanced Scrum Master Training Material, Chapter on Continuous Integration​​.

Phase-gate milestones are traditional project management mechanisms that mark the end of one phase and the beginning of another. One major problem with phase-gate milestones is that they assume a point solution exists and can be built correctly the first time. This assumption does not account for the iterative nature of Agile methodologies, where solutions are developed incrementally and iteratively, with feedback loops and continuous improvement. Assuming a point solution can be finalized early often leads to rigidity, lack of adaptability, and higher risks of delivering a product that does not meet the actual needs or expectations.

Organizing teams around Features can significantly reduce dependencies between teams. When teams are aligned to deliver specific features, they have more autonomy and can work more independently, without needing to wait for other teams to complete their parts. This alignment minimizes coordination and dependency management overhead, enabling faster and more efficient delivery. It also allows teams to focus on delivering end-to-end functionality, which enhances the quality and coherence of the product.

SAFe Scrum Master References

SAFe 5.0 framework: principles of organizing teams around features to reduce dependencies

SAFe Agile Teams: benefits of feature-based team organization