What should be done if performance requirements aren't clear before starting development?

When performance requirements are not clear before development begins, it is most effective to clarify them later in the process. This approach acknowledges that in agile development environments, complete and final specifications may not be available at the outset. Scrum embraces change and encourages teams to refine their understanding of requirements iteratively.

By deferring clarification until later, teams can leverage insights gained during initial development activities, such as user feedback or changes in business context. This flexibility allows teams to adapt to evolving requirements and ensure that they meet the performance needs as they become clearer over time. It also aligns with the agile principle of valuing working software, which suggests that progress can be made even in the face of uncertain requirements.

Ultimately, the iterative nature of Scrum means that requirements, including performance needs, can evolve based on ongoing testing, stakeholder input, and learning through the development lifecycle. By choosing to clarify these requirements later, the team positions themselves to build a product that better meets the users’ needs and performance expectations.