Great video. I appreciate the help. This is my first BA role on an agile/jira team. I actually envisioned the very simple "Description: User Story Acceptance Critera: Gherkin" format yesterday when looking at how messy the user stories are currently, so seeing that you do exactly that was a great confirmation that I'm on the right track!
The drop down on the label field will show existing labels. If you've never used the label before, then you'll have to type it in the first time. You can see at 15:26 I added "Ready" for the first time as it didn't exist before then.
Would you be able to elaborate on the role of a BA once all these user stories have been refined and are sprint ready. What is the BA doing for the project when most of the work is being done by the developers and testers?
When one sprint ends, the next one starts. The BA is always working on the user stories for the next sprints. Keep in mind that BAs only exist on large complex systems/organizations. So what's usually happening is the application is getting lots of asks from many stakeholders. The BA is taking those asks, clarifying them (impacted processes, data, biz rules, stakeholders, etc), discussing them with other BAs from impacted systems, creating user stories, then collaborating with the team (PO, devs, QA, architects, etc) until ready for estimation and prioritization. By the time that's all done, the current sprint is ending. Additionally, during the sprint there may be clarification required aspects that may have been missed or not covered in the user story. Ideally a BA should be working a couple of sprints ahead.
@@AngeloTheBA thank you for your clear and concise clarification of my question. This has definitely helped me get a better idea of what to expect during the full duration of the project. Thank you for your reply and the video.
Thank you for this video!! You're a great resource!
Need BA Help? Come train with me metabusinessanalyst.com/train-with-angelo-the-ba/
Well explained. Thank you for sharing.
Great Video. Keep it up!
Thanks!
Excellent Thank you.
Great video. I appreciate the help. This is my first BA role on an agile/jira team.
I actually envisioned the very simple "Description: User Story
Acceptance Critera: Gherkin" format yesterday when looking at how messy the user stories are currently, so seeing that you do exactly that was a great confirmation that I'm on the right track!
waw man you're great, thanks
Thanks for this useful content. Can you please explain how to add "raw,refined and ready" user story field states on the drop-down menu?
The drop down on the label field will show existing labels. If you've never used the label before, then you'll have to type it in the first time. You can see at 15:26 I added "Ready" for the first time as it didn't exist before then.
Would you be able to elaborate on the role of a BA once all these user stories have been refined and are sprint ready. What is the BA doing for the project when most of the work is being done by the developers and testers?
When one sprint ends, the next one starts. The BA is always working on the user stories for the next sprints. Keep in mind that BAs only exist on large complex systems/organizations. So what's usually happening is the application is getting lots of asks from many stakeholders. The BA is taking those asks, clarifying them (impacted processes, data, biz rules, stakeholders, etc), discussing them with other BAs from impacted systems, creating user stories, then collaborating with the team (PO, devs, QA, architects, etc) until ready for estimation and prioritization. By the time that's all done, the current sprint is ending. Additionally, during the sprint there may be clarification required aspects that may have been missed or not covered in the user story. Ideally a BA should be working a couple of sprints ahead.
@@AngeloTheBA thank you for your clear and concise clarification of my question. This has definitely helped me get a better idea of what to expect during the full duration of the project. Thank you for your reply and the video.
TIGGGGGHT
Lol