JIRA Tutorial for Agile Business Analysts & Product Owners
JIRA is one of the most popular software tools for agile teams and agile business analysts should know how to use it.
Ready to make the transition into business analysis? Do you want to be able to produce high-quality BA deliverables that get results? Come train with me metabusinessanalyst.com/train...
metabusinessanalyst.com/busin...
00:00 - Introduction
00:41 - Business Analysis in Agile
04:40 - Epics/Features in JIRA
05:37 - Epic Hypothesis Statement
06:55 - Adding User Stories to Epics/Features in JIRA
07:58 - Authoring Epic/Feature Attributes & Details in JIRA
10:20 - User Stories & Acceptance in JIRA
15:18 - Adding User Story to a Sprint in JIRA
16:49 - Note to BAs
Contact Me
To see a video response to your more extended questions
- www.metabusinessanalyst.com/c...
If you have a more personal/specific question and want a direct personal response (may still anonymize and post or make a video to respond) use Facebook messager
- Send me a message through the page / metabusinessanalyst
- or directly in FB messager m.me/metabusinessanalyst
Пікірлер: 15
Thank you for this video!! You're a great resource!
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!
Well explained. Thank you for sharing.
Excellent Thank you.
waw man you're great, thanks
Great Video. Keep it up!
@AngeloTheBA
9 ай бұрын
Thanks!
Need BA Help? Come train with me metabusinessanalyst.com/train-with-angelo-the-ba/
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?
@AngeloTheBA
Жыл бұрын
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?
@AngeloTheBA
Жыл бұрын
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.
@jacobmark8810
Жыл бұрын
@@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
@AngeloTheBA
Жыл бұрын
Lol