What are user stories used for in Scrum?

User stories are a fundamental component of the Agile framework, particularly in Scrum, serving to define product functionality from the end-user perspective. They allow teams to capture requirements in a way that emphasizes the value provided to users, focusing on the 'who', 'what', and 'why'. This user-centric approach ensures that development efforts align with user needs and expectations, fostering collaboration and communication within the team and with stakeholders.

By writing user stories, the Scrum team can prioritize features based on user value and ensure that the development process is guided by actual user requirements rather than purely technical specifications. This makes it easier for the team to adapt to changes, refine their understanding of user needs, and deliver a product that genuinely resonates with its intended audience.

While the other options may serve important roles in project management, they do not align with the core purpose of user stories in Scrum. Documenting project budgets involves financial planning and tracking costs, which is unrelated to user needs. Tracking team performance metrics pertains to measuring productivity and efficiency rather than defining product features. Creating detailed technical specifications focuses on implementation details, which can overlook the broader user experience that user stories prioritize.