We are often contacted by customers with very rough, technical requirements lists for software projects. In cases like this, the first project step for //SEIBERT/MEDIA is to turn the customer’s requirements list into a product backlog that highlights how the customer benefits from the requirements. This is not a trivial task and requires time and resources. But why should the customer pay for this preparation work that has nothing to do with actually completing the project?
Why we transfer requirements lists into a backlog with user stories
