[{"data":1,"prerenderedAt":936},["ShallowReactive",2],{"tutorial-en-understanding-charts":3},{"doc":4,"prev":278,"next":601,"related":764},{"id":5,"title":6,"body":7,"dateModified":256,"datePublished":256,"description":257,"extension":258,"heading":259,"image":260,"imageAlt":259,"keywords":261,"locale":266,"meta":267,"navigation":268,"order":269,"path":270,"section":271,"seo":272,"sitemap":273,"slug":274,"stem":275,"translationKey":276,"__hash__":277},"tutorials\u002Ftutorials\u002Fen\u002Funderstanding-charts.md","Understanding the charts | Tutorials | Scrumpy Planning Poker",{"type":8,"value":9,"toc":247},"minimark",[10,14,19,42,48,58,80,85,88,93,96,99,103,112,117,120,123,127,135,140,143,146,150,168,172,175,178,199,202,206,219,224,227,230,244],[11,12,13],"p",{},"Charts turn the votes of a session into a picture. The estimate itself never changes when you switch charts: every chart shows the same votes in a different shape, so you can choose the view that makes agreement, spread, and outliers easiest to read. The charts are pictures only. They cannot be clicked, dragged, or focused.",[15,16,18],"h2",{"id":17},"the-result-chart","The result chart",[11,20,21,22,26,27,29,30,33,34,37,38,41],{},"Open a completed session and select ",[23,24,25],"strong",{},"Results",". While open voting is running, ",[23,28,25],{}," updates as votes arrive. The chart counts how many participants voted each value. With the three votes ",[23,31,32],{},"2 sp",", ",[23,35,36],{},"5 sp",", and ",[23,39,40],{},"8 sp",", it shows three equal parts or bars.",[43,44],"docs-figure",{"alt":45,"caption":46,"stem":47},"A pie chart with one vote each for 2, 5, and 8 story points","Pie result chart","tutorial-chart-pie",[11,49,50,51,33,53,37,55,57],{},"The pie legend sits below the chart and lists ",[23,52,32],{},[23,54,36],{},[23,56,40],{},", one colour for each voted value. A larger slice means that more participants chose that value. Three equal slices mean the team split evenly.",[11,59,60,61,64,65,68,69,33,72,75,76,79],{},"Your chart type is personal and does not change anyone else's view. Open your Jira avatar menu, choose ",[23,62,63],{},"Scrumpy Poker",", find ",[23,66,67],{},"Chart type",", and select ",[23,70,71],{},"Pie",[23,73,74],{},"Vertical bar",", or ",[23,77,78],{},"Horizontal bar",". The choice follows you across spaces and applies to every result you open.",[43,81],{"alt":82,"caption":83,"stem":84},"A vertical bar chart with one vote each for 2, 5, and 8 story points","Vertical bar result chart","tutorial-chart-vertical-bar",[11,86,87],{},"The vertical bar chart keeps the same three votes. Its legend sits above the chart, the card values are on the horizontal axis, and the bar height is the number of voters. It is easier to compare two values that are close together.",[43,89],{"alt":90,"caption":91,"stem":92},"A horizontal bar chart with one vote each for 2, 5, and 8 story points","Horizontal bar result chart","tutorial-chart-horizontal-bar",[11,94,95],{},"The horizontal bar chart turns the same bars on their side. The card values are on the left, the bar length is the number of voters, and long labels stay readable.",[11,97,98],{},"Use the pie for a quick share at a glance, the vertical bars to compare close values, and the horizontal bars when the labels are long.",[15,100,102],{"id":101},"quadrant","Quadrant",[11,104,105,106,108,109,111],{},"A perspective with two parameters shows a ",[23,107,102],{}," tab after ",[23,110,25],{}," once the session completes. Each axis is one parameter, drawn with its real values, including negative ones.",[43,113],{"alt":114,"caption":115,"stem":116},"A quadrant chart with three voters and the averaged position","Quadrant chart","tutorial-chart-quadrant",[11,118,119],{},"Each dot is one participant's vote at its pair of parameter values. The dashed crosshair marks the averaged position calculated from the recorded votes. The chart has no legend: the colours keep the dots apart, but they do not map a dot to a person. That is deliberate, because the chart shows how the votes compare, not who cast them.",[11,121,122],{},"Read a cluster of dots as agreement, a wide spread as a discussion that is still open, and a dot far from the crosshair as an outlier. The quadrant is useful when two factors decide the estimate, for example risk and value.",[15,124,126],{"id":125},"radar","Radar",[11,128,129,130,108,132,134],{},"A perspective with three or more parameters shows a ",[23,131,126],{},[23,133,25],{}," once the session completes. Each ray is one parameter, scaled from its minimum at the centre to its maximum on the outer ring.",[43,136],{"alt":137,"caption":138,"stem":139},"A radar chart with three voters and the averaged polygon","Radar chart","tutorial-chart-radar",[11,141,142],{},"Each participant is one polygon. A corner pulled toward the outer ring means a high value on that parameter. The dotted polygon is the averaged position calculated from the recorded votes. The chart has no legend, so read the shapes rather than looking for names.",[11,144,145],{},"Overlapping polygons mean the team agrees on the profile. A polygon that pulls away on one ray shows where the disagreement sits. The radar is useful when several parameters describe the estimate at once.",[15,147,149],{"id":148},"heat-map","Heat map",[11,151,152,153,156,157,160,161,164,165,167],{},"Open a planning session, switch the edit mode to ",[23,154,155],{},"Bulk voting",", select a card perspective such as ",[23,158,159],{},"Scrum",", open the ",[23,162,163],{},"Bucket"," tab, and select ",[23,166,25],{},". The heat map compares every listed work item in one picture.",[43,169],{"alt":170,"caption":149,"stem":171},"A heat map with three voters across ten work items","tutorial-chart-heatmap",[11,173,174],{},"Rows are the work items and columns are the cards of the perspective. The number inside a cell is how many participants chose that card for that work item. The colour runs from light orange at one vote to dark red at the highest count, and a grey cell means nobody voted that card.",[11,176,177],{},"The heat map has no legend. The card labels and the numbers in the cells are the key:",[179,180,181,189,196],"ul",{},[182,183,184,185,188],"li",{},"A dark cell with ",[23,186,187],{},"3"," means all three voters agree.",[182,190,191,192,195],{},"Three separate ",[23,193,194],{},"1"," cells in a row mean the team split three ways.",[182,197,198],{},"A grey row means the work item has no votes yet.",[11,200,201],{},"Use it to spot the work items that need another round of discussion and the ones that are already settled.",[15,203,205],{"id":204},"scatter","Scatter",[11,207,208,209,211,212,215,216,218],{},"Open the same ",[23,210,163],{}," tab for a free-scale perspective such as ",[23,213,214],{},"Time"," and select ",[23,217,25],{},". The scatter chart compares the story points voted for every listed work item.",[43,220],{"alt":221,"caption":222,"stem":223},"A scatter chart with three voters across ten work items","Scatter chart","tutorial-chart-scatter",[11,225,226],{},"Rows are the work items, the horizontal axis is story points, and every dot is one vote. Dots of the same work item share a colour, and votes at the same value fan out vertically so none is hidden. The dashed cross marks the averaged story points for that work item, and it appears only when more than one vote exists.",[11,228,229],{},"The scatter chart has no legend. Read each row from left to right:",[179,231,232,235,238,241],{},[182,233,234],{},"Dots close together mean the team agrees on that work item.",[182,236,237],{},"Dots spread far apart mean the estimates differ, and the work item needs discussion.",[182,239,240],{},"The dashed cross is the average that becomes the estimate.",[182,242,243],{},"A dot far from the cross is an outlier worth talking about.",[11,245,246],{},"The heat map answers what card the team chose. The scatter answers how far apart the numbers are. Together they show agreement across a whole planning session at a glance.",{"title":248,"searchDepth":249,"depth":249,"links":250},"",2,[251,252,253,254,255],{"id":17,"depth":249,"text":18},{"id":101,"depth":249,"text":102},{"id":125,"depth":249,"text":126},{"id":148,"depth":249,"text":149},{"id":204,"depth":249,"text":205},"2026-11-02","Read the estimation charts: pie, bar, radar, scatter, quadrant and heatmap views of a vote.","md","Understanding the charts","\u002Fog\u002Ftutorial-understanding-charts.jpg",[262,263,264,265],"estimation charts","heatmap","scatter plot","agile metrics","en",{},true,13,"\u002Ftutorials\u002Funderstanding-charts","tutorial",{"title":6,"description":257},{"loc":270,"lastmod":256},"understanding-charts","tutorials\u002Fen\u002Funderstanding-charts","tutorial\u002Funderstanding-charts","5yoIYYZbaXtR0HixB8a1KIP-qKjmY_9_kuDp-7ZXYUg",{"id":279,"title":280,"body":281,"dateModified":584,"datePublished":256,"description":585,"extension":258,"heading":586,"image":587,"imageAlt":586,"keywords":588,"locale":266,"meta":592,"navigation":268,"order":593,"path":594,"section":271,"seo":595,"sitemap":596,"slug":597,"stem":598,"translationKey":599,"__hash__":600},"tutorials\u002Ftutorials\u002Fen\u002Faffinity-and-dot-ranking.md","Affinity and Dot ranking | Tutorials | Scrumpy Planning Poker",{"type":8,"value":282,"toc":573},[283,286,304,308,326,329,333,351,358,375,380,384,392,395,403,408,412,431,438,455,458,463,467,484,487,491,501,510,514,536,545,549,554,557,561,564],[11,284,285],{},"A team does not always need an estimate to agree on what matters most. Affinity ranking asks every participant to put the work items in order. Dot voting gives every participant a small budget of dots, and the dots decide the order. Scrumpy then uses that order in the Bucket voting table, where the team can estimate the work items without losing it.",[11,287,288,289,292,293,33,295,37,297,300,301,303],{},"This tutorial continues the setup from ",[23,290,291],{},"Creating a planning session",": ten work items, the ",[23,294,214],{},[23,296,159],{},[23,298,299],{},"Bugs"," perspectives, and three participants. It uses the ",[23,302,159],{}," perspective.",[15,305,307],{"id":306},"open-the-ranking-panel","Open the ranking panel",[11,309,310,311,313,314,316,317,33,320,37,323,325],{},"Open the planning session and switch the edit mode to ",[23,312,155],{},". A row for each perspective appears below the work items. Select the radio beside ",[23,315,159],{},". The panel on the right opens with ",[23,318,319],{},"Affinity",[23,321,322],{},"Dot",[23,324,163],{}," tabs, the perspective title and description, a settings gear, your role badge, and the sound bell.",[11,327,328],{},"Only voters can rank. A guest sees the same tables read-only.",[15,330,332],{"id":331},"rank-with-affinity","Rank with Affinity",[11,334,335,336,338,339,342,343,346,347,350],{},"Open the ",[23,337,319],{}," tab. Drag a work item up or down to change its position. Every move is saved as you drag and shared live, so the other participants see your order at once. The table keeps your own order. ",[23,340,341],{},"My rank"," is your position, ",[23,344,345],{},"Deviation"," is your distance from the agreed position, and ",[23,348,349],{},"Rank"," is the agreed position. A positive deviation means the team ranked the work item above your position, and a negative one means it ranked it below.",[11,352,353,354,357],{},"Every listed work item takes part, even when you never moved it. Below the table you see the participants who have ranked. ",[23,355,356],{},"Withdraw"," removes your ranking.",[11,359,360,361,364,365,368,369,371,372,374],{},"A moderator chooses the agreed position with ",[23,362,363],{},"Mean rank"," or ",[23,366,367],{},"Median rank"," beside the perspective title. ",[23,370,363],{}," averages the positions, and ",[23,373,367],{}," uses the middle position.",[43,376],{"alt":377,"caption":378,"stem":379},"The Affinity tab after three participants ranked ten work items","The Affinity panel with three participants","tutorial-affinity-ranking",[15,381,383],{"id":382},"rank-with-dots","Rank with dots",[11,385,335,386,388,389,391],{},[23,387,322],{}," tab. Each participant can place one dot on a work item, and placing the same dot again removes it. A work item's rank is the total number of dots it receives from all participants. The ",[23,390,349],{}," column shows that total.",[11,393,394],{},"The dot budget is the number of dots each participant can give. It is one dot per work item by default, so ten dots for ten work items, and a moderator can lower it. A moderator can also share one budget between all participants; dots are then given first come, first served. The moderator sees the number field, and everyone sees the dots-left badge. In this example each participant spent between five and eight dots.",[11,396,397,399,400,402],{},[23,398,356],{}," removes all of your dots. The ",[23,401,25],{}," tab of both rankings shows a chart: the agreed position for Affinity and the dot count for Dot.",[43,404],{"alt":405,"caption":406,"stem":407},"The Dot tab after three participants spent between five and eight dots each","The Dot panel with three participants","tutorial-dot-ranking",[15,409,411],{"id":410},"rank-the-bucket-table","Rank the bucket table",[11,413,335,414,416,417,420,421,364,424,427,428,430],{},[23,415,163],{}," tab. The dropdown beside the perspective title reads ",[23,418,419],{},"No ranking"," by default. Choose ",[23,422,423],{},"Affinity ranking",[23,425,426],{},"Dot ranking"," once at least one participant has submitted that ranking. The table then lists the work items from the best rank to the worst and adds a ",[23,429,349],{}," column. The card rows keep their configured order.",[11,432,433,434,437],{},"Work items with the same rank can be reordered inside the same card row or inside ",[23,435,436],{},"No estimate",", but they cannot cross a work item with a different rank. Dragging a work item under a card can change more than one row, because the table keeps the rank order:",[179,439,440,446,449],{},[182,441,442,443,445],{},"Drop onto ",[23,444,436],{}," to clear the dropped work item and the better-ranked carded work items above it.",[182,447,448],{},"Drop onto a better card, higher in the table, to move the dropped work item and the better-ranked carded work items it passes under that card.",[182,450,451,452,454],{},"Drop onto a worse card, lower in the table, or out of ",[23,453,436],{},", to move the dropped work item and the worse-ranked work items that land under that card.",[11,456,457],{},"Work items with the same rank as the dropped work item never move with it. Only the dropped work item changes card among its rank peers. Every work item that lands under a card takes that card's estimate, so the whole group is estimated together.",[43,459],{"alt":460,"caption":461,"stem":462},"The Bucket tab with Affinity ranking, the ranked work items in the No estimate group, and the Rank column","The Bucket tab with Affinity ranking","tutorial-bucket-ranking",[15,464,466],{"id":465},"changing-the-ranking-clears-the-bucket-votes","Changing the ranking clears the bucket votes",[11,468,469,470,472,473,364,475,477,478,480,481,483],{},"Switching from ",[23,471,419],{}," to ",[23,474,423],{},[23,476,426],{},", or between the two, resets the votes in the Bucket table and returns every work item to ",[23,479,436],{},". The change appears at once, and if it cannot be saved, the previous ranking and votes return. Switching back to ",[23,482,419],{}," keeps the votes you have.",[11,485,486],{},"Once the enforced ranking has a vote or a completed session in the Bucket table, its own tab locks. You cannot rerank the Affinity table, place or remove dots, or withdraw, and the algorithm selector becomes read-only. Change the enforced ranking to unlock it. The other ranking stays editable.",[15,488,490],{"id":489},"sync-the-rankings-with-jira","Sync the rankings with Jira",[11,492,493,496,497,500],{},[23,494,495],{},"Affinity:"," only a moderator sees the ",[23,498,499],{},"Sync to Jira"," arrow. Scrumpy uses the rank field configured on the board you opened the space page from. If Jira does not report a board, or the board does not configure a rank field, Jira's default rank field is used. Press the arrow and Scrumpy writes the agreed order, not your own order, into the Jira rank. The top work item keeps its place and the rest are ranked after it, so the listed work items become one ranked block. If Jira refuses the change, an error appears below the controls and you can try again. You need permission to rank work items in Jira.",[11,502,503,506,507,509],{},[23,504,505],{},"Dots:"," every participant presses the ",[23,508,499],{}," arrow in their own Dot panel. Scrumpy adds or removes your Jira vote on each listed work item so it matches your dots. Each participant syncs their own votes. This changes the Jira votes, not the estimates. If some work items fail, an error appears and you can try again.",[15,511,513],{"id":512},"reset-a-ranking","Reset a ranking",[179,515,516,521,530],{},[182,517,518,520],{},[23,519,356],{}," removes your own ranking or all of your dots.",[182,522,523,526,527,529],{},[23,524,525],{},"Clear rankings",", the delete icon beside ",[23,528,356],{},", is for a moderator and deletes the rankings for everyone on that tab.",[182,531,532,533,535],{},"Choose ",[23,534,419],{}," in the Bucket tab to stop enforcing a ranking.",[11,537,538,539,541,542,544],{},"If the ranking you clear was the enforced one, the Bucket tab returns to ",[23,540,419],{}," by itself. With a completed session, the Bucket tab allows only ",[23,543,419],{},".",[15,546,548],{"id":547},"when-the-rankings-are-deleted","When the rankings are deleted",[11,550,551,552,544],{},"Cancelling or accepting a work item's voting session removes that work item from both rankings. When you accept the estimates and close the last voting session, both rankings for that perspective are deleted and the enforced ranking returns to ",[23,553,419],{},[11,555,556],{},"Completing a session does not delete its ranking. The completed work item keeps its place, and the enforced order stays locked until you cancel or accept that session.",[15,558,560],{"id":559},"completed-sessions-lock-the-bucket-table","Completed sessions lock the bucket table",[11,562,563],{},"A completed session stays in the Bucket table with its recorded vote, so you can compare it with the others. It cannot be moved or re-estimated.",[11,565,566,567,569,570,572],{},"When a ranking is enforced and at least one voting session is completed, the whole Bucket table is locked. You cannot drag work items or press ",[23,568,356],{},", and the ranking dropdown allows only ",[23,571,419],{},". Cancel or accept the completed sessions to unlock the table.",{"title":248,"searchDepth":249,"depth":249,"links":574},[575,576,577,578,579,580,581,582,583],{"id":306,"depth":249,"text":307},{"id":331,"depth":249,"text":332},{"id":382,"depth":249,"text":383},{"id":410,"depth":249,"text":411},{"id":465,"depth":249,"text":466},{"id":489,"depth":249,"text":490},{"id":512,"depth":249,"text":513},{"id":547,"depth":249,"text":548},{"id":559,"depth":249,"text":560},"2026-11-08","Group work items by affinity and rank them with dot voting to speed up large refinements.","Affinity and Dot ranking","\u002Fog\u002Ftutorial-affinity-and-dot-ranking.jpg",[589,590,591],"affinity ranking","dot voting","backlog refinement",{},12,"\u002Ftutorials\u002Faffinity-and-dot-ranking",{"title":280,"description":585},{"loc":594,"lastmod":584},"affinity-and-dot-ranking","tutorials\u002Fen\u002Faffinity-and-dot-ranking","tutorial\u002Faffinity-and-dot-ranking","rcWzwNos5qn1ewoWDRh93HZS_38wLdC3_wwXb-YKeio",{"id":602,"title":603,"body":604,"dateModified":748,"datePublished":748,"description":749,"extension":258,"heading":618,"image":750,"imageAlt":618,"keywords":751,"locale":266,"meta":755,"navigation":268,"order":756,"path":757,"section":271,"seo":758,"sitemap":759,"slug":760,"stem":761,"translationKey":762,"__hash__":763},"tutorials\u002Ftutorials\u002Fen\u002Fcapacity-planning.md","Capacity planning | Tutorials | Scrumpy Planning Poker",{"type":8,"value":605,"toc":738},[606,609,613,628,632,635,639,648,653,657,660,665,669,683,687,690,693,698,702,708,712,716,722,726,733],[11,607,608],{},"Capacity planning helps your team see how much work fits into the next sprints before you commit to it. Scrumpy compares the work you plan with the capacity your team really has, so the conversation starts from numbers instead of guesses.",[15,610,612],{"id":611},"start-with-the-sprints-you-finished","Start with the sprints you finished",[11,614,615,616,619,620,623,624,627],{},"Open the space page and choose the ",[23,617,618],{},"Capacity planning"," tab. Select your planning session, then select ",[23,621,622],{},"Plan sprint",". In the ",[23,625,626],{},"Past sprints"," tab, tick the closed sprints that should set your team's velocity. Three past sprints give a steady average. Each past sprint should include the work the team completed, and its team should be filled in.",[43,629],{"alt":630,"caption":626,"stem":631},"The Plan sprint dialog with three past sprints selected","tutorial-capacity-plan-sprint-past",[11,633,634],{},"If you are starting for the first time and there are no past sprints, you can still plan. Add the team to the sprint you want to plan, set each person's utilization and hours of work, and Scrumpy calculates the target from that team. Add past sprints later to get a velocity.",[15,636,638],{"id":637},"add-the-active-and-future-sprints-you-want-to-plan","Add the active and future sprints you want to plan",[11,640,335,641,644,645,544],{},[23,642,643],{},"Sprints"," tab in the same dialog and tick the active or future sprints you want to include. You can plan several sprints at once, so the team can compare the next few weeks in one view. Select ",[23,646,647],{},"Add",[43,649],{"alt":650,"caption":651,"stem":652},"The Sprints tab of the Plan sprint dialog with an active sprint selected","Active and future sprints","tutorial-capacity-plan-sprint-future",[15,654,656],{"id":655},"the-board-selector-decides-which-sprints-you-can-plan","The board selector decides which sprints you can plan",[11,658,659],{},"This part is important. The sprint picker only lists sprints that originated from the board currently chosen in the board selector at the top left of the capacity table. Switch the board and the list changes. Each board keeps its own plan, so choose the board first, then add its sprints.",[43,661],{"alt":662,"caption":663,"stem":664},"The board selector at the top left of the capacity planning page","Board selector","tutorial-capacity-board-selector",[15,666,668],{"id":667},"add-and-remove-work-items","Add and remove work items",[11,670,671,672,675,676,679,680,544],{},"With a sprint selected in the table, use ",[23,673,674],{},"Add from filter"," to bring in work items from a saved Jira filter, a sprint, or a Refinement\u002Fgrooming session. Drag a work item to reorder it inside its sprint, or drag it onto another sprint row to move it. To remove items, tick them and select ",[23,677,678],{},"Remove",". Removing an item changes the plan, not Jira, until you select ",[23,681,682],{},"Apply",[15,684,686],{"id":685},"read-the-capacity-timeline","Read the capacity timeline",[11,688,689],{},"In this example the planned sprint has seven work items. Their estimates are 1, 2, 3, 5, 8, 5, and 3 story points. The timeline adds them up as you read down the table. Green means there is room, yellow means you are close to the healthy range, and red means the running total is above the capacity your team has.",[11,691,692],{},"If the later work items sit behind a red line, the plan is too big for this team. Remove an item, lower an estimate, or add capacity before you start the sprint.",[43,694],{"alt":695,"caption":696,"stem":697},"The capacity table with seven work items and the timeline turning red above capacity","Capacity timeline","tutorial-capacity-timeline",[15,699,701],{"id":700},"set-up-the-team","Set up the team",[11,703,335,704,707],{},[23,705,706],{},"Team capacity"," tab. This example has three team members. Each person has a utilization percentage and hours of work for the sprint. Time off is added in the person's calendar. When you change a value, the target and the timeline update right away.",[43,709],{"alt":710,"caption":706,"stem":711},"The Team capacity table with three team members and their hours","tutorial-capacity-team",[15,713,715],{"id":714},"agree-on-the-sprint-goal","Agree on the sprint goal",[11,717,335,718,721],{},[23,719,720],{},"Sprint"," tab to write the sprint goal. Everyone can vote with the thumbs up and thumbs down buttons, and the counts update for the whole team. A clear goal helps the team agree on what the sprint is for before voting starts.",[15,723,725],{"id":724},"vote-on-a-work-item-and-chat","Vote on a work item and chat",[11,727,728,729,732],{},"Select a work item in the table, then open a perspective tab to vote with the same cards you use in Refinement\u002Fgrooming. A ",[23,730,731],{},"Chat"," tab appears for the selected work item, so the team can discuss that item without leaving the capacity plan.",[43,734],{"alt":735,"caption":736,"stem":737},"The perspective voting panel and the Chat tab for a planned work item","Vote and chat","tutorial-capacity-voting-chat",{"title":248,"searchDepth":249,"depth":249,"links":739},[740,741,742,743,744,745,746,747],{"id":611,"depth":249,"text":612},{"id":637,"depth":249,"text":638},{"id":655,"depth":249,"text":656},{"id":667,"depth":249,"text":668},{"id":685,"depth":249,"text":686},{"id":700,"depth":249,"text":701},{"id":714,"depth":249,"text":715},{"id":724,"depth":249,"text":725},"2026-11-10","Plan the next sprints from recent velocity, read the capacity timeline and apply the plan to Jira.","\u002Fog\u002Ftutorial-capacity-planning.jpg",[752,753,754],"capacity planning","sprint capacity","velocity",{},14,"\u002Ftutorials\u002Fcapacity-planning",{"title":603,"description":749},{"loc":757,"lastmod":748},"capacity-planning","tutorials\u002Fen\u002Fcapacity-planning","tutorial\u002Fcapacity-planning","dXqFjEQiGF7gHvaxbkFg7mAJK_PdEsz8aLt9oMCwdxI",{"id":765,"title":766,"body":767,"dateModified":748,"datePublished":919,"description":920,"extension":258,"heading":786,"image":921,"imageAlt":786,"keywords":922,"locale":266,"meta":926,"navigation":268,"order":927,"path":928,"section":929,"seo":930,"sitemap":931,"slug":932,"stem":933,"translationKey":934,"__hash__":935},"guide\u002Fguide\u002Fen\u002Fpersonal-settings.md","Personal Settings | Scrumpy Planning Poker",{"type":8,"value":768,"toc":913},[769,772,775,779,784,788,835,839,845,858,861,865,868,900,903,906,910],[11,770,771],{},"Personal settings let each team member customize their Scrumpy experience. These settings are stored per user and follow you across all spaces.",[11,773,774],{},"Changes apply immediately and are synced to your other open panels right away. If a change cannot be saved, the setting returns to its previous value.",[15,776,778],{"id":777},"chart-type","Chart Type",[11,780,781,782,544],{},"Controls how voting results are visualized after a session completes. The default is ",[23,783,71],{},[43,785],{"alt":786,"caption":786,"stem":787},"Personal Settings","guide-personal-settings",[789,790,791,804],"table",{},[792,793,794],"thead",{},[795,796,797,801],"tr",{},[798,799,800],"th",{},"Option",[798,802,803],{},"Best for",[805,806,807,817,826],"tbody",{},[795,808,809,814],{},[810,811,812],"td",{},[23,813,71],{},[810,815,816],{},"Quick glance at vote distribution",[795,818,819,823],{},[810,820,821],{},[23,822,74],{},[810,824,825],{},"Comparing individual vote values",[795,827,828,832],{},[810,829,830],{},[23,831,78],{},[810,833,834],{},"Reading vote labels comfortably",[15,836,838],{"id":837},"card-visuals","Card Visuals",[11,840,841,842,544],{},"Adjusts the appearance of voting cards in the estimation panel. The default is ",[23,843,844],{},"Colorful",[179,846,847,852],{},[182,848,849,851],{},[23,850,844],{},": Bright, visually distinct cards with gradients",[182,853,854,857],{},[23,855,856],{},"Minimalistic",": Subdued, flat design for less visual distraction. Cards show the estimate value instead of a playful label",[11,859,860],{},"Choose minimalistic if you find colorful visuals distracting during focused estimation sessions.",[15,862,864],{"id":863},"sound-volume","Sound Volume",[11,866,867],{},"Controls the volume of audio notifications, from 0% to 100%. The default is 50%. Scrumpy plays sounds for key events:",[179,869,870,876,882,888,894],{},[182,871,872,875],{},[23,873,874],{},"Vote",": When another participant casts a vote",[182,877,878,881],{},[23,879,880],{},"Start",": When the moderator starts a voting session",[182,883,884,887],{},[23,885,886],{},"End",": When the voting session reveals results",[182,889,890,893],{},[23,891,892],{},"Reminder",": When the moderator sends a reminder to unvoted participants",[182,895,896,899],{},[23,897,898],{},"Message",": When a new chat message arrives",[11,901,902],{},"Scrumpy does not play a sound for your own action. For example, you hear the vote sound when someone else votes, and the message sound for incoming messages, not for the one you just sent.",[11,904,905],{},"Set the volume to 0% to mute all sounds. Your preference is remembered across sessions. The voting panel header also has a quick mute toggle that turns sound on or off without changing this volume.",[15,907,909],{"id":908},"resetting","Resetting",[11,911,912],{},"You can reset all personal settings to their defaults from the Personal settings panel. A confirmation appears first, and the reset cannot be undone.",{"title":248,"searchDepth":249,"depth":249,"links":914},[915,916,917,918],{"id":777,"depth":249,"text":778},{"id":837,"depth":249,"text":838},{"id":863,"depth":249,"text":864},{"id":908,"depth":249,"text":909},"2026-07-26","Personal settings in Scrumpy: chart type, card visuals, sound volume and how to reset your own preferences.","\u002Fog\u002Fguide-personal-settings.jpg",[923,924,925],"scrumpy settings","chart type","jira estimation app",{},6,"\u002Fgetting-started\u002Fpersonal-settings","guide",{"title":766,"description":920},{"loc":928,"lastmod":748},"personal-settings","guide\u002Fen\u002Fpersonal-settings","guide\u002Fpersonal-settings","0b68M8kSjL4pUwUkWJv1uat3Xlb4Q695DsSN0vajubo",1795345576512]