Fibonacci Sequence for Story Point Estimation The fibonacci sequence is a popular scoring scale within some teams. Story points are relative and are measured against a baseline or benchmark. I think most teams use fibonacci numbers. When doing estimates with relative sizing techniques, we recommend using numbers in the Fibonacci sequence rather than t-shirt sizes (S, M, L), 1-10, percentages, or other similar values. For a complete break down on the points vs. The formula to arrive at a Fibonacci sequence is: Xn = Xn-1 + Xn-2. Sometimes, cards with 0, ½, ∞, ?, and. #2) Release Level includes assigning story points to user stories that can help in defining the order of user stories based on priority and can. Story points in Agile help you and your team optimize workflows for efficiency and business value. g. Some teams will use the classic Fibonacci sequence, while others will use the. But before you go, remember that story point estimates are not a perfect science, and there will always be some. Though not required, adding values to the T-shirt sizes used in the fruit salad game helps us estimate team velocity over time. Perfect for high-level estimation. For 8 story points, the number of hours might be 15 to 20 hours. . The Fibonacci series graciously defines the complex nature of building the product or delivering the right product. It's a relative Estimation Technique. 5 = 13 Story Points. Selecting from a specific Fibonacci-like sequence of Story Points allows us to capture uncertainty. Nevertheless, the recommended approach would be to use relative estimation using (modified) Fibonacci sequence to calculate the value or impact of a feature or a backlog item. V. 1. 618, and . A Story Point could be thought of as a number that would let the developer understand the level of difficulty of a User Story based on several factors such as risks and efforts, complexities, and uncertainty revolving around the User Story. Agile Story Points: Modified Fibonacci Sequence Final thoughts What is the modified Fibonacci Sequence? In this post, we’ll focus on the modified Fibonacci. You might be wondering why we'd choose the Fibonacci Sequence for story points estimation. Our Agile/Scrum team follows the Fibonacci sequence for story point estimation. Story points are used to estimate the effort required to complete a user story. -The amount of effort involved in 1 story point should remain stable for your. 2. Later I realized that this task can be broken down into 2 smaller sub-tasks. Should you measure user stories in hours? It might seem like a natural choice, but equating story points to hours neutralizes the benefits of relative sizing. As a refresher, here are the larger Fibonacci numbers: 13, 21, 34, 55, 89, 144. You may assign point values using consecutive whole numbers or the Fibonacci sequence, which is more popular because it leaves room for approximation. In order to make an accurate estimation of story points, there are a few things to keep in mind: How to measure story points: the Fibonacci sequence. Story points are a unit of measurement for estimating the effort required to complete a work item on the backlog. ) Agile Estimation Is Abstract On PurposeAlso, a Fibonacci-like sequence such as 1, 2, 3, 5, 8, 13, often used in story points, can be easily used in hours. They serve as units of measurement for. . Story Points are a tool to make that understanding easier by providing a point of comparison between work the team has already done and work that's still on the. La suite de Fibonacci agile donne aux équipes une façon plus réaliste d’aborder les estimations à l’aide de story points. As described above, there are three ways you can size user stories: linear sequence, Fibonacci sequence, and using T-shirt sizes. This sequence is the sum of the previous two numbers in the series. The higher the number, the more intricate the story point becomes. 1170 – c. The Fibonacci scale is a series of numbers which increase exponentially. These numbers may seem random, but they’re actually rounded variations of the Fibonacci sequence. That is, each story point value is implicitly a range--just like a bucket can hold a range of amounts of water. In planning poker, members of the group make estimates by playing numbered cards face-down to the table, instead of speaking them aloud. It is the ratio of a regular pentagon's diagonal to its side and thus appears in the construction of the dodecahedron and. When we observe the geometry of plants, it’s easy to recognize recurring patterns in nature. Even though a story may have minimal development effort, it still needs to be tested, regressed, documented, and deployed. The term originates from the way T-shirt sizes are indicated in the US. 61803398875 . Using the Fibonacci sequence for agile story point estimation. You can use two scales to determine your story points: a linear scale or Fibonacci sequence. So the sequence looks something like this. So, I can create 2 sub-tasks with story points 8 and 13. Zero-story point exists also and that can be applied to tasks that require almost no effort at all. The choice of a specific number from this sequence reflects the amount of uncertainty. ). The. 1. Some plants branch in such a way that they always have a Fibonacci number of growing points. Story Points in Fibonacci Scale. That is, 1, 2, 3, 5, 8, 13, 20. you’ll get the higher scoring, like 3. . The. . 2. Team's composition should remain stable for a sufficiently long. Fibonacci scale: numbers from the Fibonacci. This sequence, known as the Fibonacci sequence, is utilized as a scoring scale in Fibonacci agile estimation. All include a Question card and a Pass card. Many simplify the numbers to “1, 2, 3, 5, 8, 13, 20, 40, and 100. For instance, the difference between 3 and 5 is 2, while the difference between 5 and 8 is 3. Whereas it’s almost impossible to estimate a User Story in hours without the defined. Story Points specify an unknown time range. Complex tasks are assigned more Agile story. In terms of sizing, story points can range from extra small to extra large, but mostly commonly used is the Fibonacci series. For example, it is more difficult to estimate accurately a 13 point story than it is to estimate a 2 point story. The smallest tasks are estimated at 1 point and then other tasks are weighed and estimated in accordance with that task. Mathematicians have studied the golden ratio's properties since antiquity. The idea here is the ability to draw comparison between the. A 5 is going to be bigger than a 3 but smaller than an 8. Many simplify the numbers to “1, 2, 3, 5, 8, 13, 20, 40, and 100. 5, 1, 2, 3, 5, 8, 13, 20, 40, 100; It’s not black and white. The product owner will then bring a user story to the table. Create a project estimation template. This. There are two types of scales used for creating estimation matrices: the linear scale (1,2,3,4,5,6,7…) and Fibonacci sequence numbers (0. Why Story Points With a Fibonacci Sequence Are Better Than Hours. Buckets: 0,1,2,3,4,5,8,13,20,30,50,100, and 200, I would recommend to use fibonacci series and use up tp 21 story points. To find 2, add the two numbers before it (1+1) To get 3, add the two numbers before it (1+2) This set of infinite sums is known as the Fibonacci series or the Fibonacci sequence. The Fibonacci sequence is useful for teams estimating with story points. Story Points are Relative:. In case of Fibonacci series for story pointing, if a team thinks that a story is little bigger than 3 points then it goes to 5, likewise 5 to 8 or 8 to 13. The Fibonacci Sequence is a numbers list that follows a pattern starting with 0. One of the most well-known, best practices of Agile is to split big stories or epics. The fibonacci sequence is used by Scrum teams for story point estimates – 1, 2, 3, 5, 8, 13, 21, and so on. Sequences are helpful because they force your team to focus on the relative size between the numbers, making estimating complex tasks easier. Going over 21 is usually a bad idea. I think the story point estimation is useful precursor to planning. Mathematicians have studied the golden ratio's properties since antiquity. Teams generally estimate in “relative complexity”. The Fibonacci sequence is a great way to estimate story points because it accommodates for the uncertainty that comes with any estimation. However, this modified Fibonacci sequence in Agile estimation world is 1,2,3,5,8,13,20,40…. —representing the Fibonacci sequence in mathematics. The Fibonacci scale is commonly used for story points to address risk and uncertainty. I use script runner plugin quite a lot and you can use the Behaviour module of the plugin to restrict the story points to a certain. Story points- the metrics used in Agile product development. The Story of Phi,. Now comes a tricky bit. The higher the number, the more intricate the story point becomes. This sequence is a series of numbers in which each is the sum of the two. hours debate see Scrum Inc. Total points: 10; Person B has TWO 5 point tickets. 5, 1, 2, 3, 5, 8, 13. At this point the old complexity was zero, so you add 1 and 0 to get your new estimate of 1. Story points are a system for measuring work that accounts for the work’s uncertainty, its complexity, and its quantity. For example, when playing Planning Poker many teams will use a modified Fibonacci sequence of 1, 2, 3, 5, 8, 13, 20, 40 and 100. Nobody knows exactly how many hours you are appointing to a specific issue. You can also calculate a single number in the Fibonacci Sequence, F n, for any value of n up to n = ±500. Ideally, using the Fibonacci series, the story point estimate should be much more obvious to the team, since one story point could be almost 2x the other, and there is less need for disagreement. PO reads out the user story and ask the team members to show their card c. What is the Fibonacci sequence?. Common estimating methods include powers of 2 (1, 2, 4, 8), the Fibonacci sequence (1, 2, 3, 5, 8, etc. 12 Common mistakes made when using Story PointsThe Fibonacci sequence is useful for user story estimation because it reflects the exponential growth of uncertainty and complexity as tasks get larger. In Fibonacci Sequence the sequence starts from 0, 1 and then the next term is always the sum of the previous two terms. Fibonacci sequence is "the old number plus the one before that". 8%, and 100%. This is a video compilation of clips from various sources with The Divine Book: The Absolute CreatorThe uncertainty in the estimation is captured in the Story Point Fibonacci-like sequence itself: 1, 2, 3, 5, 8, 13, 20, 40, 100. The simplest is. 382, . The Fibonacci scale is a series of exponentially increasing numbers used to estimate the effort required to complete a task or implement a user story . Scrum, Fibonacci, Power Of Two and T-Shirt Card Decks; Unlimited Participants; Contact Us. The estimators are then given Agile poker cards with the Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21. Start the estimation. Effort: The second. Is something worth 45. While development teams commonly adopt the Fibonacci series, alternative options also exist. The reason for using the Fibonacci sequence instead of simply doubling each subsequent value is because estimating a task as exactly double the effort as another task is misleadingly precise. Popular estimating methods in an agile development environment include story points, dot voting, a bucket system, affinity mapping, and t-shirt sizing. Here’s an example. The Fibonacci sequence is a series of numbers that is commonly used for Scrum story point estimation. Too big user stories can be broken into smaller user stories. Story point measurement is relative. Actually most of the agile team are estimating following the "modified Fibonacci sequence", that's why Planning poker cards are available mainly with this sequence. Affinity Estimation is a great technique if a project has just started, and have a backlog that. So, I can create 2 sub-tasks with story points 8 and 13. Each unit of work in a project is assigned an appropriate number of story points, which helps the team prioritize the backlog. Though it varies by team, we generally suggest the medium story is one that can be completed in a day or two. One way to clearly define story points is to use the Fibonacci sequence rather than a linear scale. Some teams will use the classic Fibonacci sequence, while others will use the adapted one. What are story points? Six easy steps to estimate work in Agile Whitney Vige December 3rd, 2022 • 8 min read. Combine story points with the Fibonacci sequence. It should also be two-thirds the effort of a. You can start increasing numbers in the series by 60% from the number, 2. Story Points are a metric used in agile project management and programming to estimate the difficulty of implementing a given User Story. It is used to estimate the amount of effort that will be required to complete a given task or implement a user story. According to Scum Inc, even the best experts in the company could not estimate how much time a project would take, including the people who implemented it. Why the Fibonacci Sequence Matters. Determine your story point sequence Next, determine your story point sequence. -Points will mean different things to different teams or organizations. When we estimate using numbers like 1, 2, or 3, we tend to be overly optimistic because we. The term originates from the way T-shirt sizes are indicated in the US. . This, Cohn argues, based on Weber. story-writing criteria. Story points for each work item are calculated as an average of the input from all the team members involved. Teams assign story points to work, relative to work complexity, the amount of work, and risk or uncertainty. Most teams use the Fibonacci sequence to represent agile story points. Agile teams favor the Fibonacci numbering system for estimating. Each story’s size (effort) is estimated relative to the smallest story, which is assigned a size of ‘one. the team will use the story points. 1170, Pisa?—died after 1240), medieval Italian mathematician who wrote Liber abaci (1202; “Book of the Abacus”), the first European work on Indian and Arabian mathematics, which introduced Hindu-Arabic numerals to Europe. Too big user stories are not recommended. In the previous case, B could be a 3 or 5 and there's a clearer idea of how complicated it can be to develop compared to A. Team members will typically gather around to form a circle. The Fibonacci sequence is a series of numbers in which each digit reflects the sum of the two preceding numbers. This allows us to better manage the time expectations of stakeholders for future work. Even a rough approximation of the resources required or the amount of time it’ll take to accomplish a task is helpful when it. The estimators discuss the feature, asking questions of the product owner as needed. g. For example: We have a post it card and assign it a story point 2 and three post it card's size would mean 2*3=6 story points. Estimation is a collaborative process in which teammates discuss the effort of completing an item from. Here at RubyGarage we use Fibonacci sequence numbers. Fibonacci series occurs in nature (Fibonacci number). When it’s time to provide an estimate for each Story, the Team Lead will ask the team to collectively hold up the card that they. Some plants branch in such a way that they always have a Fibonacci number of growing points. Continuing in this fashion you obtain the following Fibonacci Sequence:" I don't understand. you get it. A story which is, lets say, bigger than a 5-points story will remain big, so the team should not spend time in figuring out if it is a 10 or 11. Fibonacci Sequence. Teams generally estimate in “relative complexity”. One of the most popular scales for estimating story points is the Fibonacci sequence Leveraging the Fibonacci Series for Agile Work Sizing T he Fibonacci series is a mathematical sequence of numbers that starts with 0 and 1, and each subsequent number is the sum of the previous two numbers. The Fibonacci Sequence technique is ideal when estimating large and complex tasks, and there is a need to prevent estimates from being too close to one another. Story Points specify an unknown time range. We would like to show you a description here but the site won’t allow us. independentDuring planning, teams use a User Story Point scale (Fibonacci or similar) to measure the amount of effort for each User Story. It can be used in an completely automated manner, i. 3. The traditional Fibonacci series is 1, 2, 3, 5, 8, 13, 21, 34, 55 and so on. Let the team discuss final thoughts or questions about the story. The Pros and Cons of Using Story Points in Sprint Planning. Too big user stories can be broken into smaller user stories. His father's job was to represent the merchants of the Republic of Pisa who were trading in Bugia, later called Bougie and now called Bejaia. The Fibonacci sequence consists of numbers that each number is the sum of. Taking the seriesTake a video course from Mountain Goat Software: can read the original. Story points are used to represent the size, complexity, and effort needed for completing or implementing a user story. For estimating the time it takes to complete tasks, you want a scale that is made of integers. Fibonacci sequence is used a lot while estimating with Story Points. Fibonacci for User Stories – How & Why to Use Relative Story Points James Davis 9 minute read Imagine you’ve scheduled an Uber from the airport but instead of providing. As you understand from the above sequence of. It’s Composed Of Integers. When we estimate using numbers like 1, 2, or 3, we tend to be overly optimistic because we round down the true effort required. The sequence is closely related to “the golden ratio, “ which artists use to create works with beauty, balance, and harmony. When you assign values to your story points, place them in the corresponding row. Now we introduced customizable story points sequences. One of the most well-known, best practices of Agile is to split big stories or epics. Fibonacci numbers also appear in plants and flowers. The two floating-point values would be encoded as fixed-point values. The guideline for applying story points is to estimate not in terms of hours but in terms of abstracts units. It is the ratio of a regular pentagon's diagonal to its side and thus appears in the construction of the dodecahedron and. A. Story Points represent. What is Fibonacci Series? Fibonacci Series is a pattern of numbers where each number results from adding the last two consecutive numbers. Learn more about points, why they’re better than hours, and also some pitfalls to be aware of. There is a natural. Story Point 6 falls between fibonacci series number 5 and 8 with 5 being the closer number and hence the storypoint would be 5. Story points account. Fibonacci sequence is used a lot while estimating with Story Points. A typical question most of the newbies introduced to planning poker come up with is — “after all if we are using numbers for story pointing, why just not use the normal number sequence of 0, 1. Agile Mentors Community Gets Real about Story Points and Fibonacci. Levels are calculated using the high and low points of the chart. And for more on leading an. 1, 2, 3, 5, 8, 13, 21, 34, 55… This sequence helps give a sense of scale. Story points are estimated using one of the fair method like planning poker or affinity estimation. Scrum is not a one-size-fits-all solution, a silver bullet or a complete. One of the most well-known, best practices of Agile is to split big stories or epics. 2. The Story Points Fibonacci scale assigns numbers to Story points: Story point = Story Size – Story Complexity. Choose reference stories. In his article on why Story Points are better than hours he puts it like this: Story points are therefore faster, better, and cheaper than hours and the highest performing teams completely abandon any hourly estimation as they view it as waste that just slows them down. Story points != time is good because it automatically accounts for “other things” that use up time within a sprint, beyond your -1day example for the ceremonies. e. Create a custom estimation scale: Use letters, numbers or even emoji to make a scale that works for you. The size (effort) of each story is estimated relative to the smallest story, which is assigned a size of ‘one. One-by-one, have the team estimate each user story using the standard fibonacci sequence scale of 1, 2, 3, 5, and 8 (discard any user story larger than an 8). Agile teams often use the Fibonacci sequence to estimate the “size” of tasks and user stories for their upcoming sprint. 1. Natural Rhythm. This point system is popular because there is about a 40% difference between each number in a Fibonacci sequence. Play story points planning poker. Story points- the metrics used in Agile product development. With their help, it looks much easier to decide if an item equals 3 story points or 5 story points. Too big user stories are not recommended. Story points are the estimates of the effort it will take to build all the features needed to create the experience described in the user story. Agile uses the Fibonacci sequence to assign numbers to story points. ) or some other relative scale. If that's the case then you can add a check using a plugin. Fibonacci sequence numbers offer a simple scale for estimating agile story points. As we go further out in the Fibonacci sequence, the ratios of successive Fibonacci numbers approaches the fixed limiting value of 1. So the sequence looks something like this. Planning Poker – Agile Estimation Method. The only issue with this proposal is that it returns a value for numbers that are not in the Fibonacci sequence, but the original problem specifically stated that the input to the function would be Fib(n), which implies that only valid Fibonacci numbers would be used. 3 steps to estimating story points. Fibonacci, paired with User Stories being high-level estimations, gives a more approximate idea (educated guess) of how complex a feature is going to be. The mathematical ideas the Fibonacci sequence leads to, such as the golden ratio, spirals and self- similar curves, have long been appreciated for their charm and beauty, but no one can really explain why they are echoed so clearly in the world of art and nature. Fibonacci was born in Italy but was educated in North Africa where his father, Guilielmo, held a diplomatic post. 1. Why use the Fibonacci sequence or Fibonacci series for Story Points is a frequently asked question in an agile scrum team. -Points will mean different things to different teams or organizations. Apply the Fibonacci sequence to the T-shirt sizes. In the depths of the 2008 recession, the index hit its lowest point in 2009 at 666 points. Note. The uncertainty in the estimation is captured in the Story Point Fibonacci-like sequence itself: 1, 2, 3, 5, 8, 13, 20, 40, 100. Note that Junior’s number of hours per point is 4 times that of Superstar. 5, 1, 2, 3, 5, 8, 13, 20, 40, 100; It’s not black and white. Story Points don’t follow the Fibonacci sequence strictly. Story points are relative, without a connection to any specific unit of measure. This makes the math easy as you simply divide the points by 2 and you get the number of days it will likely take to complete the story. It helps improve team members’ understanding of the project requirements. Each card has a Fibonacci Number on it — 1, 2, 3, 5, 8, 13, 21. And this is just one instance. When we use the Fibonacci series in estimating these gaps. These values most commonly represent story points. It highlights the difference and gives better estimates. Question: Rubric Name: Story Pointing Rubric Criteria All (five or more) user stories have a story point and a value point All (five or more) user stories have a value in the Fibonacci sequence Key Points to Remember Story points simply show the relative size, complexity, and risk of a story. It aids in estimating the effort required for agile development tasks. At first, all the team can estimate using their intuition and first impressions of the task. Los puntos de historia se utilizan para representar el tamaño, la complejidad y el esfuerzo necesarios para completar o implementar una historia de usuario. In agile software development, particularly in Scrum, teams usually use story points to give a relative size to their stories. While you could use a different scale for estimating tasks, such as 0-1 or shirt sizes (XS, S, M, L, XL), the Fibonacci scale is a better choice for 5 reasons: 1. Estimation is usually done by assigning Fibonacci Story Points to each story. This gives a series of numbers that looks like the following. Fibonacci Sequence (1, 2, 3, 5, 8, 13, 21) for EvaluationIn mathematical terms, the sequence Fn of Fibonacci numbers is defined by the recurrence relation: with seed values and and . The Fibonacci sequence of numbers “F n ” is defined using the recursive relation with the seed values F 0 =0 and F 1 =1: Fn = Fn-1+Fn-2. Because of this, it requires some adaptations: Fibonacci — 0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144, etc; Story Points — 0. The reason for using the Fibonacci sequence is to reflect the inherent uncertainty in estimating larger items. Story points != time is good because it automatically accounts for “other things” that use up time within a sprint, beyond your -1day example for the ceremonies. Affinity Estimation is a great technique if a project has just started, and have a backlog that. Here’s an example. Rather than using a number of planning pokers, here, Items are classified into t-shirt sizes: XS, S, M, L, XL. seventh term = 5th term + 6th term = 3+5 = 8. Affinity Estimation is a technique many agile teams use too quickly and easily estimate a large number of user stories in story points. You create a Fibonacci sequence by adding the two preceding numbers. , 8),then fix it against the story point d. , are all close to 1. (typically in the Fibonacci sequence) to assign each user story. Rather than using a number of planning pokers, here, Items are classified into t-shirt sizes: XS, S, M, L, XL. The formula to arrive at a Fibonacci sequence is: Xn = Xn-1 + Xn-2. Affinity Estimation is a technique many agile teams use too quickly and easily estimate a large number of user stories in story points. There are hidden depths there. His father's job was to represent the merchants of the Republic of Pisa who were trading in Bugia, later called Bougie and now called Bejaia. Such sizing can be done in time or story points – a measurement unique to agile, which is based on a task’s expected complexity, the amount of work required, and risk or uncertainty. . Chaque story point se voit attribuer un nombre sur la suite de Fibonacci. Most development teams use the. It can be calculated in different ways for different organizations. 規劃會議怎麼進行Story Point評分？ 說了分數的用意後，接著就要來說說，到底規劃會議要怎麼評出Story Point。以及它的原則與細節又是什麼。Your team has opted to use Story Points, which are based on the Fibonacci sequence of numbers (1, 2, 3, 5, 8, 13, 21, etc. By story pointing with Fibonacci, teams can provide a clearer, more accurate estimation scale. 6180339887498948482. Story points vs. The Fibonacci sequence is useful for teams estimating with story points. Read 10 Reasons To Use Fibonacci Sequence For Story Points by agilebin on Issuu and browse thousands of other publications on our platform. The ratio between the numbers in the Fibonacci sequence (1. FAQ: 1. This sequence of points provides a much better jumping-off point. The Fibonacci Sequence is a numbers list that follows a pattern starting with 0. This sequence will be slightly modified. The bigger the user story, the harder it is. It can be used in almost any project management software that supports estimation, such as Jira or Asana. The choice of a specific number from this sequence reflects the amount of uncertainty. Story Points represent the complexity, uncertainty, and effort (CUE) needed for completing or implementing each work item. When done, everyone reveals their estimates and discusses them until everyone agrees about each item. Start by deciding on your sizes. When estimating story points, most teams use a modified Fibonacci sequence that starts at 1 and ends with 20. So when Scrum teams come up with a story point estimate (usually via planning poker ), they use FIbonacci numbers for those estimates. The T-Shirt size cards are for relative sizing using T-Shirt sizes (XS, S, M, L, XL). Fibonacci Sequence. In the main() function, we call the function fib() for nth number in the Fibonacci Series. Starting at 0 and 1, the first 10 numbers of the sequence. The Fibonacci sequence is used because it is a non-linear sequence, which means that the difference between two consecutive numbers increases as the numbers. Retracements are created when the distance between two points on a stock chart. Accurate enough to plan Sprints ahead. Start h. For example: Add a product to a drop-down menu is 1 story point. This enables you to intuitively differentiate the Fibonacci numbers as different magnitudes. You can start estimate story point sizes with effort or time as your base, but your team should agree on a consistent baseline and expand from there. One of the characteristics of the Fibonacci series is that the gaps between the values increases with their size. that generation. The chambers provide buoyancy in the water. The scale is based upon the Fibonacci sequence and is a series of numbers where each number is the sum of the two preceding numbers. Story points are an estimate of the overall effort. It can be used in almost. The Fibonacci series is a mathematical sequence where each number is the sum of the previous two, with the scale being 1, 2, 3, 5, 8…and as a best practice, usually work that is an 8 or beyond should be. Fibonacci, (born c. Let’s understand each of these in detail. When we observe the geometry of plants, it’s easy to recognize recurring patterns in nature. In order to capture these elements of complexity and uncertainty, story points are estimated using the Fibonacci number sequence. They are non-linearFibonacci numbers are non-linear in nature, which reduces the. In simple terms, Scrum Epic in Agile Methodology is a big chunk of work that can be divided into smaller. Fibonacci sequence up to 13 as maximum is enough and most of the Planning Poker cards are up to 13. 2. For example, a. Why do team's use fibonacci series on Planning Poker cards?Apeksha Patel [a Certified Scrum Trainer from Scrum Alli. The 13-point card should be used for any story the team estimates larger than 8 and no larger than 13.