[{"data":1,"prerenderedAt":768},["ShallowReactive",2],{"blog-en-sheepherding-story-points":3,"blog-related-en-sheepherding-story-points":189,"blog-chapter-en-sheepherding-story-points":606},{"id":4,"title":5,"author":6,"body":7,"dateModified":162,"datePublished":163,"description":164,"extension":165,"heading":166,"image":167,"imageAlt":16,"keywords":168,"locale":173,"meta":174,"navigation":175,"path":176,"reviewed":175,"seo":177,"sitemap":178,"slug":186,"stem":187,"translationKey":186,"__hash__":188},"blog\u002Fblog\u002Fen\u002Fsheepherding-story-points.md","Sheepherding story points: anchoring in planning poker | AELBOX","AELBOX",{"type":8,"value":9,"toc":150},"minimark",[10,22,25,30,38,48,53,58,61,64,71,75,78,82,85,90,94,98,101,108,112,116,119,124,128,132,144,147],[11,12,13],"p",{},[14,15],"img",{"alt":16,"height":17,"loading":18,"src":19,"width":20,"fetchPriority":21},"A flock of sheep and planning poker cards on a coffee table",960,"eager","\u002Fblog\u002Fsheepherding-story-points\u002Fcoffee-table-sheep.webp",1600,"high",[11,23,24],{},"Story point estimation is often neglected or done in chat rooms and open meetings where everyone can see or hear every vote. Knowing how others voted distorts the outcome and produces inaccurate estimates. Repeated inaccurate estimates lead to flawed plans and delayed or canceled deliveries. Here is what happens in an open vote.",[26,27,29],"h2",{"id":28},"the-characters-in-voting","The characters in voting",[11,31,32,33,37],{},"Several characters show up in an open estimation vote. The estimate depends on who goes first, and it is usually far from honest. Why does the order matter so much in an open vote? Because of the ",[34,35,36],"strong",{},"sheep effect",": the anchoring bias that makes other team members copy the first estimate.",[11,39,40],{},[14,41],{"alt":42,"height":43,"loading":44,"src":45,"width":46,"decoding":47},"The sheep effect",746,"lazy","\u002Fblog\u002Fsheepherding-story-points\u002Fsheep-1.png",1779,"async",[11,49,50],{},[51,52,42],"em",{},[54,55,57],"h3",{"id":56},"the-overconfident-voter","The overconfident voter",[11,59,60],{},"Every team has at least one member who believes they know the system best. They usually vote first, because the answers seem obvious to them. They often overlook details that can derail the estimate. Those details can be uncovered in advance, but only if someone prompts a discussion. That cannot happen in an open vote.",[11,62,63],{},"This person usually votes lower than the honest estimate. Perhaps only they could finish the story that quickly, and only with luck.",[11,65,66],{},[14,67],{"alt":57,"height":68,"loading":44,"src":69,"width":70,"decoding":47},290,"\u002Fblog\u002Fsheepherding-story-points\u002Fimg7.png",600,[11,72,73],{},[51,74,57],{},[11,76,77],{},"Everyone else follows, so the task looks easy and doable by anyone in the allotted time. In practice, someone else usually ends up doing it.",[54,79,81],{"id":80},"the-quiet-voter","The quiet voter",[11,83,84],{},"There is usually more than one quiet voter, and they are afraid to vote first. They wait for someone else to vote so they can copy it. They rarely join the discussion and answer only when asked. They vote second, just before the disengaged voters.",[11,86,87],{},[14,88],{"alt":81,"height":68,"loading":44,"src":89,"width":70,"decoding":47},"\u002Fblog\u002Fsheepherding-story-points\u002Fimg5.png",[11,91,92],{},[51,93,81],{},[54,95,97],{"id":96},"the-disengaged-voter","The disengaged voter",[11,99,100],{},"They are hard to pin down during implementation, but their behavior is obvious during voting. They always vote last and copy someone else's estimate. If the estimates differ, they pick the most common one. They do not want to explain why they chose a lower or higher number, so they avoid collaborating in refinement and dodge questions.",[11,102,103],{},[14,104],{"alt":97,"height":105,"loading":44,"src":106,"width":107,"decoding":47},353,"\u002Fblog\u002Fsheepherding-story-points\u002Fimg4.png",758,[11,109,110],{},[51,111,97],{},[54,113,115],{"id":114},"the-tired-voter","The tired voter",[11,117,118],{},"Some team members cannot stay focused for long and miss key parts of the discussion. They lose context and either guess or hunt for the most common vote to copy.",[11,120,121],{},[14,122],{"alt":115,"height":68,"loading":44,"src":123,"width":70,"decoding":47},"\u002Fblog\u002Fsheepherding-story-points\u002Fimg6.png",[11,125,126],{},[51,127,115],{},[26,129,131],{"id":130},"how-to-keep-the-attention-during-estimation","How to keep the attention during estimation",[11,133,134,135,140,141,143],{},"Estimation matters because only honest story points can ",[136,137,139],"a",{"href":138},"\u002Fblog\u002Fcorrectly-estimating-release-deadline","keep a project on track to its release date",". The key to honest estimation is to counter the ",[34,142,36],{},", whether you use paper cards or software.",[11,145,146],{},"Team members should never see each other's estimates until the moderator reveals them. This way the quiet voter starts thinking, the disengaged voter gets interested and the tired voter wakes up. The best question to ask, especially when someone disagrees with the group, is \"why did you vote X story points?\" That starts a conversation about the real implementation issues. Closed questions such as \"would you agree with X story points?\" invite a meaningless \"yes\".",[11,148,149],{},"A good estimation tool makes refinement more engaging and keeps everyone alert and ready to discuss, so even complex stories get better estimates.",{"title":151,"searchDepth":152,"depth":152,"links":153},"",2,[154,161],{"id":28,"depth":152,"text":29,"children":155},[156,158,159,160],{"id":56,"depth":157,"text":57},3,{"id":80,"depth":157,"text":81},{"id":96,"depth":157,"text":97},{"id":114,"depth":157,"text":115},{"id":130,"depth":152,"text":131},"2026-11-21","2018-04-30","Open votes let the first estimate anchor the room. See how the sheep effect skews story points and how to run planning poker honestly.","md","Sheepherding story points","\u002Fblog\u002Fsheepherding-story-points\u002Fcoffee-table-sheep.jpg",[169,170,171,36,172],"story points","planning poker","anchoring bias","agile estimation","en",{},true,"\u002Fblog\u002Fen\u002Fsheepherding-story-points",{"title":5,"description":164},{"loc":176,"images":179,"lastmod":162},[180,181,182,183,184,185],{"loc":19},{"loc":45},{"loc":69},{"loc":89},{"loc":106},{"loc":123},"sheepherding-story-points","blog\u002Fen\u002Fsheepherding-story-points","m0FgZBGi6-ktByr0j85XgV8pgG-BtNxA3Fip11a4DC8",[190,369,510],{"id":191,"title":192,"author":6,"body":193,"dateModified":162,"datePublished":348,"description":349,"extension":165,"heading":350,"image":351,"imageAlt":199,"keywords":352,"locale":173,"meta":358,"navigation":175,"path":359,"reviewed":175,"seo":360,"sitemap":361,"slug":366,"stem":367,"translationKey":366,"__hash__":368},"blog\u002Fblog\u002Fen\u002Fmanage-sprint-dependencies-with-chained-pull-requests.md","Sprint dependencies and chained pull requests | AELBOX",{"type":8,"value":194,"toc":330},[195,201,204,211,215,219,227,230,234,237,241,244,248,251,255,258,262,265,273,278,282,285,289,292,296,299,303,306,310,313,317,320,324,327],[11,196,197],{},[14,198],{"alt":199,"height":17,"loading":18,"src":200,"width":20,"fetchPriority":21},"A metal chain, planning poker cards and a coffee cup on a table","\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fcoffee-table-chain.webp",[11,202,203],{},"Sprints often contain dependent tickets, either within one team or across several Scrum teams. In a perfect world, dependencies would not exist; in practice, business needs win and dependencies are added to shorten the release cycle. This article describes one way to manage dependent tasks in software teams.",[11,205,206],{},[14,207],{"alt":208,"height":209,"loading":44,"src":210,"width":209,"decoding":47},"Dependencies between tasks",336,"\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fblog-dep1.png",[11,212,213],{},[51,214,208],{},[26,216,218],{"id":217},"the-old-fashioned-way","The old-fashioned way",[11,220,221,222,226],{},"The straightforward approach is to start a task as soon as its dependency is merged into the main branch. With that approach, some team members sit idle until a task is ready. Eventually there is little or no time left for the remaining dependent tasks. The last tasks are carried over, and ",[136,223,225],{"href":224},"\u002Fblog\u002Fcomparison-metrics-for-agile-teams","the team is unhappy",".",[11,228,229],{},"Why does this happen even though capacity is correctly estimated? This happens mostly because of idle time while waiting for colleagues to finish. Even small delays compound, especially in short sprints.",[26,231,233],{"id":232},"working-on-dependent-tasks-simultaneously","Working on dependent tasks simultaneously",[11,235,236],{},"There is a way to do this with a small overhead. When team members work on tasks simultaneously, there are several advantages.",[54,238,240],{"id":239},"better-collaboration","Better collaboration",[11,242,243],{},"When team members work simultaneously on dependent tasks, it resembles pair programming. One person must understand the upstream task; the other must understand the downstream task. The team gains broader knowledge of the problems being solved.",[54,245,247],{"id":246},"avoiding-the-idle-time","Avoiding the idle time",[11,249,250],{},"When tasks run concurrently, nobody waits for a fix to land. Everyone can work at once, with more ad-hoc discussion as questions come up.",[54,252,254],{"id":253},"pull-requests-ready-for-code-review-earlier","Pull requests ready for code review earlier",[11,256,257],{},"When your branch is based on a colleague's branch, approving the original pull request is easier. You already understand how the upstream ticket was implemented, and the original branch has been tested and reviewed throughout implementation. It is no longer unfamiliar territory.",[26,259,261],{"id":260},"using-chained-stacked-pull-requests","Using chained (stacked) pull requests",[11,263,264],{},"This level of concurrency requires the right tooling. With Git-based version control, it is straightforward. The steps below describe the process.",[11,266,267],{},[14,268],{"alt":269,"height":270,"loading":44,"src":271,"width":272,"decoding":47},"Dependency tree",438,"\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fdep-img2.png",800,[11,274,275],{},[51,276,277],{},"Dependency tree (working on 6 dependent tasks simultaneously)",[54,279,281],{"id":280},"outline-the-dependencies-clearly","Outline the dependencies clearly",[11,283,284],{},"Define the dependency chain during sprint planning. The pull request chain then follows that definition exactly. Changing the chain mid-development is expensive because of rebasing.",[54,286,288],{"id":287},"start-with-the-root-tasks-first","Start with the root tasks first",[11,290,291],{},"Every dependency chain has root tasks that depend on nothing else. Work on them can start on day one.",[54,293,295],{"id":294},"do-core-implementation-first","Do core implementation first",[11,297,298],{},"This may conflict with test-driven development, where tests come first. To keep the pull request chain manageable, implement the core first. That gives dependent team members access sooner.",[54,300,302],{"id":301},"organize-and-code-review-in-a-fifo-queue","Organize and code review in a FIFO queue",[11,304,305],{},"The first branch created should be reviewed and merged first. Each merge triggers CI; if it breaks the main build, the problem is fixed while it is still small.",[26,307,309],{"id":308},"the-overhead","The overhead",[11,311,312],{},"Maintaining a chain of dependent branches has benefits, but also some drawbacks.",[54,314,316],{"id":315},"rebasing-or-merging","Rebasing or merging",[11,318,319],{},"The chain must be kept in sync, which takes effort. Modern tools offer one-click synchronization with the base branch when there are no conflicts. Use it on demand, when it is safe to pull in upstream changes. When the build is green and the feature works, sync.",[54,321,323],{"id":322},"teamwork","Teamwork",[11,325,326],{},"A dependency chain needs a collaborative team whose members are willing to talk to each other. It cannot work if people work in isolation.",[11,328,329],{},"Dependent tickets are best kept out of the current sprint. When business needs require them to run in parallel, a chain of derived branches is a practical way to manage the dependency overhead.",{"title":151,"searchDepth":152,"depth":152,"links":331},[332,333,338,344],{"id":217,"depth":152,"text":218},{"id":232,"depth":152,"text":233,"children":334},[335,336,337],{"id":239,"depth":157,"text":240},{"id":246,"depth":157,"text":247},{"id":253,"depth":157,"text":254},{"id":260,"depth":152,"text":261,"children":339},[340,341,342,343],{"id":280,"depth":157,"text":281},{"id":287,"depth":157,"text":288},{"id":294,"depth":157,"text":295},{"id":301,"depth":157,"text":302},{"id":308,"depth":152,"text":309,"children":345},[346,347],{"id":315,"depth":157,"text":316},{"id":322,"depth":157,"text":323},"2018-05-27","Dependent tickets stall a sprint while people wait. Learn how stacked pull requests keep work moving and reduce idle time.","Managing sprint dependencies with chained pull requests","\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fcoffee-table-chain.jpg",[353,354,355,356,357],"sprint dependencies","stacked pull requests","chained pull requests","code review","agile delivery",{},"\u002Fblog\u002Fen\u002Fmanage-sprint-dependencies-with-chained-pull-requests",{"title":192,"description":349},{"loc":359,"images":362,"lastmod":162},[363,364,365],{"loc":200},{"loc":210},{"loc":271},"manage-sprint-dependencies-with-chained-pull-requests","blog\u002Fen\u002Fmanage-sprint-dependencies-with-chained-pull-requests","wvh2xXsMf-_D4su-7k6V7w5M5HeQzIs6vYvyGaF6jn8",{"id":370,"title":371,"author":6,"body":372,"dateModified":162,"datePublished":489,"description":490,"extension":165,"heading":491,"image":492,"imageAlt":378,"keywords":493,"locale":173,"meta":499,"navigation":175,"path":500,"reviewed":175,"seo":501,"sitemap":502,"slug":507,"stem":508,"translationKey":507,"__hash__":509},"blog\u002Fblog\u002Fen\u002Fcomparison-metrics-for-agile-teams.md","Comparison metrics for agile teams | AELBOX",{"type":8,"value":373,"toc":480},[374,381,384,388,391,399,403,407,410,414,417,425,429,436,440,443,446,453,457,460,467,470,474,477],[11,375,376],{},[14,377],{"alt":378,"height":379,"loading":18,"src":380,"width":20,"fetchPriority":21},"A ruler, planning poker cards and a coffee cup on a table",958,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Fcoffee-table-ruler.webp",[11,382,383],{},"Comparing agile teams is difficult, and it is worth asking why we compare them at all. How does comparing teams in different domains actually help?",[26,385,387],{"id":386},"creating-a-competition","Creating a competition",[11,389,390],{},"Teams should not be ranked against each other on arbitrary metrics. That only demotivates people. Instead, metrics should give every team an equal opportunity to compete. Performance then improves because teams want it to, not because someone is pushing.",[11,392,393],{},[14,394],{"alt":395,"height":396,"loading":44,"src":397,"width":398,"decoding":47},"Create a competition",487,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun2.png",525,[11,400,401],{},[51,402,395],{},[26,404,406],{"id":405},"the-metrics-for-creating-equal-opportunities","The metrics for creating equal opportunities",[11,408,409],{},"Here are four basic metrics for comparing teams. They measure each team's ability to compete on equal ground, nothing more. Comparable metrics create equal opportunities.",[54,411,413],{"id":412},"successful-sprints","Successful sprints",[11,415,416],{},"If a sprint were only a time frame, it would serve no purpose. A sprint is a milestone and needs a goal. The sprint goal (the most important set of stories) is the larger milestone; completing every story is the smaller one. Hold a cross-team demo at the end of each sprint where teams present what they delivered. That healthy competition encourages teams to finish their sprint goals. People need a visible goal to be motivated.",[11,418,419],{},[14,420],{"alt":421,"height":422,"loading":44,"src":423,"width":424,"decoding":47},"Sprint to a goal",680,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun1.png",874,[11,426,427],{},[51,428,421],{},[11,430,431,432,435],{},"Could this turn into a game of over- and under-commitment? If a team under-commits, the demo makes it obvious: there is less to show. If it over-commits, the demo becomes ",[34,433,434],{},"yet another failed sprint",". Delivering what the team committed to builds the motivation to do more. Teams feel satisfied with the work.",[54,437,439],{"id":438},"velocity-stability-and-the-honest-estimation","Velocity stability and the honest estimation",[11,441,442],{},"This is knowledge work, not assembly-line work. If nobody on the team understands a problem well enough to estimate its solution, the problem was not researched in advance.",[11,444,445],{},"A time-boxed spike in the previous sprint, followed by a team review of the findings, makes it easy to split the implementation into smaller stories and estimate them properly. For complex work, write a fuller technical design document that lists the implementation stories.",[11,447,448,449,226],{},"The spike and the design work are themselves stories that can be estimated. The key is defining the structure and sequence of work for a complex solution. Instead of committing to a story the team does not understand, create a research task to fill the gap. Then estimation is ",[136,450,452],{"href":451},"\u002Fblog\u002Fsheepherding-story-points","grounded in evidence",[54,454,456],{"id":455},"capacity-predictability-avoiding-unexpected-work","Capacity predictability (avoiding unexpected work)",[11,458,459],{},"Research comes first; implementation follows. As research uncovers problems, new tickets are created and estimated. You then have a much clearer picture of the next sprint. Known work can be estimated and planned; unknown work gets a time-boxed research ticket before it is estimated. The discipline is splitting large work into small, estimable pieces.",[11,461,462,463,226],{},"Complex work can start early, even if only to discover that it needs its own set of stories. That still reduces the ",[136,464,466],{"href":465},"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint","risk of the unknown",[11,468,469],{},"Support and production firefighting usually run in a time-boxed Kanban flow outside the sprint. There, time to first response and SLA breaches become the comparison metrics.",[54,471,473],{"id":472},"team-availability-time-spent-on-tasks-divided-by-total-time-in-a-sprint","Team availability (time spent on tasks divided by total time in a sprint)",[11,475,476],{},"Availability is the share of time team members spend on estimated work. If one team is pulled into training, knowledge sharing or other internal work more often than others, fix the imbalance. The only way to keep velocity stable is to keep availability stable. When availability between teams is equal, the other comparison metrics will work.",[11,478,479],{},"Comparing teams is not about punishing low performance, but about increasing motivation and the spirit to compete and deliver more. That is why those metrics should not be visible to individual team members: they are a tool for coaching, not for public rankings. By tracking these metrics and guiding Scrum Masters indirectly, you give teams equal footing to compete.",{"title":151,"searchDepth":152,"depth":152,"links":481},[482,483],{"id":386,"depth":152,"text":387},{"id":405,"depth":152,"text":406,"children":484},[485,486,487,488],{"id":412,"depth":157,"text":413},{"id":438,"depth":157,"text":439},{"id":455,"depth":157,"text":456},{"id":472,"depth":157,"text":473},"2018-05-04","Metrics should create equal ground, not a leaderboard. Four comparison metrics that motivate agile teams without punishing them.","Comparison metrics for agile teams","\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Fcoffee-table-ruler.jpg",[494,495,496,497,498],"agile metrics","team velocity","agile teams","scrum","capacity",{},"\u002Fblog\u002Fen\u002Fcomparison-metrics-for-agile-teams",{"title":371,"description":490},{"loc":500,"images":503,"lastmod":162},[504,505,506],{"loc":380},{"loc":397},{"loc":423},"comparison-metrics-for-agile-teams","blog\u002Fen\u002Fcomparison-metrics-for-agile-teams","7dD24JRfvLNCanpoMQPK1XHg24wBljL3TZETU2V8M7M",{"id":511,"title":512,"author":6,"body":513,"dateModified":162,"datePublished":586,"description":587,"extension":165,"heading":588,"image":589,"imageAlt":519,"keywords":590,"locale":173,"meta":595,"navigation":175,"path":596,"reviewed":175,"seo":597,"sitemap":598,"slug":603,"stem":604,"translationKey":603,"__hash__":605},"blog\u002Fblog\u002Fen\u002Fthe-10-percent-scrumban-rule-for-every-sprint.md","The 10% Scrumban rule for every sprint | AELBOX",{"type":8,"value":514,"toc":581},[515,522,530,534,537,545,549,553,556,560,563,566,574,578],[11,516,517],{},[14,518],{"alt":519,"height":520,"loading":18,"src":521,"width":20,"fetchPriority":21},"Planning poker cards and a Kanban board on a coffee table",959,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fcoffee-table-scrumban.webp",[11,523,524,525,529],{},"Many teams plan to use exactly the capacity shown in their Jira plan. That is often a mistake and leads to failed sprints. Why does it happen when the ",[136,526,528],{"href":527},"\u002Fblog\u002Fthe-importance-of-predictable-velocity","capacity calculations"," look so precise?",[26,531,533],{"id":532},"the-rush-to-deliver-more","The rush to deliver more",[11,535,536],{},"Product Owners tend to push for higher velocity after every successful sprint, a natural reaction to the latest results. If the team completed a certain number of story points last sprint, it is expected to complete more next sprint. This repeats until a sprint fails. The push is an attempt to test the team's limits. In our experience, it is counter-productive. It ultimately demotivates the team, who come to see every future sprint as doomed.",[11,538,539],{},[14,540],{"alt":541,"height":542,"loading":44,"src":543,"width":544,"decoding":47},"The doomed sprint",349,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fimg1.png",400,[11,546,547],{},[51,548,541],{},[26,550,552],{"id":551},"the-hectic-end-of-a-sprint-during-a-delivery-rush","The hectic end of a sprint during a delivery rush",[11,554,555],{},"When capacity is planned to fill the sprint exactly, any delay or realized risk creates pressure to work at a frantic pace at the end. The team then delivers less than promised because stress takes over. That end-of-sprint rush should be eliminated.",[26,557,559],{"id":558},"let-the-team-deliver-more-by-its-own-will","Let the team deliver more by its own will",[11,561,562],{},"Plan only 90% of the team's capacity and reserve the remaining 10% for unplanned backlog work. Those tasks are pulled from the backlog in Scrumban fashion during the sprint. The buffer absorbs risk and lets the team finish the sprint (or at least the sprint goal) a few days early. If an external dependency threatens the sprint, a buffered task can replace the problematic one.",[11,564,565],{},"That 10% is not part of the sprint commitment. If risk does not materialize, the team delivers it as extra work; if something goes wrong, the buffer is consumed but the sprint goal and commitment are still met. Monitor how much of the buffer is used: if it regularly reaches 20%, for example, it is time to raise the team's velocity by 10% while keeping the 10% buffer.",[11,567,568],{},[14,569],{"alt":570,"height":571,"loading":44,"src":572,"width":573,"decoding":47},"Deliver early, deliver extra",320,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fimg3-1.png",296,[11,575,576],{},[51,577,570],{},[11,579,580],{},"Our experience shows that this is when employees work without pressure and contribute the most. Velocity can then increase at the team's own pace, without outside pressure and with less stress. The increase feels natural and sustainable.",{"title":151,"searchDepth":152,"depth":152,"links":582},[583,584,585],{"id":532,"depth":152,"text":533},{"id":551,"depth":152,"text":552},{"id":558,"depth":152,"text":559},"2018-04-28","Committing to full capacity makes every sprint fragile. A 10% Scrumban buffer absorbs risk, protects the sprint goal and lets velocity grow naturally.","The 10% Scrumban rule for every sprint","\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fcoffee-table-scrumban.jpg",[591,592,593,594,497],"scrumban","sprint capacity","agile buffer","velocity",{},"\u002Fblog\u002Fen\u002Fthe-10-percent-scrumban-rule-for-every-sprint",{"title":512,"description":587},{"loc":596,"images":599,"lastmod":162},[600,601,602],{"loc":521},{"loc":543},{"loc":572},"the-10-percent-scrumban-rule-for-every-sprint","blog\u002Fen\u002Fthe-10-percent-scrumban-rule-for-every-sprint","opFsZGR01i-_Ve2m9OgpL6tVmwOz0coJhY_PzMJbUJk",{"id":607,"title":608,"body":609,"dateModified":753,"datePublished":754,"description":755,"extension":165,"heading":659,"image":756,"imageAlt":659,"keywords":757,"locale":173,"meta":758,"navigation":175,"order":759,"path":760,"section":761,"seo":762,"sitemap":763,"slug":764,"stem":765,"translationKey":766,"__hash__":767},"guide\u002Fguide\u002Fen\u002Fwhat-is-story-point-estimation.md","What is Story Point Estimation? | Scrumpy Planning Poker",{"type":8,"value":610,"toc":748},[611,617,621,649,653,656,661,679,683,686],[11,612,613,614,616],{},"Story point estimation is a collaborative technique used by agile teams to estimate the effort required to complete work items. Instead of estimating in hours or days, teams use abstract units called ",[34,615,169],{}," that represent the relative complexity, effort, and uncertainty of a task.",[26,618,620],{"id":619},"why-story-points","Why Story Points?",[622,623,624,631,637,643],"ul",{},[625,626,627,630],"li",{},[34,628,629],{},"Relative sizing"," - It is easier to say \"this task is twice as hard as that one\" than to guess exact hours",[625,632,633,636],{},[34,634,635],{},"Team calibration"," - Points are defined by the team, for the team, based on shared experience",[625,638,639,642],{},[34,640,641],{},"Velocity tracking"," - Over time, the team learns how many points they can complete in a sprint, enabling more accurate forecasting",[625,644,645,648],{},[34,646,647],{},"Reduced anchoring"," - Abstract units avoid the emotional baggage of time-based estimates",[26,650,652],{"id":651},"how-planning-poker-works","How Planning Poker Works",[11,654,655],{},"Planning Poker is a consensus-based estimation technique where team members privately select a card representing their estimate, then reveal simultaneously to avoid anchoring bias.",[657,658],"docs-figure",{"alt":659,"caption":659,"stem":660},"What is Story Point Estimation?","guide-voting-cards",[662,663,664,667,670,673,676],"ol",{},[625,665,666],{},"A work item is presented for estimation",[625,668,669],{},"Each team member privately selects a card value",[625,671,672],{},"Votes are revealed simultaneously",[625,674,675],{},"The team discusses discrepancies and may re-vote",[625,677,678],{},"The final estimate is accepted and recorded",[26,680,682],{"id":681},"scrumpys-role","Scrumpy's Role",[11,684,685],{},"Scrumpy automates this process inside Jira. It provides:",[622,687,688,694,700,706,712,718,724,730,736,742],{},[625,689,690,693],{},[34,691,692],{},"Multiple estimation perspectives"," - Estimate the same work item from different angles (complexity, time, risk)",[625,695,696,699],{},[34,697,698],{},"Live voting"," - See votes appear as team members submit them",[625,701,702,705],{},[34,703,704],{},"Instant feedback"," - Changes you make appear right away, and if something cannot be saved the previous state returns",[625,707,708,711],{},[34,709,710],{},"Automatic result computation"," - Configurable averaging methods calculate the final estimate",[625,713,714,717],{},[34,715,716],{},"Certainty signal"," - A percentage that shows how often participants settled on their votes instead of re-voting",[625,719,720,723],{},[34,721,722],{},"Variation signal"," - A percentage that shows how widely the vote values are spread around their average",[625,725,726,729],{},[34,727,728],{},"Required voters and reminders"," - Choose who must vote and nudge anyone who has not",[625,731,732,735],{},[34,733,734],{},"Asynchronous voting"," - Let participants vote at their own pace, with an optional deadline",[625,737,738,741],{},[34,739,740],{},"Built-in chat"," - Discuss estimates and react to messages during a session",[625,743,744,747],{},[34,745,746],{},"Jira integration"," - Accepted estimates are written directly to your Jira board or custom fields",{"title":151,"searchDepth":152,"depth":152,"links":749},[750,751,752],{"id":619,"depth":152,"text":620},{"id":651,"depth":152,"text":652},{"id":681,"depth":152,"text":682},"2026-11-10","2026-07-26","Story points explained: why agile teams estimate in relative units, how planning poker works, and where Scrumpy fits into Jira.","\u002Fog\u002Fguide-what-is-story-point-estimation.jpg",[169,172,170,497],{},1,"\u002Fgetting-started\u002Fwhat-is-story-point-estimation","guide",{"title":608,"description":755},{"loc":760,"lastmod":753},"what-is-story-point-estimation","guide\u002Fen\u002Fwhat-is-story-point-estimation","guide\u002Fwhat-is-story-point-estimation","1LvzuatCesskMgp8oWejkQfEzGP5X2z8jPgSLHfRprc",1795345545403]