00:00 - Intro 00:46 - What is Product Backlog 01:25 - Who participates in this exercise 03:02 - When to conduct this exercise 03:30 - How to create Product Backlog 05:01 - Outro
All your videos are excellent. My only recommendation would be that you show examples of each topic you discuss. You did this in the first video and it would be nice to see the hotel booking website idea sampled throughout all the videos. Thanks again!
Hello Vibhor, You are awesome. I request you to please guide me in Business Analyst domain. Please Suggest something as I am going to start my journey as a BA in a month. From where to start and how to master things. You are doing great job !!
Just a question, in the Release planning phase we list down approx dates. However in the product backlog creation phase, when we are placing in user stories, how do we control the scope to meet the Release planning mentioned timeframe? as this exercise happens post dates provided in the release planning phase.
Well again a concise and informative series...May I know how if we get features with same rank using WSJF method, especially in a program where are more than 10 product owners
Can you tell us a little bit about what happens when a customer only knows the problems. So they don't come to you with a request in their head, but they start telling you what they can't do. What do you call these statements and how do you collect them, how do you turn them into requirements?
Problem statements: How to convert them into requirements: 1- Write the problem 2- identify the simple reason behind the problem. 3- brainstorm the solution 4- choose the best solution. This is your requirement.
Hi vibor , very informative session and waiting for you website ..though I have a questions how do we manage change in agile ? Is it feature priorization ?
Agile enables multiple short feedback loops wherein the business is required to check and provide their approval that the team is heading ion the right direction. This way if there is a need to CHANGE directions the team can easily pivot in the upcoming iteration. That's Agile enables continuous change.
Thanks for the awesome session. I have basic doubt in the order 1) product vision 2) product road map next comes the release plan or backlog? Because without backlog we can't create the release plan is my understanding. Pls help confirm
00:00 - Intro
00:46 - What is Product Backlog
01:25 - Who participates in this exercise
03:02 - When to conduct this exercise
03:30 - How to create Product Backlog
05:01 - Outro
Heyy I need your help..
Kindly drop me your email
The perfect video I was looking for.. thank you for real time examples
Thank you sir! Awesome, simplest explanation. You deserve a trophy!
Appreciate that Olamide
very very effective..... simply good
to the point and usable
All your videos are excellent. My only recommendation would be that you show examples of each topic you discuss. You did this in the first video and it would be nice to see the hotel booking website idea sampled throughout all the videos. Thanks again!
Excellent and very Crispy
Great video, thanks!
Super duper !
Amazing.. you explain so well with a background and effect that gives a feel like we are in the beach relaxing:-)
Well explained
Nicely done, Love the series, thanks!!
Hello Vibhor, You are awesome. I request you to please guide me in Business Analyst domain. Please Suggest something as I am going to start my journey as a BA in a month. From where to start and how to master things. You are doing great job !!
Just a question, in the Release planning phase we list down approx dates. However in the product backlog creation phase, when we are placing in user stories, how do we control the scope to meet the Release planning mentioned timeframe? as this exercise happens post dates provided in the release planning phase.
Well again a concise and informative series...May I know how if we get features with same rank using WSJF method, especially in a program where are more than 10 product owners
6:15 Epic
Can you tell us a little bit about what happens when a customer only knows the problems. So they don't come to you with a request in their head, but they start telling you what they can't do. What do you call these statements and how do you collect them, how do you turn them into requirements?
Problem statements:
How to convert them into requirements:
1- Write the problem
2- identify the simple reason behind the problem.
3- brainstorm the solution
4- choose the best solution. This is your requirement.
Hi vibor , very informative session and waiting for you website ..though I have a questions how do we manage change in agile ? Is it feature priorization ?
Agile enables multiple short feedback loops wherein the business is required to check and provide their approval that the team is heading ion the right direction. This way if there is a need to CHANGE directions the team can easily pivot in the upcoming iteration. That's Agile enables continuous change.
Thanks for the awesome session. I have basic doubt in the order 1) product vision 2) product road map next comes the release plan or backlog? Because without backlog we can't create the release plan is my understanding. Pls help confirm
You need an initial product backlog. The videos in the whole series guide you how to do that.
what is the best research method to test backlog features with customers?
Try a product box.
Do you provide mentorship. Please let me know.
I do Sneha. I don't currently have capacity though. Once my website is done, you'd be able to book time. Hope that helps.
@@VibhorChandel yes absolutely it helps. Please let us know whenever it is ready. Thank you Vibhor
What tool do you use to create a product backlog?