Open CarstenJahnke opened 1 year ago
Hi Carsten, your value proposition syntactically implies that the user gets some kind of overview and can assign movies etc. to these phases. Is that really what you want to cover in this user story?
As far as I understood your project idea, I assume that it would be a first step to give a predefined version of these phases and use them as some kind of (visual and logical) container to display movies belonging to the corresponding phase.
In both cases your acceptance criteria lack a clear and detailed description of your feature (reads more like a task item). Try to imagine what the user would see on the screen and describe the elements and their UX in detail (e.g. the phases are shown in a scollable list). And there will be definitely more than one acceptance criteria ;)
Concerning your task list at least a movie component is also missing as you are referring sort the movies.
Cheers, Thomas
Apart from a bit of confusion of your Value PropositionValue Proposition stating "So that I can better assign them all to the phases" speaking of the User's perspective and not the developer's perspective, it implies that the user will be assigning something over your WebApp's UI, but I believe you were writing this from the developer's perspective, for which case I would suggest changing the text
from So that I can better assign them all to the phases to So that I can easily identify what phase any movie belongs to 👆 I believe this would be more from the "User" perspective and relevant to your described goal 😊
Value Proposition
As a user I like to see an overview of all movies of the Marvel Cinematic Universe displayed in the order of the phases So that I can easily identify what phase any movie belongs to
Description
Acceptance Criteria
Tasks
Container
componence wich called "phases" (for example "Phase 1", "Phase 2", etc.)