Especially when joining projects for a second release with already existing functional design specifications (FDS), it may well be that user stories are not what they should be. With much room for interpretation they might not be clear, easy to understand or even complete. The impact is an additional (unexpected) effort with all further consequences and discussions between the customer and the contractor about what has and what hasn’t been offered. But why is it like that? If you have ever asked yourself one of the following questions: “What is a user story?”, “How can I write one?” and “Where can I keep all the conditions to lay the foundation for a successful project?” – well, this blog post is for you.