You are so correct, everyone should be clear from the user story what the release goal is for the client/ end user. Writing a user story from a developer perspective is fundamentally not scrum which should be who, what, why and NEVER HOW! PO wont necessarily have the full Dev knowledge and will block the Dev conversations by doing user stories this way.
You are so correct, everyone should be clear from the user story what the release goal is for the client/ end user. Writing a user story from a developer perspective is fundamentally not scrum which should be who, what, why and NEVER HOW! PO wont necessarily have the full Dev knowledge and will block the Dev conversations by doing user stories this way.
Hi
Thank you
Thank you 😊
Number one, it is called USER story,so that alone should clear the confusion.
Straight, simple, period and thank you 😊
What if they asked you what projects are you currently working on ?
How would you overcome this challenge being a Scrum Master in that environment?
Hi