Epics Features and User Stories - iZenBridge
HTML-код
- Опубликовано: 21 авг 2024
- The video covers the discussion related to Epic, User Stories, and Features.
Agile Trainer Saket Bansal is discussing Epic, User Stories, and Features with Agile Professional.
Resources and Links
✔️ Leading SAFe Training from iZenBridge - bit.ly/3dnQO3Z
________________________________________________________________
Have any doubts email - sales@izenbridge.com
Follow us on - Linkedin - / 2728435
Twitter - / izenbridge
Instagram - instagram/izenbridge
#scrum #scrummaster #scrum #scrumframework #estimation #projectmanagement #agile #feature #estimation #userstory #epicinSAFe #scaledagile #safe #scaledagileframework
Wonderful explanation! Saket is my favorite mentor now 😀❤️👍.
Glad you liked it!
The best explanation I have ever heard. 👏👏👏
Thank you for your comment.
Excellent explanation sir
Thanks for liking
Thanks for the amazing information. Appreciate it.. Can you look at below example and quickly comment if this understanding is correct?
Epic : Airbnb for Healthcare [12 mo]
Feature 1 -- Customer Panel [4 mo]
--- User Story: design UI, Development etc..
Feature 2 -- Healthcare Service Providers [4mo]
--- User Story: design UI, Development etc..
Feature 3 -- Admin Dashboard [4mo]
--- User Story: design UI, Development etc..
Epic is good, Features and Stories are expected to be more user focused.
Example Feature:
Web based onboarding of healthcare service providers to support fast onboarding process.
User Story
As a healthcare provider I should be able to publish my services so people can find the relevant one.
As a healthcare service provider i should be able to share pics of my services so people can know about it.
@@izenbridge yeah right. US will have user oriented details with AC. Thanks :)
You are very articulate. Sending love from North Carolina
Thank you.
Amazing explanation, brilliant ..bravo.
Glad it helped!
S.U.P.E.R.B video… EPIC Explanation 😁👌👌
Thank you.
This is really good discussion and response on spot on point is awesome..
Thank you for checking it out.
Beautiful explanation
Thank you.
@Saket: Wonderful eplaination, please start some business analyst interview series as well.
We published on PO related video this week, we look for more people coming forward to have more PO / BA oriented conversations.
Nicely explained about configuration in tool as admin level as display names but still confused feature--epic--user story or epic--feature--user story????
Keep it up Sir!
Thank you
Sir, one query, when there's no other story to make relative estimation, how can we assign any point value to the story first time? Just to reframe my question, what story point value we can give to the first story in a new project? Is there any standard for this?
In the beginning of the project, first you need to identify reference stories for each size. Team starts looking which one is the smallest story and give it size 1. Then team look at next big size user story and can give it 2 or 3 story points (based on their expert judgement) . Team can continue same process to identify reference stories for other sizes. Also, in the beginning of the project, the reference work items will have an assumed size. As team finishes work items, it is a good idea to pick a recently completed work items as a reference rather than something the team worked on several months back.
Team has to come with definition of small, one of the possible way is , team group all items in size (considering complexity, effort ) order and say the smallest one and rest accordingly .
@@izenbridge ¹¹
Also, we can add MVP has another attribute defining Epics.
In SAFe, MVP is part of epic, so it is recommended to identify what minimum set may be need to validate the assumptions.
@@izenbridge sure.. thank u for everything..
Any chance you can do a video on epic writing and refinement workshop?
I am planning some series around it, I did one workshop on same yesterday.
Still thinking why they Safe 5.0 replaced sprint with iteration...
how to tie feature to epic and user stories? I created epic->feature-> user stories.. and now I want to track the task to epic
Sir, is planning poker and 3C's the same?
3 Cs. Which represent Card , Conversation and Confirmation is to show that User Stories are not elaborated in one go, they get elaborated progressively, more about User Stories : ruclips.net/video/aPBvkUgk08M/видео.htmlsi=KWX_XGoSpQSRZMF8
Planning Poker , is a tool to facilitate estimation of user story where people can apply expert judgement , more on planning poker ruclips.net/video/NfjTX1TgifY/видео.htmlsi=e-aPR4KqVZOyV5W4
@@izenbridge thank you so much!! It's clear now
Safe has introduced features not sure why and they based on still scrum frame works 😢
Sir, do we write user stories in waterfall model?
I posted short to answer your query : ruclips.net/user/shortsYQklWZ7-DpQ
We also have detailed blog on User Stories, you may want to check it out : www.izenbridge.com/blog/user-stories-a-comprehensive-guide-with-examples/
Hi Saket, how can I reach out to you for any queries or concern
We have one platform for generic discussion oguild.com
in case you have some specific query, you can drop email at saket.bansal@izenbridge.com
Is PBI same as User story?
Any Item in Product Backlog can be termed as Product Backlog Item (PBI), yes many of PBI are User Stories but you also have other things in Product Backlog like some technical exploration work (in SAFe we call it Enabler)