What is the correct approach if a Product Owner hasn't attended Sprint Retrospectives due to Developers' fears of negativity?

The recommended approach in this scenario is to facilitate a discussion that explores the Developers' fears regarding the Product Owner's presence during the Sprint Retrospectives. This choice is effective because it prioritizes creating an environment of psychological safety, which is essential for open communication and trust within the team. By addressing the concerns directly, the Scrum Master can foster an atmosphere where Developers feel comfortable sharing their thoughts, enabling a thorough investigation of the underlying issues causing the apprehension.

Moreover, involving the Product Owner in the discussions can lead to greater transparency and collaboration, ultimately enhancing the effectiveness of the retrospective. It allows the team to collaboratively determine how to proceed in a way that respects everyone's feelings while promoting a culture of continuous improvement.

Ensuring that all voices are heard while allowing for the Product Owner's feedback can help bridge any gaps in understanding or address any miscommunications that may have occurred. This choice aligns with Scrum's principles, emphasizing teamwork and the importance of transparency in maintaining a healthy team dynamic.