User Story in details for Agile Software Development.

[@igorsolaja609]

Excellent video. IMHO, Agile Digest' videos are best on KZbin

[@AgileDigest]

Thanks a lot

[@avinashvarma8855]

Great one Sir. Interesting and Engaging.

[@amargupta1728]

Niladri..very nice and explainde in a simple manner and yes you have god gifted teaching skills.👍

[@karandeeparora7636]

Best video to understand the topic, superb sir. Well explained with ppt. Superb comination of theory and practical examples.

[@JanardhanMankala]

Very good one Niladri..

[@byn135]

This is REALLY helpful for a person like me who's ramping up on Scrum practice. Big thanks, Niladri!

[@jkhokhar4206]

P

[@gobbaka]

Excellent Conceptual clarity. Really i appreciate your effort.

[@shafichowdhury7923]

Niladri nailed!!!!! Awesome simply!!!!!

[@Sibusiso6]

I am a Test Analyst and I absolutely love this. very informative.

[@qwerty1994ize]

All your videos are very well thought out and beautifully crafted. Thank you so much for your time.

[@AgileDigest]

Glad you like them!

[@tanmoyananda]

Loved it... Very well explained Niladri. Thank you so much.

[@mj1737]

very informative sir , thank you so much ...

[@aryarahimi4773]

Greatly explained. Thanks

[@aboubacarsidikidouno331]

Man, this was a wonderful video. I am glad I came across your channel. I am definitely subscribing. Keep up the good work.

[@crazy4earth]

Great explanation 🙏 Thanks All the best

[@ermanjisingh]

hats-off to your website. agiledigest... its really in a structured manner to understand about agile.. I like each and every thing about it

[@AgileDigest]

Thank you Manjit.

[@lifewithtomi7873]

This is really helpful, best class so far! Thank you!

[@puppala773]

Simply Excellent..... Excellent...

[@AgileDigest]

Thank You

[@mustafasange]

Thanks for the video

[@dheeraj.vpoojari7696]

You covered almost everything in one video, this is really amazing

[@AgileDigest]

Thanks a ton!

[@sreekumarmenon7957]

Hi Niladri, you did an excellent job in presenting the concepts. I really enjoyed your presentation. Thanks a lot.

[@manishbillaiya4395]

nice presentation ...Need more like this.

[@AgileDigest]

Thank You, Sure

[@saurabhsinghchandail]

Really impressive and informative video. Thanks for making these terms simpler.

[@kurtcampher4716]

This is an excellent vid. Love the examples.

[@AgileDigest]

Thank You

[@loshomusic]

Excellent presentation. Thanks you very much!

[@maheshmohite7578]

Good one

[@250taz]

Hi, Can we take Change request that are urgent as per client as a spike ?

[@ramsha547]

This was beautifully explained

[@bonkuroy6549]

Really worth appreciating ...

[@AgileDigest]

Thank You

[@melvinpereira6806]

Very Informative. learned many things. Well presented.

[@Najstar43211]

Loving your videos keep up the good work. I'm slowly making my way through a playlist of your videos

[@AgileDigest]

Awesome! Thank you!

[@MKhan-zj3fb]

Great video covering most/all items associated with a user story, thank you.

[@AgileDigest]

Glad you enjoyed it!

[@shubhamgupta9553]

Thanks it was very good and informative.

[@gayatrigaitonde3744]

Excellent video Sir just like every video of yours.

[@tunapradhan3595]

Can I tell you one thing sir.. your tutorial video is not just an excellent but the explanation , content just forced us to make attention.. thank you so much for your effort.. wish like agile , if you could have any other technology video like , project management (cost management, risk management etc) .. not sure if you have any plan in near future , but exciting to see any new video..

[@srikanthbabu419]

Great explanation and very informative.

[@heidijackson1523]

Thank you, this is very helfpful!

[@esmailiyou]

Thx, though so much theory and very few real examples

[@rumanaamin6329]

Very helpful Niladri.

[@mmiittrroovv]

"As a SG application Admin" - What SG stands for ? :) P.S. Thanks for the presentation

[@AgileDigest]

Official the name of the application is Swiss gear.

[@mmiittrroovv]

@@AgileDigest Thanks :)

[@utubeddong]

Good stuff! Thanks

[@g-ronnmendoza]

Very informative and straight to the point.

[@AgileDigest]

Thank You Gerry.

[@NehaSharma-qu4tn]

V informative

[@rowenajocson1566]

This is a great material ! Thanks for sharing ...

[@Mr.Chakle]

How to write test cases from user stories

[@Zpoetry0909]

Awesome video, very useful! Do you have a video where you use user stories examples?

[@AgileDigest]

Story example, sorry not yet have it.

[@adeliyiseyi525]

Thank you for the video. Two questions: 1. The technical spike you spoke of, is it about building end-to-end reference stories to size up story points? and 2. is there always a need for an attribute and data type description for every story documented?

[@AgileDigest]

No Technical spikes are for any kind of Analysis or Research work. Did not understood the 2nd question.

[@geraldnathan9646]

Excellent ! I like it!

[@goodthoughts453]

Could you please help me on this question ? #38 You have been given the following story: “As a plant lover who travels frequently, I want to have an automated watering system, so that my plants won’t die.” You have also been given the following acceptance criteria: 1. The water should turn on when the temperature is > 85 degrees and the moisture content of the soil changes from “normal” to “dry”. 2. The water should be dispersed for 5 minutes at the rate of 0.5 ounces per minute. Which one of the following provides the proper values to use to achieve 100% two-value boundary value analysis coverage with the minimum number of test cases? a. Temperature at 85 and 86, moisture at “dry” and “normal” b. Temperature at 85 and 86, moisture at “dry” and “normal”, water disbursement for 5 minutes and 5 minutes 1 second, rate at 0.5 and 0.4 c. Temperature at 85 and 86, moisture at “dry” and “normal”, water disbursement for 5 minutes and 4 minutes 59 seconds, rate at 0.5 and 0.6 d. Temperature at 85 and 84, moisture at “dry” and “normal”

[@AgileDigest]

+aishwary singh what is your question?

[@goodthoughts453]

What can be the answer that minimum number of test cases required as per boundary value analysis ...as per my understanding the answer is "a"

[@avnishso]

Nice video.. Sir u did not mention project manager role.. Where they fit to work with user story?

[@AgileDigest]

PM does not fit in Scrum Team, They can play an overarching role

[@JayanthChennai]

Niladri sir, the Title which you mentioned in the "Story" in the card portion of Jira, does we create in summary field as when we create a new story, 1st field is "Summary" and then "Description".

[@AgileDigest]

Yes

[@AgileDigest]

Yes

[@maheshmohite7578]

can we assign one user story to multiple people at the same time ?

[@AgileDigest]

If it is in sprint, it's owned by the team, usually be executed by more than one members

[@ImRajeshR]

Very informative.. Thanks for the session. Just a question whether user story replace BRD for development team to build FSD/FRD ?

[@juno7893]

👏🏻👏🏻👏🏻

[@mahapol8812]

How to estimate user stories and subtasks as a combine effort.can we estimate epic at start of print.

[@AgileDigest]

Epic estimation is not necessary to start a sprint. Estimate your user story on Story Point. Estimate the effort on sub tasks, which will combined to show the total effort estimate for the user story

[@poojachawla9597]

Very nice video. About 13:30 - how is it practically possible that User story is always independent of other stories? Software requirements can be inter-related. In 25:20 u said one story can depend upon multiple stories as successor/predecessor. So how is it INDEPENDENT? Anyways thanks a lot for your wonderful effort. Much much appreciated !!!

[@honestcomments8053]

Thank you. Very well done! BTW, my company uses T in SMART for testable.

[@AgileDigest]

T is testable in INVEST. Time bound in SMART.

[@anilgondi1008]

How can we say that the user story is good or perfect??

[@AgileDigest]

Responded on the Video - Comment Response Feb 2024

[@mmmikram]

Thanks, Very good sharing of knowledge. I need some more explanation on technical spike, can you please explain it with some examples.

[@AgileDigest]

Technical spikes are are any technical work, research or analysis kind of work. some time you may face difficulties to estimate a story point of a user story, a research can help you to uncover the un-certainties. some time you may need to migrate some data from mainframe system to your test database, which is not a need from function prospective or from your PO, but to enable the test for multiple stories, you need to have your test data ready etc etc.

[@mpsstudio-tutorials7402]

Thanks a lot!

[@ak_gaming1594]

Can u share some example of user story

[@AgileDigest]

Sure send a mail to [e-mail]

[@tehiladar8606]

Thanks a lot for this presentation. It is a great one! Few questions that I really appreciate your help with: If I want to make a UX UI changes, I need to make a user story? If I have a small change regarding to the site flow, I need to create an epic and a feature ? even if it will be only one sentence? Will be happy to hear your opinion. Thanks again.

[@mahapol8812]

Great thanks.however I have few observations in Jira When I set estimated hours for Epics,user stoires ,it does not calculate correct time for tasks in user stories. for e.g 1. I created one Epic and did'nt set any time estimate but entered due date ,for example if today is 21st May ,I set due date as 24th May 2. I created user story US01 in that epic and did'nt enter any estimate in user story as well 3. I created 3 sub tasks ,development,design.testing in user story US01 and entered 2 days for each task , 3 subtaks tasks time sums upto 6 days but it does'nt change the due date set for Epic. How do I set the estimate days /hours in JIra for epics/user stories/tasks?

[@ohfama]

Great video! If may I ask you, could you make the power point presentation available for download somewhere? I would love to to use it in my classes, but it will be necessary to translate it into portuguese...

[@AgileDigest]

Thank you Farius that you liked the video. We also conduct training using the same presentation, and to keep it unique, we don't share our presentations.

[@nikhilpawar31]

@@AgileDigestI did like the info you shared in this video but this idea of not sharing "to keep it unique" is NOT Cool, brother. You never know someone could come up with a different version of the same say.. in a different language, which could be better understood by a certain viewer group. Pls don't mind. Cheers!

[@pesilpathirana8878]

Can you please explain the reasons of tasks are estimate using hours?? What if, after we estimated tasks using hours the total number of hours exceeds the sprint length?

[@AgileDigest]

Hours are for effort estimation, so when you create task you are estimating with Hours. Estimate on or before your sprint planning. commit the number of stories that is with in your team capacity. Plan the Capacity before sprint Planning.

[@pesilpathirana8878]

Hi thanks for info. I have a small confusion. Let's say our velocity is 50 story points and sprint length is 2 weeks. In sprint planning meeting we pulled 50 warth of stories for sprint backlog. Then we break user stories to tasks and estimate the effort using hours. Then we noted that total number of hours is 2.5 weeks. At that time velocity and effort estimate is conflicting. Isn't it?

[@pesilpathirana8878]

Finally, I understood some benefit of estimation of tasks using hours and how to overcome my second question. According to my understand, breaking user stories into tasks is beneficial to understand “how much work team can committed to a sprint”, if we don’t know the teams velocity. However before estimating tasks, Scrum Master should prepare a team’s capacity planning to understand what is the maximum/total working hours of individual member will have in the sprint. After that, in sprint planning team can break user stories to tasks and scrum master can facilitate to monitor the induvial task commitments against the total capacity of individual person. If one member is exceeding the total capacity SM should inform it to the team in advance. In this way we can avoid the overloading or underloading of a team member with in sprint. Once all the team members committed to tasks with their full capacity we can identify the velocity by calculating the committed user stories. However if the team is mature enough to estimate using user story points and we know the average velocity (after run 4+ sprints) there is no need of breaking stories in to tasks unless company use individual commitments as their annual evaluation KPIs. To avoid exceeding the sprint length, Scrum Master should prepare a capacity planning before individual task commitment. The SM should monitoring the capacity of individual team member by compering to his/her total capacity so that team will not exceed the spring length with the estimation. However in this method we cannot pull the user stories to sprint backlog by considering velocity, then break them into tasks and again estimate using hours. Either we have to pull stories by considering the velocity or we have to pull stories using team’s capacity.

[@saeedtawfiq]

Hello I would like to chat with you

[@rishikesh831]

Please make a video on Technical debt.

[@AgileDigest]

Sure

[@syedarazvi7078]

Description: As a sentinel team member, I want to know what options exist to export the table view search results, so that we may present the option to the business... sir...I unable to understand what I have mentioned above how can I create story in ServiceNow? card: P$CSERVICEPORTAL - Export table view search results to excel research

[@JayanthChennai]

Niladri sir, kindly give a real time example of Technical spike to interpret it better.

[@hudakhaled8353]

Thank you for this great video, but I don't understand what is the technical spike..?

[@AgileDigest]

Thank You, Technical Spikes are Analysis or research work in your Backlog.

[@ShivaKumar-in8hn]

Nice very nice

[@sunvarutube]

This information was really useful and greatly presented. Quick question who define these characteristics, is it an experience that involves to these or is there any baseline created as framework e.g INVEST. For sure Scrum just discusses high level ceremonies but doesn't defines its characteristics as the presenter presented. It was interesting and practical. I would like to know further on this.

[@RanjanVron]

thank you sir

[@orionstar6268]

Hello...good job ... very informational but you need to polish your accent to makes it hard to understand. Thanks

[@AgileDigest]

Thank you. Sure

[@racheldorthy1777]

hi sir will you please take a lesson on Requirement traceability matrix, FRD and BRD.

[@Santoshkumar-vi3ix]

Thanksss

[@Santoshkumar-vi3ix]

Thanks

[@Santoshkumar-vi3ix]

Hii

[@RU-qv3jl]

Yet another XP practice that has been screwed up by scrum.