Other estimation methods like Planning Poker or Bucket System are effective methods of establishing consensus in small projects. They serve as units of measurement for. What we have listed above. Notes: The above story point translation to the hour is not exactly equal; it is an equivalent comparison. The benefit of Fibonacci is that each number is roughly 60% greater than the previous one (with the obvious exception of 1 and 2, of. 's webinar on the topic. In the non-linear series such as Fibonacci series, numbers are ordered in a range of values. Fibonacci sequence (commonly used for story points) T-shirt sizes (Note: Keep in mind that the platform calculates the cumulative size of work items inside initiatives/projects. It explains the rationale for Cohn’s suggestion of a modified sequence that has wider intervals but grows at a consistent rate of about 60%. What Is the Fibonacci Sequence? It's a sequence of numbers: 0, 1, 1, 2, 3, 5, 8, 13, 21, 34, and so on, and so on. Often referred to as a "story point". Once you get scored the easiest story, find the mid-size one and run the same procedure. The resulting number sequence, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55 (Fibonacci himself omitted the first term), in which each number is the sum of the two preceding numbers, is the first recursive number sequence (in which the relation between two or more successive terms can be expressed by a formula) known in Europe. "We're targeting 6 story points, and will probably deliver between 3 to 8 points this Sprint. 5, 1, 2, 3, 5, 8, 13. Start the estimation. The Fibonacci sequence is one of the most famous mathematics formulas adapted for various practice areas. Story Points don’t follow the Fibonacci sequence strictly. Fibonacci scale: numbers from the Fibonacci series like 1, 2, 3, 5, 8, and so on; For simplicity’s sake, most Agile teams tend to pick the Fibonacci series for their story points estimation. . Use one of three default scales for estimating Story Points: Fibonacci sequence, 5 fingers and t-shirt sizes. Story points are used to help organize a project backlog. Fibonacci sequence is used a lot while estimating with Story Points. , 1+1=2, and so on. Apply the Fibonacci sequence to the T-shirt sizes. The Fibonacci sequence is one popular scoring scale for estimating agile story points. ” The spacing between the numbers becomes further apart as the story point values get higher. if all the cards are same (for e. Using the Fibonacci sequence for agile story point estimation. 786 retracement levels. Story points also provide a metric known as velocity, which is the number of points implemented per sprint. If the numbers are different, all the. 382, . Choose reference stories. Planning poker, also called Scrum poker, is a consensus-based, gamified technique for estimating, mostly used for timeboxing in Agile principles. Lastly, we have T-shirt sizes. Read more about different Agile estimation techniques such as the Fibonacci sequence. Total points: 10; On paper and from management’s perspective, both person A and B have the same amount of work, 10 points each. 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. These Planning Poker cards display values like 1, 2, 3, 5, 8, 13, 20, 40 and 100 (the modified Fibonacci sequence). Before you introduce t-shirt sizing to your team, decide on the sizes you want to use. 13 = 34 Story Points. So, I can create 2 sub-tasks with story points 8 and 13. Story Points specify an unknown time range. 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. Fibonacci Sequence and Phi in Nature. A clear Definition of Done helps the team better understand how much effort it will take to complete an item. In this estimation technique, the Fibonacci scale is then inserted into a table where you can assign any user story to a value. 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. The difference is huge, and we’re more likely to perceive a story with 89 story points as much more complex than one with 10 points. 2. Use Fibonacci or a modified Fibonacci series for estimates. The recursive relation part is F n = F. Too big user stories are not recommended. Of course, if the uncertainty is too great to estimate, you may use the ‘?’ card. 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. 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. These are a sequence of numbers where each successive number is the sum of. The team selects an item from the product backlog, discusses it briefly, and then each team member holds up a card with a number corresponding to their estimate. I've used story points using a Fibonacci scale and have tried 'poker cards' to get consensus over complexity. This enables you to intuitively differentiate the Fibonacci numbers as different magnitudes. ’ A modified Fibonacci sequence (1, 2, 3, 5, 8, 13, 20, 40, 100) [2] is applied that reflects the inherent uncertainty in estimating, especially large. Any number in the sequence is the sum of the two that came immediately before it. Reference story When a team is new to estimations, it’s good to identify some reference stories. As you understand from the above sequence of. Simply put, the Fibonacci Sequence is a set of numbers where, after 0 and 1, every number is the sum of the two previous numbers. Does the use of the Fibonacci Series - in Agile Estimating and Planning - lead to more ACCURATE estimates?Download your FREE CHEAT SHEET: foregoing justifies the use of the Fibonacci sequence for story point estimation in Agile. In Custom sequence you can add any sequence if you want. Let’s understand each of these in detail. An interesting corollary of this series is that there is a relationship between each filial total. The. Story Points are Relative:. You create a Fibonacci sequence by adding the two preceding numbers. The fibonacci sequence is where each number is the sum of the two before it: 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144,. 5 = 13 Story Points. Story Points specify an unknown time range. T-shirt Sizing is one of the Story points sizing technique to estimate user story usually used in agile projects. 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. Make sure the whole team has full awareness of the story and they are ready to estimate. To some degree, using the Fibonacci sequence in assigning story points will account for uncertainty in development times, but it doesn’t exactly allow for a direct conversion. The main goal of relative estimation is not to focus on Jira story points (or any other units) and their values alone but to help determine and adapt the product plan and vision. The choice of a specific number from this sequence reflects the. 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. But that’s the same thing as equating story points to hours, which is a huge no-no. This. Fibonacci Sequence in maths is a special sequence of mathematics that has some special patterns and is widely used in explaining various mathematical sequences. It starts with 0 and 1, and each subsequent number is. While estimating the story points using the Fibonacci sequence numbers, a matrix with rows for each. There are several ways of estimating story points, and the two most common ways are by using the Fibonacci sequence, and by using the planning Poker method. For estimating the. Story point estimation is the process of assigning story points to a product backlog item or a user story. ” The story changes for higher-numbered Somos sequences. It's a relative Estimation Technique. . 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. Estimation is a collaborative process in which teammates discuss the effort of completing an item from. Story point estimation is a key component of agile project management. 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. T-shirt Sizing is one of the Story points sizing technique to estimate user story usually used in agile projects. Pick a story point estimation baseline. As I mentioned before, complexity doesn’t grow on a linear scale. The Fibonacci Story Point system has been around for a while now, but the recent adoption of agile practices has made it popular again. It encourages breaking down work into smaller chunks (preferably achievable within a sprint). The cards are revealed, and the estimates are then discussed. For example, you might have a collection of cards labeled 2, 2,. One of the most well-known, best practices of Agile is to split big stories or epics. This allows us to better manage the time expectations of stakeholders for future work. Team members will typically gather around to form a circle. In the main() function, we call the function fib() for nth number in the Fibonacci Series. Disadvantage: It might. Why do team's use fibonacci series on Planning Poker cards?Apeksha Patel [a Certified Scrum Trainer from Scrum Alli. 2%, 50%, 61. La suite de Fibonacci agile donne aux équipes une façon plus réaliste d’aborder les estimations à l’aide de story points. A human brain can easily map things based on sizes. One common methodology for employing agile story points is to assign values to backlog items using the Fibonacci sequence — 1, 2, 3, 5, 8, 13, 21. Fibonacci sequence up to 13 as maximum is enough and most of the Planning Poker cards. I think most teams use fibonacci numbers. Typically, numbers from the Fibonacci sequence (1, 2, 3, 5, 8,…) are used for this purpose. 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. Story points- the metrics used in Agile product development. With the use of the Fibonacci Sequence formula, we can easily calculate the 7th term of the Fibonacci sequence which is the sum of the 5th and 6th terms. Each number is the sum of the two preceding numbers. Agile story point estimation helps team members see a product’s priorities and the effort each item needs. This gives a series of numbers that looks like the following. No one should complain about using the higher number and an equal split usually takes a long. 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. Sometimes, cards with 0, ½, ∞, ?, and. 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. Story points give more accurate. 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. 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. If the numbers are different, all the. Although 20,. Story points are relative, without a connection to any specific unit of measure. Make a row for each number in the Fibonacci sequence. 2. 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. Fibonacci was born in Italy but was educated in North Africa where his father, Guilielmo, held a diplomatic post. When we observe the geometry of plants, it’s easy to recognize recurring patterns in nature. Note. So that’s as high as you’re likely to see. Flowers often have a Fibonacci number of petals, daisies can have 34, 55 or even as many as 89 petals!Básicamente, la escala de Fibonacci desde la perspectiva Agile les ofrece a los equipos una forma más realista de abordar las estimaciones mediante puntos de historia. V. Story points are a system for measuring work that accounts for the work’s uncertainty, its complexity, and its quantity. For example, it is more difficult to estimate accurately a 13 point story than it is to estimate a 2 point story. ). The Story of Phi,. N. Assignment Take the user stories that you created. Though not required, adding values to the T-shirt sizes used in the fruit salad game helps us estimate team velocity over time. The Fibonacci sequence contains numbers that exhibit exponential growth, where each number is the sum of the two previous ones. This allows us to better manage the time expectations of stakeholders for future work. 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. Say I assigned 21 story points to a task. In this sequence, each number is the sum of the previous two in the series. That’s the magic of the Fibonacci sequence, it’s not just the numbers, but the spaces between them, that help you size tasks during your estimation. The Fibonacci sequence is useful for teams estimating with story points. The Fibonacci spiral is created using a series of quarter circles, with radii that correspond to the Fibonacci numbers as shown in below image: The resulting spiral is known as a “ Fibonacci spiral ” or a “ Golden Spiral ” It is often associated with the Golden Ratio , which is an irrational number approximately equal to 1. The Fibonacci sequence is a series of numbers in which each digit reflects the sum of the two preceding numbers. Now we'll go through the algorithm for the Fibonacci Series using recursion in Java. Popular estimating methods in an agile development environment include story points, dot voting, a bucket system, affinity mapping, and t-shirt sizing. Since then it has generally been on a longterm. Story points- the metrics used in Agile product development. Then. The two floating-point values would be encoded as fixed-point values. This sequence is the sum of the previous two numbers in the series. The Fibonacci sequence consists of numbers that each number is the sum of. Story Point Estimation in AgileIntroduction. The Fibonacci sequence is a mathematical series of numbers that was introduced in the 13th century and used to explain certain formative aspects of nature, such as the branching of trees. Each story’s size (effort) is estimated relative to the smallest story, which is assigned a size of ‘one. That’s why Agile teams have come to use the Fibonacci scale for business because it’s easier to evaluate task efforts when you don’t have many numbers close to each other to choose from, as opposed to an even. The sprint sizing is in the form of story points based on a task’s. 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. It is also very helpful to have a reference user story that all the members of the scrum team have a good understanding of and assign it an estimate. Story point estimation is the process of assigning story points to a product backlog item or a user story. Natural Rhythm. Then take a hardest story and get a third scoring,. In planning poker, members of the group make estimates by playing numbered cards face-down to the table, instead of speaking them aloud. Fibonacci story points and Planning Poker Typically,. The 4th number is the addition of the 2nd and 3rd number, i. -1 story point for your team might not equal the same amount of effort involved in 1 story point for another team. Be. ’ A modified. This measuring tool is developed in a very interesting sequence. You can also calculate a single number in the Fibonacci Sequence, F n, for any value of n up to n = ±500. Story points are used to represent the size, complexity, and effort needed for completing or implementing a user story. It is a number that informs the team about the difficulty level of the User Story. If that's the case then you can add a check using a plugin. Multiply that by whatever your charge rate is, and voila, you have your time and cost estimation. Story points in Scrum often use a standard or modified Fibonacci sequence to estimate the level of effort for stories based on some agreed-upon baseline such as a "typical" one-point story. 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. If you come up with story points of 13, that means you are in the range over 8 and under 21. 1. ) is frequently called the golden ratio or golden number. Why is the Fibonacci sequence used in planning poker? To play planning poker, you start with a deck of cards, but not your standard playing cards. 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. Planning poker is an Agile estimation technique that helps teams to assign values to story points. Story Points in Fibonacci Scale. 8%, and 100%. Moreover, the Fibonacci sequence has a varying distance between Story Points. Agile Story Points: Modified Fibonacci Sequence Final thoughts What is the modified Fibonacci Sequence? In this post, we’ll focus on the modified Fibonacci. One pitfall to avoid is trying to convert story points back into hour. . ) or some other relative scale. During story refinemnt meeting, it is critical to slice the stories, small enough, to fit into the sprint. As the story size increases, it becomes difficult to precisely estimate. When done, everyone reveals their estimates and discusses them until everyone agrees about each item. Story points in Agile help you and your team optimize workflows for efficiency and business value. Some plants branch in such a way that they always have a Fibonacci number of growing points. (S, M, L, XL), but you can also use the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, and so on). This approach proves highly valuable as it simplifies the process by restricting the number of values in the sequence, eliminating the need for extensive. g. Story point estimation is a technique used in Agile project management to replace task estimation in time or money. They can then begin working to estimate stories in “relation” to the first story. . Here at RubyGarage we use Fibonacci sequence numbers. But before you go, remember that story point estimates are not a perfect science, and there will always be some. We do this because people are really good at comparing sizes, but not at. That is, 1, 2, 3, 5, 8, 13, 20. Here’s an example. 8 = 21 Story Points. We would like to show you a description here but the site won’t allow us. 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. 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 two floating-point values would be encoded as fixed-point values. By this point, you should have a series of cards on display around the table representing the effort assessment of all parties. Finally, a connection between the Fibonacci-based story point system and the golden ratio is derived. Fibonacci numbers are used when doing story point estimation. In Relative estimations, if we are using Story points, then we mostly use modified Fibonacci series numbers. 1. Story Points represent the complexity, uncertainty, and effort (CUE) needed for completing or implementing each work item. [ F_{0} = 0,quad F_{1} = F_{2} = 1, ] andStep 2: Story Point Estimation Matrix. Learn how Story Points can help you estimate and plan your Agile projects more accurately and quickly. But there is no rule about this. So user story points ideally define the complexity and efforts involved to design, develop and deliver a product to the main line (production environment). Although Mike didn't state it explicitly in the book, at some point someone recognized that this was almost like the Fibonacci series and thus was born the "modified Fibonacci" scale for story. Some teams will use the classic Fibonacci sequence, while others will use the. This point system is popular because there is about a 40% difference between each number in a Fibonacci sequence. 0 – Very quick to deliver and no complexity. S. consecutive sizes might be 5 and 8 if you are using the Fibonacci sequence for sizing (1, 2, 3, 5, 8, 13). Myth 9: Story Points are Required in Scrum. Story points are estimated using one of the fair method like planning poker or affinity estimation. Determine the sizing type. What matters are the relative values. Fibonacci series do not have 4. Selecting from a specific Fibonacci-like sequence of Story Points allows you to capture. Therefore 1 point takes 8 hours. You're saying that "the old complexity plus the complexity you just discovered" is the same. A Story Points Scale encompasses a spectrum of potential values that agile teams use to gauge the size of a user story. You can use two scales to determine your story points: a linear scale or Fibonacci sequence. In story points estimations, the team doesn’t estimate the exact time needed to implement the functionality. Why use Fibonacci for story points? There are two types of scales used to create estimation matrices: the linear. Ceux-ci sont utilisés pour représenter la taille, la complexité et l’effort nécessaire pour réaliser ou mettre en œuvre une user story. See moreWhile Story Points include effort, like absolute estimating, it further accommodates the expected ambiguity of Agile requirements. Story points are relative, without a connection to any specific unit of measure. Now we introduced customizable story points sequences. The Pros and Cons of Using Story Points in Sprint Planning. The Fibonacci series graciously defines the complex nature of building the product or delivering the right product. You may assign point values using consecutive whole numbers or the Fibonacci sequence, which is more popular because it leaves room for approximation. We do this because people are really good at comparing sizes, but not at. 3 steps to estimating story points. Fibonacci (/ ˌ f ɪ b ə ˈ n ɑː tʃ i /; also US: / ˌ f iː b-/, Italian: [fiboˈnattʃi]; c. The Fibonacci Sequence is a numbers list that follows a pattern starting with 0. 6180339887498948482. A story point is an attempt to create something like a kilometer, so that we can use a simple math to predict arrival times for example (Distance = rate * time) Unlike distance there is no formula to calculate Story Point, but you have 2 different estimates. Continuing in this fashion you obtain the following Fibonacci Sequence:" I don't understand. Avoid using too many sizes so team members aren’t confused. g. Essentially, each number in the Fibonacci scale corresponds to the complexity of the task. Accurate enough to plan Sprints ahead. To do this, we use the Fibonacci sequence. It has its own default sequences; they are Prime Numbers, Fibonacci, Modified Fibonacci and Custom sequence. The term originates from the way T-shirt sizes are indicated in the US. Perfect for high-level estimation. Why agile teams use Fibonacci sequence for estimating Corrado De Sanctis 3y. The first 18 terms of Somos-8 are integers, but the 19th term is a fraction. Each estimation is modified just for the sake of easiness of use of 20,40,80 and 100. Using story points, a team could, for instance, estimate using a combination of risk, uncertainty, complexity and effort for the entire team. 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. , are all close to 1. 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. The implications of this connection to our understanding of effort in stories are explained. Uncertainty is captured in the Fibonacci-like. It helps improve team members’ understanding of the project requirements. The question often arises: why adopt the Fibonacci sequence for story points? This article delves into the 10 compelling reasons behind choosing the Fibonacci sequ. Assign a number of fingers to each number. These values represent each person’s estimation of the story points. Chaque story point se voit attribuer un nombre sur la suite de Fibonacci. The Fibonacci sequence is a series of numbers with each number being the sum of the two previous. Fibonacci series occurs in nature (Fibonacci number). Here, the sequence is defined using two different parts, such as kick-off and recursive relation. Fibonacci Sequence Formula. It is the ratio of a regular pentagon's diagonal to its side and thus appears in the construction of the dodecahedron and. The. 5 = 13 Story Points. ) is frequently called the golden ratio or golden number. Most teams use the Fibonacci sequence to represent agile story points. It’s not uncommon to see. I think story points for a task is in fibonacci so that it can be decomposed into two (or more) smaller sub-tasks with appropriate story point. The Nth Fibonacci Number can be found using the recurrence relation shown above: if n = 0, then return 0. Agile teams discuss upcoming tasks and assign points to each one using the Fibonacci scale to prioritize tasks to be included in the next sprint. Agile Story Points: Modified Fibonacci Sequence. ) or some other relative scale. Even a rough approximation of the resources required or the amount of time it’ll take to accomplish a task is helpful when it. To do this, we use the Fibonacci sequence. In simple terms, Scrum Epic in Agile Methodology is a big chunk of work that can be divided into smaller. Fibonacci sequence and Planning Poker Planning Poker uses of the Fibonacci sequence to assign a point value to a feature or user story. Now comes a tricky bit. Fibonacci sequence up to 13 as maximum is enough and most of the Planning Poker cards. And for more on leading an. . Fibonacci Sequence for Story Point Estimation The fibonacci sequence is a popular scoring scale within some teams. If the story received 5 points on a Fibonacci scale, then you would compare it to stories your team estimated for 3 and 8 points, respectively. Story Points Use a Relative Scale. Story Points Use a Relative Scale. Many simplify the numbers to “1, 2, 3, 5, 8, 13, 20, 40, and 100. Ceux-ci sont utilisés pour représenter la taille, la complexité et l’effort nécessaire pour réaliser ou mettre en œuvre une user story. 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. Here at RubyGarage we use Fibonacci sequence numbers. Since then it has generally been on a longterm. Determine your story point sequence Next, determine your story point sequence. Are there real-life examples? The Fibonacci sequence is a series of numbers in which each number is the sum of the two that precede it. Consider an example : If the team wants to map the sizes to a number system (to calculate velocity or the number of points they can close per Sprint), they simply replace small with 1 and medium with 2 and so on. Read 10 Reasons To Use Fibonacci Sequence For Story Points by agilebin on Issuu and browse thousands of other publications on our platform. This starts with 0 and 1. this approach, the team starts with a deck of cards, each with a number —1, 2, 3, 5, 8, 13, etc. Agilists around the world have been using the modified Fibonacci sequence to remove the painstakingly slow precision out of estimating. When we estimate using numbers like 1, 2, or 3, we tend to be overly optimistic because we round down the true effort required. Little is known about. If a user story is bigger than 3 then it is a 5. Giving ‘2’ provides you the room to give a smaller story ‘1’ if discovered at a later stage. Fibonacci Sequence and Phi in Nature. The Fibonacci series also better represents the fact that uncertainty grows proportionally with the size of the story. 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. The implications of this connection to our understanding of effort in stories are. Traditional estimation is a different ballgame and uses methods that follow ‘bottom-up’ estimating. natoric, and Fibonacci-based scales of story points. Here’s an example. In terms of sizing, story points can range from extra small to extra large, but mostly commonly used is the Fibonacci series. In Fibonacci Sequence the sequence starts from 0, 1 and then the next term is always the sum of the previous two terms. 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. They are a number that the Developers on the Scrum Team come up with and agree on during the Backlog Refinement or Sprint Planning event. With such a sequence, you could more easily assign story points to tasks. independentDuring planning, teams use a User Story Point scale (Fibonacci or similar) to measure the amount of effort for each User Story. 6180339887498948482. Story points are units of measurement to estimate the effort needed to complete items in the product backlog. The Scrum Master, Product Owner, and the development team participate in Planning Poker activity. 2 = 4 Story Points. The estimators are then given Agile poker cards with the Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21. The Pros and Cons of Using Story Points in Sprint Planning. Apply the Fibonacci sequence to the T-shirt sizes. The first 2 numbers start with 0 and 1, and the third number in the sequence is 0+1=1.