*STORY POINTS are only for developers* Naaah!! This is just a "myth" 🎓 Story points are often shrouded in myths and misconceptions. A few of which include 👉 Believing they measure time directly 👉 Assuming they are always precise 👉 Thinking they can be compared across teams 👉 Having the assumption that they are only used for software development 👉 Presuming they are a direct measure of progress 🎓 What is a Story Point.... This is a unit of measure used in Agile project management to estimate the relative effort required to fully implement a user story or a product backlog item It is a relative measure of complexity, efforts, and size of a task. 👉 In simpler terms, story points are used to estimate the difficulty, risk and complexity of a task or user story. The most common scale used to estimate story points is.... 📌The *FIBONACCI SEQUENCE* 👉 Named after the Italian mathematician - "Leonardo Fibonacci" in the 13th century, the Fibonacci Sequence is a series of numbers in which each number is a sum of the 2 preceeding numbers. Just like 👉 0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, and so on... Where tasks with the lesser numbers are considered simple tasks while those with the higher numbers are considered complex tasks. ♾ Remember, 👉 Story points are relative and team specific so they shouldn't be compared across teams or used as direct measure of individual performance. 👉 Also, in as much as story points are commonly used, they are "not mandatory". 📌 Other methods like T-Shirt sizing or simply tracking the completed stories without assigning points can still be applied. I do hope you've learnt something today. Cheers... #learningiscontinuous #Iamanarchitectofsuccessfulprojects