The cost of a reject can be substantial, with an average story or bug ticket taking around three hours to resolve after being rejected by QA, including additional time for revisiting steps and re-checking requirements. Most teams lack visibility into the impact of rejects on their Scrum team's capacity, but tracking these events can help identify areas where improvements are needed. To mitigate rejects, teams can improve communication between developers, QA, and designers/product/business owners, use Test Early and Often techniques like TDD/BDD, automate deployment processes, and strive for efficiency in tracking story and bug rejects. By implementing these strategies, teams can reduce the time spent on resolves and prevent rejects from becoming a recurring issue.