Historic-preservation reviewers mock developers in Slack after every pull request. Throughput looks fine this week. What should the SM/TC address first?
Select an answer to reveal the explanation.
Short Explanation
Mocking a preservation pull request is not a code review—it is throwing stones at the scaffold. Tickets can still move while people stop speaking up. Respect is a core value; without it the team is just temporarily fast.
Full Explanation
Respect for People is a SAFe Core Value and a required high-performing-team behavior. Contempt in Slack destroys psychological safety even when short-term throughput looks acceptable, so learning and quality will degrade. Ignoring the culture, rewarding mockery, or hiding critique behind anonymous forms all leave disrespect in place. The SM/TC should stop the contempt, reset review norms, and reconnect critique to the work—not to humiliation of historic-preservation teammates.