I see a lot of scrum leads asking for functional user stories to be written for extremely technical epics with no end user interaction. Such as: receiving a message from a third party when the schema is already complete and agreed. All of the tasks are technical in nature, but they argued that they're all functional. It was mainly to come up with the architecture around how the message would be received and processed into the system, with no view/update to the end user. As far as they were concerned this was just happening 'in the background'. There was a separate EPIC to work on the screen display and CRUD of these messages. Would you agree this is where we should use technical stories, not functional user stories? It made no sense to me having to write "as a user I want to validate the incoming message" - that's not a user function. I don't know, I feel like people have very different understandings of functionality. Developers seem to think if it does ANYTHING it's functional.
Yes. Those must be technical user stories. If a story has to be functional there must be human interaction. We are adding a drop down that users will come and interact with. Or a donut chart that shows various parameters. These must be functional stories . Technical stories will be - if the revenue goes below $X then email is sent to the executive . No human interaction and there is an action .
How would you write agile story for data virtualization/business intelligence projects? ETL type effort . Can you please post example here in comments?
A BA might not use SQL...you'd had that to your data person or developer to query and execute. If it was you doing SQL, that'd make you a data analyst.
I see a lot of scrum leads asking for functional user stories to be written for extremely technical epics with no end user interaction. Such as: receiving a message from a third party when the schema is already complete and agreed. All of the tasks are technical in nature, but they argued that they're all functional. It was mainly to come up with the architecture around how the message would be received and processed into the system, with no view/update to the end user. As far as they were concerned this was just happening 'in the background'. There was a separate EPIC to work on the screen display and CRUD of these messages.
Would you agree this is where we should use technical stories, not functional user stories? It made no sense to me having to write "as a user I want to validate the incoming message" - that's not a user function.
I don't know, I feel like people have very different understandings of functionality. Developers seem to think if it does ANYTHING it's functional.
Yes. Those must be technical user stories.
If a story has to be functional there must be human interaction. We are adding a drop down that users will come and interact with. Or a donut chart that shows various parameters. These must be functional stories . Technical stories will be - if the revenue goes below $X then email is sent to the executive . No human interaction and there is an action .
I have a question: How do you write user stories for each data element. Is it maintained only in data dictionary?
@@arunaswaminathan420 The Data points will be mentioned in the acceptance criteria .
Self explained examples especially for a beginner like me. Thanks so much.
@@amaefuleperpetua4797 Thanks for watching 😀
@@amaefuleperpetua4797 Do SUBSCRIBE for more content 😀
The examples are really good. You describe with unique format. Thanks
@@RhishabSharma Thanks for watching
How would you write agile story for data virtualization/business intelligence projects? ETL type effort . Can you please post example here in comments?
Sure . Will post a video on this. Thanks for watching our video . Do SUBSCRIBE if you haven't already.😀
Great video. Can you please make a video to illustrate where exactly BA uses SQL?
A BA might not use SQL...you'd had that to your data person or developer to query and execute. If it was you doing SQL, that'd make you a data analyst.