What can go wrong without requirements ?

1. Miscommunication and misunderstandings: Without clear and well-defined requirements, there is a risk of miscommunication and misunderstandings among stakeholders. This can lead to confusion and delays in the development process and ultimately result in a product that does not meet the needs of the customer.
2. Lack of alignment: Without requirements, it can be difficult for teams to align on the goals and objectives of the project. This can lead to different interpretations of what the final product should look like and ultimately result in a product that does not meet the needs of the customer.
3. Lack of traceability: Without requirements, it can be difficult to trace the progress of the project and identify any issues or areas for improvement. This can make it difficult to identify defects and make necessary changes, leading to a final product that is of poor quality.
4. Lack of flexibility: Without requirements, it can be difficult to adapt to changes in requirements or technology. This can make it difficult to evolve the product over time and ultimately result in a product that does not meet the needs of the customer.
5. Increased costs: Without requirements, it can be difficult to manage and control the cost of the project. This can lead to cost overruns and ultimately result in a product that is more expensive than it needs to be. Additionally, lack of requirements can lead to rework and wasted effort.

Overall, not having well-defined requirements can lead to a wide range of issues, including miscommunication and misunderstandings, lack of alignment, lack of traceability, lack of flexibility, and increased costs. These issues can ultimately lead to a final product that does not meet the needs of the customer and is of poor quality.

**