Super Video

Perfect explanation ❤

Do you have a link to download this template?

Fruitful video

Very good one Niladri..

Full form of DEEP is Detailed,Estimated,Emergent and Prioiritized.

What a clear and great video! Thank you very much, for bringing all the scenarios in.

Thank you

Very Informative to point

Well done!Indeed, a great video to learn and understand. A suggestion: make a practical planning poker session in real team developing software product with POs, BAs, Developers and Scrum Master; purposely to make other understand who it is executed. Nevertheless, I have understood it quiet well, therefore I am contend. Keep posting more video on Scrum related issues.

Such an amazing video with lots of real life scenarios. Exceptional ✨

Product backlog cobtains both refined and unrefined user stories. Sprint backlog contains only refined stories that meet the definition of ready and are being worked on

Are the stories independent of each other in case of workflow splitting? Are they following the Invest criteria, Independent being one of the requirements. Here we cannot complete a story unless other stories are completed. That means we cannot notify customer of price update in cart unless we update it in admin. Correct me if i am wrong.

thanks

Jira is shit, who the hell uses it, slows down development

Stop hand gestures

This is very helpful. Can you share your ppt presentation?

So helpful videos, many thanks to Niladri.

Wonderful Video. Thank you so much!

Where I get more videos on Sam e

Extra ordinary session 🎉🎉🎉

But as you use Y axis as hours, how would you know which hour is for which Story point?

perfect for beginners, thank you sir

I like a way of your explaination, but I have one question, when we are doing the product grooming in our scrum process?

DOD is criteria that determines the readiness of user story for release.

Thank you sir for this vedio. Lot of insight got for SAFe.

Good efforts, thank you. Usually BA/PO business analysis would be converted into user stories, where the technical feasibility, or tech gaps needs to be analysed tech debt will be raised. Further in some cases, where current system configuration/function is not clearly documented during build, requires tech debt.

Spikes will be created when we want to work on new new technologies which requires POC and spikes will not have any story points

Very structured approach. loved it.

Anything which is blocking you to continue your activity

INVEST I- user story should be independent N- negotiable- user story can be repriorotozed/ changed/ deleted if it is not delivering any value to the end user. V-Every user story after implement should deliver value to the end user E- user story should be estimatable S- User story should be simple and understandable T- user story should be testable

Burndown chart is a chart that shows how much work is still remain to complete

Product Backlog will contain all the prioritized list of user stories that should be implemented as a part of project, but sprint backlog will contain the user stories which we are working current sprint

Niladri you have been making SAFe to be understood in the best possible manner. Great to see this video and it act as a brushup experience before heading for interview as well 😊

Move the story to the next sprint.

In SAFe, during PI Planning, How Business owner or stakeholder give Business value to each PI objectives and how will they assess actual business value, could you please explain us

How Business owner or stakeholder give Business value to each PI objectives and how will they assess actual business value, could you please explain us

How to Assess Actual Business Value in PI Planning

Importance of this Question: Optimizing sprint planning meetings ensures they are time-efficient while still thorough, improving team productivity and project momentum.

When SM also needs to work as a RTE, what things we should look at? A video or reel on this would be nice

But the scrum guide suggest scrum master and product owner can be a single person if required

Yes, team members can write the user story and get it reviewed with product owner and it is important to know and understand all the team members while working in agile

Background music is loud

Could you make video on problem solving techniques used by scrum master and risk analysis techniques a scrum master should know

​​அல்லாஹு அக்பர்

agiledigest.com/definition-of-ready/

Importance of Question: Exploring the possibility of a Scrum Master also serving as a Product Owner touches on Agile's flexibility and roles' adaptability. This consideration delves into balancing facilitative leadership with product vision responsibilities, reflecting on Agile's emphasis on team dynamics, role clarity, and maintaining effective balance between guiding the team and advocating for the product's success.

No there no role as Project manager in scrum infact we have roles like Scrum master, Product owner.