Open Luxa23 opened 2 years ago
Hi @Luxa23 !
Looks good so far for your first user story. I still have some questions and hope resolving them helps you ;)
When you say component you mean an actual component? Or are you talking about input fields or a button for example? This may sound a little bit petty but makes a difference in the work load and your data structure.
If you do mean components maybe you should consider to break down this user story into smaller pieces. For example to write a single user story for (bigger) components. Especially when it comes to building a form this is in general a kind of bigger deal.
Also it helps to think about what happens on the page when it is used. For example would it be an acceptance criteria, if the text which is typed in appears as item in the list above? If so, feel free to add it ;)
To be honest. Especially in the beginning writing user stories sucks. But I am sure it will help you structure your project and your work flow. At least for me it worked out ;)
One last tip: In my experience it is good to have small and exact user stories. In general this also breaks down the complexity and makes it much easier to work with.
Hope this helps. In case you have any questions, please let me know ;)
hi @raimartontsch,
thanks a lot for reviewing and all the advice!!
Indeed, I meant components but they currently only consist of the mentioned pieces:
"RecipeListEntry" --> text "Button" --> button with two states "RecipeForm" --> one input field for the recipe title
Later on, I would like to add more complex stuff to them. E.g. an image to the "RecipeListEntry" or more input fields to the form.
value description / statement
As a user I want to save a list of recipes so that I don't forget them.
Description
Acceptance criteria
#
Tasks
Complexity
large