One of the key benefits of the using Scrum is that it allows the team to quickly identify defects and obstacles. Now that the team has made these known, the team has the ability to remove and fix these defects. What is the value of identifying problems in the product when nothing is done to repair them? The team will become much faster if it can improve the quality on its own by removing known defects and making the software better. Then the team will be able to take on more audacious goals instead of being weighed down by quality problems. Moving known defects to the top of the Product Backlog places quality work as a central goal for the team to achieve which directly improves the product, makes customers and users of the software much happier and invigorates the team to continue to become more effective. Placing known defects away from the top of the Product Backlog causes morale challenges, acceptance by the team of poor quality work and creates an atmosphere of apathy. These are likely to cause a failure by the Scrum Team to deliver on its goals.