Скачать с ютуб Jira | Scrum | Story Point Estimation | 05 | Tamil | Absolute Beginner Guide в хорошем качестве

Jira | Scrum | Story Point Estimation | 05 | Tamil | Absolute Beginner Guide

In this video, we will be learning one of the most important and difficult process on Agile product development which is story point estimation. There is no concrete steps or methodology to arrive at the story points for a given story. Like everything else in Agile, story point also comes from experience. Story Points represent the effort required to put a PBI (Product Backlog Item) live. For example,1 Story Point could represent a range of 4–12 hours, 2 Story Points 10–20 hours, and so on. This time distribution is unknown during estimation. By using reference PBI’s relative to which to estimate, it is not necessary to know how much time it takes. You just want to have a rough indication of how much time the PBI will take to complete. Why do we need estimation at all? 1. Arrive at a shared understanding among the team members, 2. Organize the Product Backlog based on value and effort, 3. Plan upcoming work, 4. Slice the stories and work smaller. Story points vs Hours Traditional software teams give estimates in a time format: days, weeks, months. However, many agile teams have transitioned to story points. Story point === overall effort required to fully implement the PBI (product backlog Item). Why not dates? It may sound easier if we provide the estimate on time. But what stopping us? • Dates don’t account for the non-project related work that inevitably creeps into our days: emails, meetings, and interviews that a team member may be involved in. • For you it can take only 3 days for but for me it will take 5 days. • We already mentioned story point is effort and Effort is not equal to time. Story points are abstract, relative, and about effort. What should the story point estimate? Starting from the start of the sprint until the definition of done is met for the backlog, the story point should consider everything as effort. How do we estimate? • Estimation should be done by people who are actually doing the work. • Get multiple estimates from all the people involved in the team. The average of the estimate should be a correct one. • Don't use subjective measures, use objective measures. Use relative estimate techniques instead of absolute estimation. . Fibonacci series: It's not accurate, but on an average 20 points roughly equates to 16 hours. Support by donating: --------------------------------- Google pay UPI Id: arulprasath36@okicici Name: Arulprasath Email: [email protected] You can watch my other tutorials ------------------------------------------------------ 1)Selenium basics: http://bit.ly/2XtOt1F ​ 2)Selenium Advanced: http://bit.ly/2WYieZe ​ 3)TestNG Absolute Beginner Guide: http://bit.ly/2N6xgaM ​ 4)Data-driven framework: http://bit.ly/2WVjSFT ​ 5)Page Object Model: http://bit.ly/2IAXJZR ​ 6)How to write XPath on our own: http://bit.ly/2KwMLql ​ 7)Must know Java concepts for Selenium: http://bit.ly/31Ro7G8 ​ 8)Selenium Interview Questions: http://bit.ly/2N6xu1F ​ 9)Java for Selenium Automation: http://bit.ly/2IylOAh ​ 10)Maven beginner guide: http://bit.ly/2Rsigm0 ​ 11)Github Absolute beginner Guide: http://bit.ly/2Kxdzqj ​ 12)REST Web services beginner guide: http://bit.ly/2N69rQq ​ 13)Cucumber absolute beginner guide: http://bit.ly/2X0lSBB ​ 14)Acceptance Testing (Fitnesse) beginner guide: http://bit.ly/2Y6oE55 ​ 15)Jenkins beginner guide: http://bit.ly/2X39fGb ​ 16) Jmeter beginner tutorials: https://bit.ly/32achqW ​ Follow me on Instagram: https://bit.ly/2Ez36rH ​ Facebook: https://bit.ly/2TqPlis