User Story Points in Scrum
Agile principles or scrum guide dont talk about User story points. Over time these emereged from xtream programming. Could you let me know if this is correct.
Yes, story points emerged from teams working in Extreme Programming. Ron Jeffries wrote about the creation of and problems with story points on his blog. By the time Extreme Programming Explained 2nd Edition came out, Kent Beck didn't go into details specifically on story pointing, and the XP practices work with various forms of estimation and planning techniques.
I believe Mike Cohn was responsible for the modified Fibonacci sequence we associate with story points today. He landed on it in or around 2007 for his first run of Planning Poker cards.
James Grenning had introduced Planning Poker 5 years earlier, explicitly as a story estimation technique for use in XP. However, he used a day-oriented sequence of 1, 2, 3, 5, 7, 10 and infinity.
A bit outside of the question. The events and artifacts that are specified, are viewed as the minimal necessary in an implementation framework. The Scrum Guide does not specify additional methods, and story point estimation is such a practise. Even user stories themselves are not mandated.
Scrum then allows practises that are deemed to add value by the tean, to be added, as long as Scrum values and principles are not violated.
Ron Jeffries himself don´t use them anymore,let the story points rest in peace.
I suggest https://www.amazon.com/Applying-Scrum-Kanban-Pointless-Book-ebook/dp/B0…