Thanks a lot! Most critical concept and framework explained in a most simple and comprehensive manner. One of the Best videos I came across on this topic on RUclips.
Thanks, buddy!! this is a massive help for me to understand how to write user stories for the API integrations related projects. However, I want to mention that the user stories alone will not help the devops to understand the success criteria. You need to have the user acceptance criteria with lots of scenarios covered.
The intuitive measure of defining user stories into small enough units is from cluster analysis in statistics where clusters are defined based on minimizing in-group variance while maximizing between-groups variance. Is that a valid criterion of how small value-units/user-stories should be? that variance is the complexity factor of a story in this case?
Hi, this is helpful. Thanks for sharing. I have a unique project which consists basically in system migration. The ordering flows are all already implemented and delivered. So from real users perspective, the stories aren't changing. However, the amount of work to change how the stories are realized is quite significant. Let me pick one. "As a TV Customer I want to order PPV". This is already there. But my project changes how this gets fulfilled and charged. Would you consider this a valid story in the project?
Hi Gustavo, the example helps. If I understand what you are saying, the system behind the scenes is changing but the actual functionality the user experiences is not. If this is the case, I think you could re-use the User Story but change the definition of done. Where the DoD states that the systems, data, or environments that the functionality is served from is what needs to be changed. So this means it's still a valid user story for a project. If the functionality is changing perhaps a subtle variant of use case, you could expand the User Story to a GWT - Given When Then format. For example: As a TV Customer I want to order PPV. Given I have arrived at the payment screen, I can add my [insert new fulfillment and charing scenario]. In addition, be practical, if the effort is significant, try to break the user story into several smaller user stories, smaller the better. Since the new effort is significant, that means there are likely more sub-use cases that you can break into smaller users stories that can be more easily delivered in a Sprint. If these use cases are more technical or back end, that is fine too as long as it testable, and traces to the original user need. Hope that helps.
Consider using COSMIC story points, which can be used as a framework for adding items to your backlog. I've created a somewhat fun, and somewhat polished relatively quick introduction: ruclips.net/video/HE6uq-geR7A/видео.html
![Blox Fruits Dragon Rework Update [Full Stream]](http://i.ytimg.com/vi/EqDAp8udhm0/mqdefault.jpg)
Thanks a lot! Most critical concept and framework explained in a most simple and comprehensive manner. One of the Best videos I came across on this topic on RUclips.
Excellent! Crisp demonstration of a Software Product Owner's main responsibilities.
Hi, breaking down user stories to the finest level is one very much needed input to me. Thanks.
Awesome video, the pace and sequence selected to explain is just spot on.
Thanks, buddy!! this is a massive help for me to understand how to write user stories for the API integrations related projects. However, I want to mention that the user stories alone will not help the devops to understand the success criteria. You need to have the user acceptance criteria with lots of scenarios covered.
Nice! Crisp and short.
The intuitive measure of defining user stories into small enough units is from cluster analysis in statistics where clusters are defined based on minimizing in-group variance while maximizing between-groups variance. Is that a valid criterion of how small value-units/user-stories should be? that variance is the complexity factor of a story in this case?
I am trying to understand this in the context of behavior design for social impact. Thanks for a crisp epic with easily digestible value units! :)
Hi, this is helpful. Thanks for sharing.
I have a unique project which consists basically in system migration. The ordering flows are all already implemented and delivered. So from real users perspective, the stories aren't changing. However, the amount of work to change how the stories are realized is quite significant.
Let me pick one. "As a TV Customer I want to order PPV". This is already there. But my project changes how this gets fulfilled and charged.
Would you consider this a valid story in the project?
Hi Gustavo, the example helps. If I understand what you are saying, the system behind the scenes is changing but the actual functionality the user experiences is not. If this is the case, I think you could re-use the User Story but change the definition of done. Where the DoD states that the systems, data, or environments that the functionality is served from is what needs to be changed. So this means it's still a valid user story for a project.
If the functionality is changing perhaps a subtle variant of use case, you could expand the User Story to a GWT - Given When Then format. For example: As a TV Customer I want to order PPV. Given I have arrived at the payment screen, I can add my [insert new fulfillment and charing scenario].
In addition, be practical, if the effort is significant, try to break the user story into several smaller user stories, smaller the better. Since the new effort is significant, that means there are likely more sub-use cases that you can break into smaller users stories that can be more easily delivered in a Sprint. If these use cases are more technical or back end, that is fine too as long as it testable, and traces to the original user need.
Hope that helps.
U didn’t talk about tasks
Go to this video: 6:10 m mark: ruclips.net/video/3VuznCGwoS4/видео.html
Please provide SPECIFIC API examples and user stoires
Consider using COSMIC story points, which can be used as a framework for adding items to your backlog. I've created a somewhat fun, and somewhat polished relatively quick introduction: ruclips.net/video/HE6uq-geR7A/видео.html