I actually use both, use cases and user stories. The use case is the actual feature, while the use case scenarios are mapped as user stories. You're right that a user story is a placeholder for further conversation between the customer/actor and the team, but eventually, as the conversation goes on, you end up with effectively a use case scenario, described as a sequence of steps.
Same here. I'm currently working on a personal project using an iterative methodology. I started out by creating user stories for each user class in that interacts with my system, then I assigned them a priority. I then elaborated the use cases that I would implement in my first iteration from the user stories I deemed as high priority. I would later work on the use cases that derived from the lower priority user stories in the next iteration.
Et Cetera (English: /ɛtˈsɛtərə/ or (proscribed) English: /ɛkˈsɛtərə/, Latin: [ɛt̪ ˈt͡ʃɛːt̪erä]), abbreviated to etc., etc, et cet., &c. or &c[1][2] is a Latin expression that is used in English to mean "and other similar things", or "and so forth". This drives me nuts that people pronouce it eK cetera haha. Phew, got this out of my system xD
A very clear explanation. I was mixing up between the two but your video helped clarify the confusion!
Very clear and concise like a 'Use Case'😀. Thank you for sharing
The best explanation ever. I still have no fucking idea why I being an engineer must learn this shit.
Glad it was helpful :D
Did u learn?
Thank you great explenation very helpfull
Amazing I love it!
I actually use both, use cases and user stories. The use case is the actual feature, while the use case scenarios are mapped as user stories. You're right that a user story is a placeholder for further conversation between the customer/actor and the team, but eventually, as the conversation goes on, you end up with effectively a use case scenario, described as a sequence of steps.
Same here. I'm currently working on a personal project using an iterative methodology. I started out by creating user stories for each user class in that interacts with my system, then I assigned them a priority. I then elaborated the use cases that I would implement in my first iteration from the user stories I deemed as high priority. I would later work on the use cases that derived from the lower priority user stories in the next iteration.
that was awesome thank you
it helped a LOT 👍
Glad it helped!
The best. Thanks so much..
Thank you so much
nice, detailed video
Cool explained, thanks :)
Thank you
Thanks very helpful
Very helpful. Thank you for the information.
Glad it was helpful!
Good information 🙌🏻
Great piece
Thank you :)
This video is amazing. Thanks a lot!!
Glad you liked it!
I do work in scrum environment and deals with user story.
Nice!
thanks!
No problem!
Et Cetera (English: /ɛtˈsɛtərə/ or (proscribed) English: /ɛkˈsɛtərə/, Latin: [ɛt̪ ˈt͡ʃɛːt̪erä]), abbreviated to etc., etc, et cet., &c. or &c[1][2] is a Latin expression that is used in English to mean "and other similar things", or "and so forth".
This drives me nuts that people pronouce it eK cetera haha.
Phew, got this out of my system xD
❤
Cogent