[{"data":1,"prerenderedAt":2730},["ShallowReactive",2],{"tutorials-en":3},[4,93,171,308,401,590,713,841,1006,1132,1239,1346,1664,1914,2075,2167,2481],{"id":5,"title":6,"body":7,"dateModified":72,"datePublished":72,"description":73,"extension":74,"heading":75,"image":76,"imageAlt":75,"keywords":77,"locale":81,"meta":82,"navigation":83,"order":84,"path":85,"section":86,"seo":87,"sitemap":88,"slug":89,"stem":90,"translationKey":91,"__hash__":92},"tutorials\u002Ftutorials\u002Fen\u002Fcard-voting.md","Voting with cards | Tutorials | Scrumpy Planning Poker",{"type":8,"value":9,"toc":65},"minimark",[10,14,19,22,28,32,48,53,57,60],[11,12,13],"p",{},"Voting with cards takes just a few clicks: set up your team once, start a session, and let everyone pick their estimate.",[15,16,18],"h2",{"id":17},"set-up-your-team-once","Set up your team once",[11,20,21],{},"Before any voting starts, a space administrator sets up the moderators and voters for the space. This is a one-time step: Scrumpy remembers the team for every session after that. Everyone else can watch the session and see the results, but only voters cast cards and only moderators run the session.",[23,24],"docs-figure",{"alt":25,"caption":26,"stem":27},"The Permissions tab in space settings with the Voters and Moderators fields filled in","Permissions","tutorial-permissions",[15,29,31],{"id":30},"start-a-session-and-vote","Start a session and vote",[11,33,34,35,39,40,43,44,47],{},"Once you are a moderator, press ",[36,37,38],"strong",{},"Start"," in the work item panel and the session begins. Participants pick the card that matches their estimate and cast it. When the discussion is over, the moderator finalizes the session: ",[36,41,42],{},"Accept"," the calculated estimate, or ",[36,45,46],{},"Override"," the result with the number the team agreed on.",[23,49],{"alt":50,"caption":51,"stem":52},"The estimation panel with the card deck and the Start button","Start and vote","tutorial-cards-ad-hoc",[15,54,56],{"id":55},"make-the-cards-yours","Make the cards yours",[11,58,59],{},"The deck fits the way your team estimates. Turn individual cards on or off, give them your own titles, and even upload custom images. Voters then see only the options you chose, so every vote stays quick and focused.",[23,61],{"alt":62,"caption":63,"stem":64},"Card settings with the card sequence, the available cards, and their custom titles","Card settings","tutorial-cards-configure",{"title":66,"searchDepth":67,"depth":67,"links":68},"",2,[69,70,71],{"id":17,"depth":67,"text":18},{"id":30,"depth":67,"text":31},{"id":55,"depth":67,"text":56},"2026-10-26","Vote with cards in Scrumpy: set up the team once, start a session and accept or override the estimate.","md","Voting with cards","\u002Fog\u002Ftutorial-card-voting.jpg",[78,79,80],"planning poker cards","card voting","jira estimation","en",{},true,1,"\u002Ftutorials\u002Fcard-voting","tutorial",{"title":6,"description":73},{"loc":85,"lastmod":72},"card-voting","tutorials\u002Fen\u002Fcard-voting","tutorial\u002Fcard-voting","OxrCEEfNkztwuicNXVgmtWWUifGbtX2fWDWxra_eBZU",{"id":94,"title":95,"body":96,"dateModified":72,"datePublished":72,"description":156,"extension":74,"heading":157,"image":158,"imageAlt":157,"keywords":159,"locale":81,"meta":163,"navigation":83,"order":67,"path":164,"section":86,"seo":165,"sitemap":166,"slug":167,"stem":168,"translationKey":169,"__hash__":170},"tutorials\u002Ftutorials\u002Fen\u002Ffree-scale-voting.md","Voting on a free scale | Tutorials | Scrumpy Planning Poker",{"type":8,"value":97,"toc":152},[98,101,105,124,129,133,148],[11,99,100],{},"A free scale keeps the cards out of the way and lets the team pick an estimate with a slider. It takes a minute to set up and one click to vote.",[15,102,104],{"id":103},"set-up-the-free-scale","Set up the free scale",[11,106,107,108,111,112,115,116,119,120,123],{},"In the perspective settings, choose ",[36,109,110],{},"Free scale"," in the ",[36,113,114],{},"Sequence"," dropdown. Then set the ",[36,117,118],{},"Free scale minimum"," and ",[36,121,122],{},"Free scale maximum",": every value between them becomes available to voters, so the range fits the kind of work your team estimates. The preview below the fields shows the slider your voters will see.",[23,125],{"alt":126,"caption":127,"stem":128},"Perspective settings with the Free scale sequence selected and the minimum and maximum fields filled in","Free scale settings","tutorial-free-scale-configure",[15,130,132],{"id":131},"vote-with-the-slider","Vote with the slider",[11,134,135,136,139,140,143,144,147],{},"During a session, each voter moves the slider to the estimate that feels right and presses ",[36,137,138],{},"Vote",". The number appears above the slider with an ",[36,141,142],{},"sp"," suffix. Change your mind? Move the slider again and vote again, or press ",[36,145,146],{},"Withdraw"," to take the vote back.",[23,149],{"alt":150,"caption":132,"stem":151},"The estimation panel with the free scale slider, the selected value, and the Vote and Withdraw buttons","tutorial-free-scale",{"title":66,"searchDepth":67,"depth":67,"links":153},[154,155],{"id":103,"depth":67,"text":104},{"id":131,"depth":67,"text":132},"Estimate on a free scale in Scrumpy, from a slider to precise values, and write the result to Jira.","Voting on a free scale","\u002Fog\u002Ftutorial-free-scale-voting.jpg",[160,161,162],"free scale voting","estimation scale","planning poker",{},"\u002Ftutorials\u002Ffree-scale-voting",{"title":95,"description":156},{"loc":164,"lastmod":72},"free-scale-voting","tutorials\u002Fen\u002Ffree-scale-voting","tutorial\u002Ffree-scale-voting","Uy_fQVxLPK6bl8fSLzAqFmpWnBDKUY8yqeQCYu-nsd8",{"id":172,"title":173,"body":174,"dateModified":292,"datePublished":72,"description":293,"extension":74,"heading":294,"image":295,"imageAlt":294,"keywords":296,"locale":81,"meta":299,"navigation":83,"order":300,"path":301,"section":86,"seo":302,"sitemap":303,"slug":304,"stem":305,"translationKey":306,"__hash__":307},"tutorials\u002Ftutorials\u002Fen\u002Fparametric-voting.md","Voting with 2 parameters | Tutorials | Scrumpy Planning Poker",{"type":8,"value":175,"toc":287},[176,179,183,227,232,236,253,257,261,282],[11,177,178],{},"Some work is easier to describe with more than one number. A parametric perspective combines several parameters with a formula and turns them into one story point result.",[15,180,182],{"id":181},"set-up-the-parameters","Set up the parameters",[11,184,107,185,111,188,190,191,119,194,197,198,201,202,205,206,209,210,213,214,218,219,222,223,226],{},[36,186,187],{},"Parametric",[36,189,114],{}," dropdown. Name the two parameters ",[36,192,193],{},"Risk",[36,195,196],{},"Value",", give each one a ",[36,199,200],{},"Minimum",", a ",[36,203,204],{},"Maximum",", and a ",[36,207,208],{},"Step",", then write the ",[36,211,212],{},"Formula"," from the variable names shown beside the fields, for example ",[215,216,217],"code",{},"(p1 + p2) \u002F 2"," where ",[215,220,221],{},"p1"," is Risk and ",[215,224,225],{},"p2"," is Value. The preview at the bottom shows the sliders and the result your team will see. Add more parameters when two are not enough.",[23,228],{"alt":229,"caption":230,"stem":231},"Perspective settings with the Parametric sequence, two parameters, and the formula","Parameter settings","tutorial-parametric-configure",[15,233,235],{"id":234},"vote-with-the-sliders","Vote with the sliders",[11,237,238,239,119,241,243,244,246,247,249,250,252],{},"During a session, each voter moves the ",[36,240,193],{},[36,242,196],{}," sliders to the values that fit the work. The formula turns those positions into the result shown in large text with an ",[36,245,142],{}," suffix, and a small badge on the right shows how far the rounded result is from the exact formula value. Press ",[36,248,138],{}," to cast it, or ",[36,251,146],{}," to take it back.",[23,254],{"alt":255,"caption":235,"stem":256},"The voting panel with two parameter sliders, the result, the deviation badge, and the Vote and Withdraw buttons","tutorial-parametric",[15,258,260],{"id":259},"read-the-results","Read the results",[11,262,263,264,267,268,270,271,273,274,277,278,281],{},"The ",[36,265,266],{},"Quadrant"," tab draws one dot per participant, so you can see how the votes spread across ",[36,269,193],{}," on the horizontal axis and ",[36,272,196],{}," on the vertical axis, plus a dashed crosshair for the averaged positions. ",[36,275,276],{},"Story points"," averages the results each participant voted, while ",[36,279,280],{},"Parameters"," averages every parameter position first and then applies the formula. The moderator can also override the default averaging method and the final result before accepting.",[23,283],{"alt":284,"caption":285,"stem":286},"The Quadrant tab with participant dots and the averaged crosshair, above the Override, Averaging, and Override averaging method controls","Quadrant results","tutorial-parametric-results",{"title":66,"searchDepth":67,"depth":67,"links":288},[289,290,291],{"id":181,"depth":67,"text":182},{"id":234,"depth":67,"text":235},{"id":259,"depth":67,"text":260},"2026-11-02","Vote on two parameters at once, such as value and effort, and combine them into one estimate.","Voting with 2 parameters","\u002Fog\u002Ftutorial-parametric-voting.jpg",[297,298,162],"parametric estimation","two parameter voting",{},3,"\u002Ftutorials\u002Fparametric-voting",{"title":173,"description":293},{"loc":301,"lastmod":292},"parametric-voting","tutorials\u002Fen\u002Fparametric-voting","tutorial\u002Fparametric-voting","EhSG0Z-zoBeseXjyGKCs9c0MgMPBbErtVRUVNSYw8XU",{"id":309,"title":310,"body":311,"dateModified":292,"datePublished":72,"description":387,"extension":74,"heading":388,"image":389,"imageAlt":388,"keywords":390,"locale":81,"meta":392,"navigation":83,"order":393,"path":394,"section":86,"seo":395,"sitemap":396,"slug":397,"stem":398,"translationKey":399,"__hash__":400},"tutorials\u002Ftutorials\u002Fen\u002Fparametric-3-voting.md","Voting with 3+ parameters | Tutorials | Scrumpy Planning Poker",{"type":8,"value":312,"toc":382},[313,316,318,342,346,348,357,361,363,377],[11,314,315],{},"When one number is not enough, a parametric perspective can combine three, four, or more parameters with a formula and turn them into one story point result.",[15,317,182],{"id":181},[11,319,107,320,111,322,324,325,328,329,201,331,205,333,209,335,337,338,341],{},[36,321,187],{},[36,323,114],{}," dropdown and add as many parameters as the work needs with ",[36,326,327],{},"Add parameter",". Give each one a name, a ",[36,330,200],{},[36,332,204],{},[36,334,208],{},[36,336,212],{}," from the parameter names shown beside the fields, for example ",[215,339,340],{},"(p1 + sqrt(p2) + 2 + p3 + p4 + p5) \u002F 5",". The preview at the bottom shows every slider and the result your team will see.",[23,343],{"alt":344,"caption":230,"stem":345},"Perspective settings with the Parametric sequence, three parameters, and the formula","tutorial-parametric-3-configure",[15,347,235],{"id":234},[11,349,350,351,246,353,249,355,252],{},"During a session, each voter moves every parameter to the value that fits the work. The formula turns those positions into the result shown in large text with an ",[36,352,142],{},[36,354,138],{},[36,356,146],{},[23,358],{"alt":359,"caption":235,"stem":360},"The voting panel with one slider per parameter, the result, the deviation badge, and the Vote and Withdraw buttons","tutorial-parametric-3",[15,362,260],{"id":259},[11,364,365,366,369,370,372,373,277,375,281],{},"A perspective with three or more parameters adds a ",[36,367,368],{},"Radar"," tab instead of the two-parameter ",[36,371,266],{},": each parameter becomes a ray, and every participant gets one polygon, with a dotted polygon for the averaged positions. ",[36,374,276],{},[36,376,280],{},[23,378],{"alt":379,"caption":380,"stem":381},"The Radar tab with one polygon per participant and the dotted averaged polygon, above the Override, Averaging, and Override averaging method controls","Radar results","tutorial-parametric-3-results",{"title":66,"searchDepth":67,"depth":67,"links":383},[384,385,386],{"id":181,"depth":67,"text":182},{"id":234,"depth":67,"text":235},{"id":259,"depth":67,"text":260},"Estimate three or more parameters in one round and review how Scrumpy combines them.","Voting with 3+ parameters","\u002Fog\u002Ftutorial-parametric-3-voting.jpg",[297,391],"multi parameter voting",{},4,"\u002Ftutorials\u002Fparametric-3-voting",{"title":310,"description":387},{"loc":394,"lastmod":292},"parametric-3-voting","tutorials\u002Fen\u002Fparametric-3-voting","tutorial\u002Fparametric-3-voting","fTV72fdLB_C_c16A38yT1SKNnxYpSpu8ChC1rCI9608",{"id":402,"title":403,"body":404,"dateModified":292,"datePublished":72,"description":575,"extension":74,"heading":576,"image":577,"imageAlt":576,"keywords":578,"locale":81,"meta":581,"navigation":83,"order":582,"path":583,"section":86,"seo":584,"sitemap":585,"slug":586,"stem":587,"translationKey":588,"__hash__":589},"tutorials\u002Ftutorials\u002Fen\u002Fvoting-with-time.md","Voting with time | Tutorials | Scrumpy Planning Poker",{"type":8,"value":405,"toc":565},[406,409,413,420,424,428,431,436,439,444,447,453,458,461,464,469,473,479,484,488,491,521,526,545,550,560],[11,407,408],{},"Some teams find it easier to think in hours than in abstract story points. Scrumpy keeps the card, free-scale, or parameter estimate and can show the equivalent time beside it, so the team can estimate the way it works while the result still lands in days and hours. The time appears only when the perspective writes to a time-based board or a Time field, and the last section shows how to set that up.",[15,410,412],{"id":411},"set-the-conversion-from-your-project-history","Set the conversion from your project history",[11,414,415,416,419],{},"Open the perspective settings and find ",[36,417,418],{},"Story points to hours",". To choose the factor, look at a few recent completed work items: add up the time they actually took and divide it by the story points they were estimated at. Use that average (for example, 1 point = 8 hours) so the time estimate reflects how your team really works rather than a generic guess.",[23,421],{"alt":422,"caption":418,"stem":423},"Perspective settings with the Story points to hours field set to the project's conversion factor","tutorial-time-estimate-configure",[15,425,427],{"id":426},"vote-with-cards-a-free-scale-or-parameters","Vote with cards, a free scale, or parameters",[11,429,430],{},"The conversion works with every voting style.",[432,433,435],"h3",{"id":434},"cards","Cards",[11,437,438],{},"With cards, the result labels show each vote in the units the perspective writes: story points on a numeric board or a story points field, the duration on a time board or a Time field, and both when the target writes a time value next to the story points.",[23,440],{"alt":441,"caption":442,"stem":443},"A card voting result with story points and time labels and the Override field showing both","Card result","tutorial-time-estimate-cards",[432,445,110],{"id":446},"free-scale",[11,448,449,450,452],{},"With the free scale, the slider preview above ",[36,451,138],{}," shows story points on a numeric board or a story points field. A time board or a Time field shows the duration, and a Field target with both a story points field and a Time field shows both.",[23,454],{"alt":455,"caption":456,"stem":457},"The free scale slider with the selected story points and time above the Vote button","Free scale vote","tutorial-time-estimate-free-scale",[432,459,280],{"id":460},"parameters",[11,462,463],{},"With parameters, the calculated result below the sliders shows story points on a numeric board or a story points field. A time board or a Time field shows the duration, and a Field target with both a story points field and a Time field shows both.",[23,465],{"alt":466,"caption":467,"stem":468},"The parametric sliders with the calculated story points and time below them","Parametric vote","tutorial-time-estimate-parameters",[15,470,472],{"id":471},"read-the-result","Read the result",[11,474,475,476,478],{},"When the session completes, the result chart, the vote list, and the moderator's ",[36,477,46],{}," field show the result in the units the perspective writes. On a time board or a Time field that is the duration; when the target writes both story points and time, they appear together, and choosing a different override updates the time beside it.",[23,480],{"alt":481,"caption":482,"stem":483},"A free scale result chart with time labels and an Override field showing the story points and time","Completed result","tutorial-time-estimate-free-scale-result",[15,485,487],{"id":486},"make-the-time-estimate-reach-jira","Make the time estimate reach Jira",[11,489,490],{},"Scrumpy shows the time value only when the perspective writes it to a Jira time field. Set up one of these before you vote.",[11,492,493,496,497,500,501,504,505,508,509,512,513,516,517,520],{},[36,494,495],{},"Use a time field as the target."," Set ",[36,498,499],{},"Estimation target"," to ",[36,502,503],{},"Field",", then choose a Jira time field under ",[36,506,507],{},"Time field",", for example ",[36,510,511],{},"Original estimate",". The ",[36,514,515],{},"Story points field"," can stay ",[36,518,519],{},"None"," when the team only wants the time written.",[23,522],{"alt":523,"caption":524,"stem":525},"The Estimation target set to Field with the Time field set to Original estimate","Time field target","tutorial-time-estimate-configure-field",[11,527,528,496,531,500,533,536,537,540,541,544],{},[36,529,530],{},"Use the board's time estimate.",[36,532,499],{},[36,534,535],{},"Default",", pick the board the team plans with, and then open ",[36,538,539],{},"Configure this board's estimation settings"," in Jira and set the board's estimation method to a time statistic such as ",[36,542,543],{},"Original time estimate",". With the default target, Scrumpy sends the result to the board and the board decides which field stores it.",[23,546],{"alt":547,"caption":548,"stem":549},"The Estimation target set to Default with the board estimation statistic set to Time Estimate","Default board target","tutorial-time-estimate-configure-board",[11,551,552,553,556,557,559],{},"In the Jira board settings, set the ",[36,554,555],{},"Estimation method"," to a time statistic such as ",[36,558,543],{},".",[23,561],{"alt":562,"caption":563,"stem":564},"The Jira board estimation method set to Original time estimate","Jira board estimation","tutorial-configure-time-estimate-board-jira",{"title":66,"searchDepth":67,"depth":67,"links":566},[567,568,573,574],{"id":411,"depth":67,"text":412},{"id":426,"depth":67,"text":427,"children":569},[570,571,572],{"id":434,"depth":300,"text":435},{"id":446,"depth":300,"text":110},{"id":460,"depth":300,"text":280},{"id":471,"depth":67,"text":472},{"id":486,"depth":67,"text":487},"Estimate effort in hours and days instead of story points, with time cards, a time field and duration results.","Voting with time","\u002Fog\u002Ftutorial-voting-with-time.jpg",[579,580,80],"time estimation","hour estimates",{},5,"\u002Ftutorials\u002Fvoting-with-time",{"title":403,"description":575},{"loc":583,"lastmod":292},"voting-with-time","tutorials\u002Fen\u002Fvoting-with-time","tutorial\u002Fvoting-with-time","CNFPsWyj97bFnrQs4SftgRf5YI5g1rKBuq3Li3rBQ-8",{"id":591,"title":592,"body":593,"dateModified":695,"datePublished":696,"description":697,"extension":74,"heading":698,"image":699,"imageAlt":698,"keywords":700,"locale":81,"meta":704,"navigation":83,"order":705,"path":706,"section":86,"seo":707,"sitemap":708,"slug":709,"stem":710,"translationKey":711,"__hash__":712},"tutorials\u002Ftutorials\u002Fen\u002Fvoting-with-tshirts.md","Voting with T-shirts | Tutorials | Scrumpy Planning Poker",{"type":8,"value":594,"toc":690},[595,598,602,616,619,628,633,637,640,656,667,672,678,682,685],[11,596,597],{},"T-shirt sizes keep a session short: voters pick a size instead of arguing over a number. Scrumpy turns the size into a story point value you control, so the estimate still fits the team's scale and can be written to Jira.",[15,599,601],{"id":600},"set-the-sizes-and-their-story-points","Set the sizes and their story points",[11,603,604,605,608,609,611,612,615],{},"Open the perspective settings and choose ",[36,606,607],{},"T-Shirt"," in ",[36,610,114],{},". Tick the sizes the team uses under ",[36,613,614],{},"Available cards",". Only the ticked cards appear during voting, so a short list keeps the session focused.",[11,617,618],{},"Each card has a story point value beside it. Change a number to match the team's scale. The values must grow from the first card to the last, so edit the list from the bottom upward when you need wider gaps. These values are the story points Scrumpy uses for the result and for Jira.",[11,620,621,622,624,625,559],{},"When ",[36,623,418],{}," is set in the same tab and the perspective writes a time value, the result also shows the converted duration beside the size, for example ",[36,626,627],{},"1 sp · 1 day 2 hours · M",[23,629],{"alt":630,"caption":631,"stem":632},"The Available cards list for a T-shirt perspective with the story points beside each size","T-shirt cards and story points","tutorial-tshirt-configure",[15,634,636],{"id":635},"write-the-result-to-one-or-two-jira-fields","Write the result to one or two Jira fields",[11,638,639],{},"A T-shirt vote can update two Jira fields:",[641,642,643,650],"ul",{},[644,645,263,646,649],"li",{},[36,647,648],{},"story points field",", using the story point value configured for the chosen size (for example, S = 10).",[644,651,263,652,655],{},[36,653,654],{},"T-shirt field",", with the size label (for example, S).",[11,657,658,659,500,661,663,664,666],{},"Set ",[36,660,499],{},[36,662,503],{},", then choose the fields you want. Choose both to update both. Leave a field as ",[36,665,519],{}," when the team does not use it.",[23,668],{"alt":669,"caption":670,"stem":671},"The Estimation target set to Field with the Story points field and the T-shirt field","Story points and T-shirt fields","tutorial-tshirt-configure-field",[11,673,674,675,677],{},"With ",[36,676,535],{}," as the target, the accepted estimate goes to the board's estimation field as the mapped story point value, and the T-shirt field can still receive the size label when it is set.",[15,679,681],{"id":680},"vote-with-the-size-cards","Vote with the size cards",[11,683,684],{},"When the moderator starts a session, voters see only the sizes you ticked. Each voter taps a card, and the panel shows who has voted. The moderator pauses, resumes, or completes the session as usual. When the estimate is accepted, Scrumpy writes the size label, the mapped story points, or both, depending on the fields you set.",[23,686],{"alt":687,"caption":688,"stem":689},"The voting panel with the T-shirt size cards","Voting with T-shirt cards","tutorial-tshirt",{"title":66,"searchDepth":67,"depth":67,"links":691},[692,693,694],{"id":600,"depth":67,"text":601},{"id":635,"depth":67,"text":636},{"id":680,"depth":67,"text":681},"2026-10-31","2026-10-29","Size work with T-shirt cards, optionally mapped to story points and time, directly in your Jira board.","Voting with T-shirts","\u002Fog\u002Ftutorial-voting-with-tshirts.jpg",[701,702,703],"t-shirt sizing","t shirt estimation","agile sizing",{},6,"\u002Ftutorials\u002Fvoting-with-tshirts",{"title":592,"description":697},{"loc":706,"lastmod":695},"voting-with-tshirts","tutorials\u002Fen\u002Fvoting-with-tshirts","tutorial\u002Fvoting-with-tshirts","-PvkZpXyh5ZpLS6tSG4ept2o2G7zNhCI0u_pSGBE3AE",{"id":714,"title":715,"body":716,"dateModified":696,"datePublished":696,"description":826,"extension":74,"heading":817,"image":827,"imageAlt":817,"keywords":828,"locale":81,"meta":832,"navigation":83,"order":833,"path":834,"section":86,"seo":835,"sitemap":836,"slug":837,"stem":838,"translationKey":839,"__hash__":840},"tutorials\u002Ftutorials\u002Fen\u002Fvoting-with-custom-cards.md","Voting with custom cards | Tutorials | Scrumpy Planning Poker",{"type":8,"value":717,"toc":819},[718,721,725,748,753,756,760,768,772,776,779,785,789,799,804,807,811,814],[11,719,720],{},"You can re-brand the whole voting board to match the team's standards: the card values, the titles, the story points on a T-shirt deck, and the artwork. Voters then see a deck that speaks the team's language instead of the built-in one.",[15,722,724],{"id":723},"every-card-set-is-customizable","Every card set is customizable",[11,726,727,728,731,732,731,735,731,738,731,741,744,745,747],{},"Titles and custom images work on every card-based sequence: ",[36,729,730],{},"Regular",", ",[36,733,734],{},"Fibonacci",[36,736,737],{},"Tens",[36,739,740],{},"Fingers",[36,742,743],{},"Dice",", and ",[36,746,607],{},". Pick the sequence first, then change its titles, choose the active cards, and upload artwork. The same steps apply to each set.",[11,749,750,752],{},[36,751,607],{}," adds one more setting. Its cards are size labels instead of numbers, so each size also has an editable story point value. The other card sets already carry a fixed number on every card, so they do not show a story point field.",[11,754,755],{},"This tutorial uses a T-shirt perspective because it shows both customizations, but you can follow the title and image steps on any card set.",[15,757,759],{"id":758},"start-with-a-t-shirt-perspective","Start with a T-shirt perspective",[11,761,604,762,608,764,611,766,615],{},[36,763,607],{},[36,765,114],{},[36,767,614],{},[23,769],{"alt":770,"caption":631,"stem":771},"The Available cards list for a T-shirt perspective with the selected sizes and their story points","tutorial-custom-cards-configure",[15,773,775],{"id":774},"change-the-titles-and-the-story-points-on-t-shirt","Change the titles, and the story points on T-Shirt",[11,777,778],{},"Each card has a title field beside its preview. Replace the built-in title with the team's own name for that card. A custom title must contain at least one letter and must be unique within the sequence; the small reset control restores the built-in title. This works the same on every card set.",[11,780,781,782,784],{},"On ",[36,783,607],{},", each size also has a story point value. Set the numbers so they grow from the first card to the last, and edit from the bottom upward when you need wider gaps. These values are what Scrumpy uses for the result and for the Jira story points field. The other card sets keep their fixed numeric value and show no story point field.",[15,786,788],{"id":787},"upload-custom-card-images","Upload custom card images",[11,790,791,792,794,795,798],{},"Click any card preview in ",[36,793,614],{}," or ",[36,796,797],{},"Available extra cards"," to open the upload dialog. This works on every card set. Choose a PNG or JPG image up to 293 kB with a width to height ratio of 1:1.5, for example 400 by 600 pixels. The same dialog removes a custom image and restores the built-in artwork.",[23,800],{"alt":801,"caption":802,"stem":803},"The Upload card image dialog with the file browser and the PNG or JPG limits","Upload card image","tutorial-custom-cards-configure-images",[11,805,806],{},"Custom images are kept per card and per sequence, so the same value in two sequences can carry different artwork. Only people who can manage the space can upload or remove an image, and the image belongs to this space.",[15,808,810],{"id":809},"vote-with-the-custom-board","Vote with the custom board",[11,812,813],{},"When a session runs, voters see the custom titles and artwork on the cards they can pick. A custom title also appears in the card tooltip and replaces the value on the minimalistic card visuals. The moderator starts, pauses, resumes, or completes the session as usual, and the accepted estimate uses the story point value behind the chosen card.",[23,815],{"alt":816,"caption":817,"stem":818},"The voting panel with custom titles and custom card artwork","Voting with custom cards","tutorial-custom-cards",{"title":66,"searchDepth":67,"depth":67,"links":820},[821,822,823,824,825],{"id":723,"depth":67,"text":724},{"id":758,"depth":67,"text":759},{"id":774,"depth":67,"text":775},{"id":787,"depth":67,"text":788},{"id":809,"depth":67,"text":810},"Build your own planning poker deck: custom card titles, images and story point values for each card.","\u002Fog\u002Ftutorial-voting-with-custom-cards.jpg",[829,830,831],"custom cards","planning poker deck","estimation cards",{},7,"\u002Ftutorials\u002Fvoting-with-custom-cards",{"title":715,"description":826},{"loc":834,"lastmod":696},"voting-with-custom-cards","tutorials\u002Fen\u002Fvoting-with-custom-cards","tutorial\u002Fvoting-with-custom-cards","ZmpaQYUlevOG4WnHeCljXE5_e-LcTChoQmaCOffDKgs",{"id":842,"title":843,"body":844,"dateModified":292,"datePublished":292,"description":990,"extension":74,"heading":991,"image":992,"imageAlt":991,"keywords":993,"locale":81,"meta":997,"navigation":83,"order":998,"path":999,"section":86,"seo":1000,"sitemap":1001,"slug":1002,"stem":1003,"translationKey":1004,"__hash__":1005},"tutorials\u002Ftutorials\u002Fen\u002Festimation-log.md","Reading the estimation log | Tutorials | Scrumpy Planning Poker",{"type":8,"value":845,"toc":982},[846,849,853,868,871,876,883,887,890,934,940,946,950,953,957,960,964,971,975],[11,847,848],{},"Every time a moderator accepts an estimate, Scrumpy records it in the estimation log for that work item. The log keeps the sizing decisions of the last 90 days, so you can see how an estimate changed over time, which perspective produced each value, and who took part.",[15,850,852],{"id":851},"find-the-log-on-a-work-item","Find the log on a work item",[11,854,855,856,859,860,863,864,867],{},"Open the work item in Jira, expand the ",[36,857,858],{},"Activity"," area, open ",[36,861,862],{},"Apps",", and choose ",[36,865,866],{},"Estimation log",". The log lists the accepted estimates for the work item, newest first.",[11,869,870],{},"If the space has a password, enter it first: the log asks for the space password before it shows any entries. Scrumpy also checks that you can open the work item in Jira, so a work item hidden from you by Jira issue-level security shows no history.",[23,872],{"alt":873,"caption":874,"stem":875},"The estimation log on a work item","The estimation log","tutorial-estimation-log",[11,877,878,879,882],{},"A space administrator can hide the log by hiding both the Scrumpy panel on work items and the ",[36,880,881],{},"Estimations"," page in space settings. While either one is shown, the log stays available.",[15,884,886],{"id":885},"read-an-entry","Read an entry",[11,888,889],{},"Each entry is one accepted estimate:",[641,891,892,898,907,913,919,928],{},[644,893,894,897],{},[36,895,896],{},"Moderator",": the avatar of the person who accepted the estimate",[644,899,900,903,904],{},[36,901,902],{},"Completion",": how many of the required voters had voted, such as ",[36,905,906],{},"100% of required voters",[644,908,909,912],{},[36,910,911],{},"Perspective",": which estimation perspective produced the value",[644,914,915,918],{},[36,916,917],{},"Time",": when the estimate was accepted, in your Jira timezone",[644,920,921,924,925],{},[36,922,923],{},"Duration",": how long the vote took, for example ",[36,926,927],{},"for 4 minutes",[644,929,930,933],{},[36,931,932],{},"Result",": the accepted value in a badge, then every vote in the deck's labels and the people who cast them",[11,935,936,937,559],{},"The result badge is green when the accepted value matches the computed average. If the moderator chose a different value before accepting, the badge is yellow and hovering it shows ",[36,938,939],{},"Overridden by the moderator",[11,941,942,943,945],{},"Values follow the perspective: story points carry the ",[36,944,142],{}," suffix, a T-shirt perspective shows the size labels, and a time perspective shows a work-day duration.",[15,947,949],{"id":948},"move-through-the-history","Move through the history",[11,951,952],{},"The log shows 5 entries per page by default. Use the page numbers at the bottom to move through older estimates, and the selector beside them to show 5, 10, 15, or 20 entries per page. Changing the page size returns you to page one. The order never changes: the most recent accepted estimate is always at the top.",[15,954,956],{"id":955},"watch-the-log-during-a-session","Watch the log during a session",[11,958,959],{},"When someone accepts an estimate for the work item while the log is open, the new entry appears at the top without a reload. If you are reading an older page, the log returns to page one so the new entry is visible. In a password-protected space, live updates start after you enter the space password.",[15,961,963],{"id":962},"see-the-trend-across-the-space","See the trend across the space",[11,965,966,967,970],{},"The estimation log is per work item. To see the whole space, open ",[36,968,969],{},"Space settings > Dashboard",", where accepted estimates are grouped into charts by perspective and by day, with the average certainty, variation, voting time, and number of voters. Use the range selector to focus on the last weeks or on all time.",[15,972,974],{"id":973},"know-how-long-the-history-stays","Know how long the history stays",[11,976,977,978,981],{},"Entries are kept for three months (90 days), then removed automatically. A space owner can clear every estimation log entry for the space at once from the space settings ",[36,979,980],{},"Dashboard"," tab; that action cannot be undone. Archiving a planning session to Confluence keeps its estimates on a Confluence page beyond the 90 days.",{"title":66,"searchDepth":67,"depth":67,"links":983},[984,985,986,987,988,989],{"id":851,"depth":67,"text":852},{"id":885,"depth":67,"text":886},{"id":948,"depth":67,"text":949},{"id":955,"depth":67,"text":956},{"id":962,"depth":67,"text":963},{"id":973,"depth":67,"text":974},"Read the estimation log: what is recorded for each accepted estimate and how long the history is kept.","Reading the estimation log","\u002Fog\u002Ftutorial-estimation-log.jpg",[994,995,996],"estimation log","estimation history","jira reporting",{},8,"\u002Ftutorials\u002Festimation-log",{"title":843,"description":990},{"loc":999,"lastmod":292},"estimation-log","tutorials\u002Fen\u002Festimation-log","tutorial\u002Festimation-log","gvxokZmR6GM9dzZGhZslUowlV8TY17qXctdhUNS8IHA",{"id":1007,"title":1008,"body":1009,"dateModified":1115,"datePublished":292,"description":1116,"extension":74,"heading":1117,"image":1118,"imageAlt":1117,"keywords":1119,"locale":81,"meta":1123,"navigation":83,"order":1124,"path":1125,"section":86,"seo":1126,"sitemap":1127,"slug":1128,"stem":1129,"translationKey":1130,"__hash__":1131},"tutorials\u002Ftutorials\u002Fen\u002Fcreating-a-planning-session.md","Creating a planning session | Tutorials | Scrumpy Planning Poker",{"type":8,"value":1010,"toc":1109},[1011,1014,1018,1036,1040,1051,1056,1060,1063,1082,1089,1093,1096,1099,1104],[11,1012,1013],{},"In Scrum, a planning session is the grooming or refinement session: the regular time the team sets aside to discuss upcoming work items and estimate them together. Scrumpy keeps the session, its work items, and the team's estimation perspectives in one place, so the discussion and the estimates stay together.",[15,1015,1017],{"id":1016},"open-the-planning-sessions-page","Open the planning sessions page",[11,1019,1020,1021,1024,1025,1028,1029,1031,1032,1035],{},"Go to the space page and open the ",[36,1022,1023],{},"Refinement\u002Fgrooming"," tab. A moderator presses ",[36,1026,1027],{},"Create"," above the session tabs, then gives the session a name, a short description, and a schedule. Use ",[36,1030,730],{}," for a start time plus a duration such as 30 minutes, or ",[36,1033,1034],{},"Long lasting"," when the session has a specific end time. The planned time is the refinement window, and the header shows how much of it is left while the team estimates.",[15,1037,1039],{"id":1038},"add-the-work-items","Add the work items",[11,1041,1042,1043,1046,1047,1050],{},"Press ",[36,1044,1045],{},"Add from filter",", choose a saved Jira filter, tick the work items you want, and press ",[36,1048,1049],{},"Add",". A filter is the quickest way to bring in a backlog slice, for example the next sprint's stories or a saved query for defects. You can add more work items later, and the same filter can be reused for the next session.",[23,1052],{"alt":1053,"caption":1054,"stem":1055},"The Add work items from filter dialog with a saved filter and ten work items selected","Add work items from a filter","tutorial-planning-add-from-filter",[15,1057,1059],{"id":1058},"give-each-estimation-style-a-perspective","Give each estimation style a perspective",[11,1061,1062],{},"Each perspective is a column in the planning table, and the same work item can be estimated in every one of them. This session shows three perspectives:",[641,1064,1065,1070,1076],{},[644,1066,1067,1069],{},[36,1068,917],{}," uses a free scale and writes the result to a board that estimates in time.",[644,1071,1072,1075],{},[36,1073,1074],{},"Scrum"," uses Fibonacci cards, limited here to 1, 2, 3 and 5, plus the infinity and coffee cards.",[644,1077,1078,1081],{},[36,1079,1080],{},"Bugs"," uses T-shirt sizes.",[11,1083,1084,1085,1088],{},"Use ",[36,1086,1087],{},"Visible perspectives"," to hide the perspectives the team does not need for this session. The choice belongs to the session, so the table stays focused on the work at hand.",[15,1090,1092],{"id":1091},"estimate-one-work-item-or-many","Estimate one work item or many",[11,1094,1095],{},"Work through the table one work item at a time, or tick several work items and use the actions above the table to start, pause, resume, complete, accept, or cancel voting for all of them. The work item you select in presenter mode opens in the panel on the right, where the team votes with the controls of the active perspective.",[11,1097,1098],{},"The example below has all ten work items selected, the sessions for Time, Scrum, and Bugs started and then paused, and the first work item open in the Scrum panel. From here the team can estimate the next work item, resume the sessions, or complete them in bulk when the discussion is over.",[23,1100],{"alt":1101,"caption":1102,"stem":1103},"The planning session with ten work items, three perspectives, all rows selected, sessions paused, and the selected work item's card panel open","A planning session with three perspectives","tutorial-planning-session",[23,1105],{"alt":1106,"caption":1107,"stem":1108},"The selected work item's card voting panel with the session paused","The selected work item's voting panel","tutorial-planning-voting-panel",{"title":66,"searchDepth":67,"depth":67,"links":1110},[1111,1112,1113,1114],{"id":1016,"depth":67,"text":1017},{"id":1038,"depth":67,"text":1039},{"id":1058,"depth":67,"text":1059},{"id":1091,"depth":67,"text":1092},"2026-11-21","Create a planning session in Jira, add work items and move from a backlog to accepted estimates.","Creating a planning session","\u002Fog\u002Ftutorial-creating-a-planning-session.jpg",[1120,1121,1122],"planning session","sprint planning","jira backlog",{},9,"\u002Ftutorials\u002Fcreating-a-planning-session",{"title":1008,"description":1116},{"loc":1125,"lastmod":1115},"creating-a-planning-session","tutorials\u002Fen\u002Fcreating-a-planning-session","tutorial\u002Fcreating-a-planning-session","w-hJTeMuUDnb3c1VJk3ZNG-EQYYx6Du2uCmvpC0oI0o",{"id":1133,"title":1134,"body":1135,"dateModified":292,"datePublished":292,"description":1223,"extension":74,"heading":1224,"image":1225,"imageAlt":1224,"keywords":1226,"locale":81,"meta":1230,"navigation":83,"order":1231,"path":1232,"section":86,"seo":1233,"sitemap":1234,"slug":1235,"stem":1236,"translationKey":1237,"__hash__":1238},"tutorials\u002Ftutorials\u002Fen\u002Fauditing-and-dashboards.md","Auditing and dashboards | Tutorials | Scrumpy Planning Poker",{"type":8,"value":1136,"toc":1217},[1137,1140,1144,1150,1153,1157,1164,1168,1174,1184,1188,1192,1201,1205,1210,1214],[11,1138,1139],{},"When you need to know what happened in a space, you do not have to ask around. Space settings keeps two audit logs and the full dashboard for the space. You need permission to manage the space in Jira to open them, and Scrumpy checks that permission again when the data loads.",[15,1141,1143],{"id":1142},"follow-a-voting-session-from-start-to-finish","Follow a voting session from start to finish",[11,1145,263,1146,1149],{},[36,1147,1148],{},"Voting audit"," tab lists every significant voting event in the space, newest first: a session started, a vote cast or withdrawn, a pause or resume, a completion, the team estimate, an accepted estimate, a change to the required voters, a reminder, and the async voting deadline.",[11,1151,1152],{},"Each row shows when the event happened, the work item type and key, the perspective, who did it, and what happened. Click a work item key to open the work item in a dialog without leaving the page.",[23,1154],{"alt":1155,"caption":1148,"stem":1156},"The Voting audit tab with recent voting events and the actor for each event","tutorial-voting-audit",[11,1158,1159,1160,1163],{},"Use the search field for a work item key, a perspective, or an event description, then click ",[36,1161,1162],{},"Search",". Choose 15, 30, 45, or 60 rows per page. You only see events for work items you can open in Jira; hidden work items are left out and are not counted.",[15,1165,1167],{"id":1166},"see-who-changed-the-settings","See who changed the settings",[11,1169,263,1170,1173],{},[36,1171,1172],{},"Configuration audit"," tab records every change to the space permissions and to the perspective settings. It covers the voter and moderator lists, the password, page visibility, the Confluence space, and every perspective setting. A perspective added, renamed, or removed also appears here.",[11,1175,1176,1177,794,1180,1183],{},"Each row shows who made the change, which perspective it belongs to, what changed, and when. The description reads like ",[36,1178,1179],{},"Certainty enabled",[36,1181,1182],{},"Active cards changed for Fibonacci",", so you can see the exact difference without opening the setting.",[23,1185],{"alt":1186,"caption":1172,"stem":1187},"The Configuration audit tab with the actor, the perspective, and the change description","tutorial-config-audit",[15,1189,1191],{"id":1190},"visualize-the-voting-activity","Visualize the voting activity",[11,1193,263,1194,1196,1197,1200],{},[36,1195,980],{}," tab in Space settings turns accepted sessions into charts for the space. It shows the total votes and estimates per perspective, the average certainty and variation, the average active and paused time, and the same numbers per day. Use the range selector to switch between 1, 2, 4, or 8 weeks and ",[36,1198,1199],{},"All time","; the choice is remembered in this browser tab.",[23,1202],{"alt":1203,"caption":980,"stem":1204},"The Dashboard tab with the range selector and the voting activity charts","tutorial-dashboard",[11,1206,263,1207,1209],{},[36,1208,980],{}," tab on the Estimations page is a lighter live view. It shows active sessions, unique voters, and sessions by state per perspective, plus the people voting right now. It has no time filter.",[15,1211,1213],{"id":1212},"keep-the-history","Keep the history",[11,1215,1216],{},"Voting audit entries, configuration audit entries, and accepted sessions are kept for 90 days, then removed automatically. Only the space owner can clear an audit log or the estimation log from these tabs. A confirmation appears first, and those deletions cannot be undone.",{"title":66,"searchDepth":67,"depth":67,"links":1218},[1219,1220,1221,1222],{"id":1142,"depth":67,"text":1143},{"id":1166,"depth":67,"text":1167},{"id":1190,"depth":67,"text":1191},{"id":1212,"depth":67,"text":1213},"Use the voting audit and dashboards to see participation, vote changes and estimation trends over time.","Auditing and dashboards","\u002Fog\u002Ftutorial-auditing-and-dashboards.jpg",[1227,1228,1229],"voting audit","estimation dashboard","agile metrics",{},10,"\u002Ftutorials\u002Fauditing-and-dashboards",{"title":1134,"description":1223},{"loc":1232,"lastmod":292},"auditing-and-dashboards","tutorials\u002Fen\u002Fauditing-and-dashboards","tutorial\u002Fauditing-and-dashboards","1Bqy4Uocd5zeK1r8FAdqEC_Xy1gEVcFBwu86ozbXlB8",{"id":1240,"title":1241,"body":1242,"dateModified":292,"datePublished":292,"description":1330,"extension":74,"heading":1331,"image":1332,"imageAlt":1331,"keywords":1333,"locale":81,"meta":1337,"navigation":83,"order":1338,"path":1339,"section":86,"seo":1340,"sitemap":1341,"slug":1342,"stem":1343,"translationKey":1344,"__hash__":1345},"tutorials\u002Ftutorials\u002Fen\u002Fbulk-voting.md","Bulk voting in a planning session | Tutorials | Scrumpy Planning Poker",{"type":8,"value":1243,"toc":1324},[1244,1247,1251,1267,1272,1276,1290,1295,1299,1302,1306,1319],[11,1245,1246],{},"A planning session is the team's grooming or refinement meeting. Its table is a spreadsheet for estimation: one row per work item, one column per perspective, and one estimate cell for every pair.",[15,1248,1250],{"id":1249},"fill-the-table-in-bulk-voting","Fill the table in Bulk voting",[11,1252,1253,1254,1257,1258,1260,1261,1263,1264,1266],{},"Switch the session to ",[36,1255,1256],{},"Bulk voting",". Every started session shows its control directly in the table: a card selector for ",[36,1259,1074],{},", a T-shirt selector for ",[36,1262,1080],{},", and a number field for ",[36,1265,917],{},". Choose a value and the vote is cast for that work item and perspective, without opening the work item.",[23,1268],{"alt":1269,"caption":1270,"stem":1271},"The planning session in Bulk voting with card, size, and number controls in the table","Bulk voting in the planning table","tutorial-bulk-voting-table",[15,1273,1275],{"id":1274},"vote-with-buckets","Vote with buckets",[11,1277,1278,1279,1281,1282,1285,1286,1289],{},"Select the ",[36,1280,1074],{}," perspective row and open the ",[36,1283,1284],{},"Bucket"," tab. Each card is a bucket. Drag a work item under the card that fits, or drop it under ",[36,1287,1288],{},"Unassigned"," to withdraw its vote. The bucket view shows the same votes as the table, grouped by card.",[23,1291],{"alt":1292,"caption":1293,"stem":1294},"The Bucket voting tab with work items placed under the Scrum cards","Bucket voting","tutorial-bulk-voting-buckets",[15,1296,1298],{"id":1297},"it-does-not-matter-where-the-vote-is-cast","It does not matter where the vote is cast",[11,1300,1301],{},"Participants can vote from the work item's ad-hoc panel, from the planning table, or from the Bucket tab by dragging. All three write the same vote for the work item and perspective, so the moderator reviews the same result everywhere. From the planning table the moderator can start, pause, resume, complete, cancel, or accept sessions in bulk.",[15,1303,1305],{"id":1304},"accept-the-estimates","Accept the estimates",[11,1307,1308,1309,1311,1312,1315,1316,1318],{},"Select all work items, choose ",[36,1310,1074],{}," in the perspective selector, and press ",[36,1313,1314],{},"Complete",". Then press ",[36,1317,42],{},". Scrumpy writes each accepted estimate to the Jira field the perspective targets, and the planning table shows the accepted value in the Scrum column.",[23,1320],{"alt":1321,"caption":1322,"stem":1323},"The planning session after accepting the Scrum estimates, with the values in the table","Accepted estimates in the planning table","tutorial-bulk-voting-accepted",{"title":66,"searchDepth":67,"depth":67,"links":1325},[1326,1327,1328,1329],{"id":1249,"depth":67,"text":1250},{"id":1274,"depth":67,"text":1275},{"id":1297,"depth":67,"text":1298},{"id":1304,"depth":67,"text":1305},"Estimate a whole backlog in one table, edit several work items at once and accept results in bulk.","Bulk voting in a planning session","\u002Fog\u002Ftutorial-bulk-voting.jpg",[1334,1335,1336],"bulk voting","backlog estimation","planning poker table",{},11,"\u002Ftutorials\u002Fbulk-voting",{"title":1241,"description":1330},{"loc":1339,"lastmod":292},"bulk-voting","tutorials\u002Fen\u002Fbulk-voting","tutorial\u002Fbulk-voting","UUL82KHZSZCCWLnlVgMUC8e-CH2FSfRs8qSJXyLUpIU",{"id":1347,"title":1348,"body":1349,"dateModified":1647,"datePublished":292,"description":1648,"extension":74,"heading":1649,"image":1650,"imageAlt":1649,"keywords":1651,"locale":81,"meta":1655,"navigation":83,"order":1656,"path":1657,"section":86,"seo":1658,"sitemap":1659,"slug":1660,"stem":1661,"translationKey":1662,"__hash__":1663},"tutorials\u002Ftutorials\u002Fen\u002Faffinity-and-dot-ranking.md","Affinity and Dot ranking | Tutorials | Scrumpy Planning Poker",{"type":8,"value":1350,"toc":1636},[1351,1354,1370,1374,1392,1395,1399,1417,1423,1439,1444,1448,1456,1459,1468,1473,1477,1496,1503,1520,1523,1528,1532,1548,1551,1555,1565,1574,1578,1600,1608,1612,1617,1620,1624,1627],[11,1352,1353],{},"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,1355,1356,1357,1359,1360,731,1362,744,1364,1366,1367,1369],{},"This tutorial continues the setup from ",[36,1358,1117],{},": ten work items, the ",[36,1361,917],{},[36,1363,1074],{},[36,1365,1080],{}," perspectives, and three participants. It uses the ",[36,1368,1074],{}," perspective.",[15,1371,1373],{"id":1372},"open-the-ranking-panel","Open the ranking panel",[11,1375,1376,1377,1379,1380,1382,1383,731,1386,744,1389,1391],{},"Open the planning session and switch the edit mode to ",[36,1378,1256],{},". A row for each perspective appears below the work items. Select the radio beside ",[36,1381,1074],{},". The panel on the right opens with ",[36,1384,1385],{},"Affinity",[36,1387,1388],{},"Dot",[36,1390,1284],{}," tabs, the perspective title and description, a settings gear, your role badge, and the sound bell.",[11,1393,1394],{},"Only voters can rank. A guest sees the same tables read-only.",[15,1396,1398],{"id":1397},"rank-with-affinity","Rank with Affinity",[11,1400,1401,1402,1404,1405,1408,1409,1412,1413,1416],{},"Open the ",[36,1403,1385],{}," 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. ",[36,1406,1407],{},"My rank"," is your position, ",[36,1410,1411],{},"Deviation"," is your distance from the agreed position, and ",[36,1414,1415],{},"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,1418,1419,1420,1422],{},"Every listed work item takes part, even when you never moved it. Below the table you see the participants who have ranked. ",[36,1421,146],{}," removes your ranking.",[11,1424,1425,1426,794,1429,1432,1433,1435,1436,1438],{},"A moderator chooses the agreed position with ",[36,1427,1428],{},"Mean rank",[36,1430,1431],{},"Median rank"," beside the perspective title. ",[36,1434,1428],{}," averages the positions, and ",[36,1437,1431],{}," uses the middle position.",[23,1440],{"alt":1441,"caption":1442,"stem":1443},"The Affinity tab after three participants ranked ten work items","The Affinity panel with three participants","tutorial-affinity-ranking",[15,1445,1447],{"id":1446},"rank-with-dots","Rank with dots",[11,1449,1401,1450,1452,1453,1455],{},[36,1451,1388],{}," 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 ",[36,1454,1415],{}," column shows that total.",[11,1457,1458],{},"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,1460,1461,1463,1464,1467],{},[36,1462,146],{}," removes all of your dots. The ",[36,1465,1466],{},"Results"," tab of both rankings shows a chart: the agreed position for Affinity and the dot count for Dot.",[23,1469],{"alt":1470,"caption":1471,"stem":1472},"The Dot tab after three participants spent between five and eight dots each","The Dot panel with three participants","tutorial-dot-ranking",[15,1474,1476],{"id":1475},"rank-the-bucket-table","Rank the bucket table",[11,1478,1401,1479,1481,1482,1485,1486,794,1489,1492,1493,1495],{},[36,1480,1284],{}," tab. The dropdown beside the perspective title reads ",[36,1483,1484],{},"No ranking"," by default. Choose ",[36,1487,1488],{},"Affinity ranking",[36,1490,1491],{},"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 ",[36,1494,1415],{}," column. The card rows keep their configured order.",[11,1497,1498,1499,1502],{},"Work items with the same rank can be reordered inside the same card row or inside ",[36,1500,1501],{},"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:",[641,1504,1505,1511,1514],{},[644,1506,1507,1508,1510],{},"Drop onto ",[36,1509,1501],{}," to clear the dropped work item and the better-ranked carded work items above it.",[644,1512,1513],{},"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.",[644,1515,1516,1517,1519],{},"Drop onto a worse card, lower in the table, or out of ",[36,1518,1501],{},", to move the dropped work item and the worse-ranked work items that land under that card.",[11,1521,1522],{},"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.",[23,1524],{"alt":1525,"caption":1526,"stem":1527},"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,1529,1531],{"id":1530},"changing-the-ranking-clears-the-bucket-votes","Changing the ranking clears the bucket votes",[11,1533,1534,1535,500,1537,794,1539,1541,1542,1544,1545,1547],{},"Switching from ",[36,1536,1484],{},[36,1538,1488],{},[36,1540,1491],{},", or between the two, resets the votes in the Bucket table and returns every work item to ",[36,1543,1501],{},". The change appears at once, and if it cannot be saved, the previous ranking and votes return. Switching back to ",[36,1546,1484],{}," keeps the votes you have.",[11,1549,1550],{},"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,1552,1554],{"id":1553},"sync-the-rankings-with-jira","Sync the rankings with Jira",[11,1556,1557,1560,1561,1564],{},[36,1558,1559],{},"Affinity:"," only a moderator sees the ",[36,1562,1563],{},"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,1566,1567,1570,1571,1573],{},[36,1568,1569],{},"Dots:"," every participant presses the ",[36,1572,1563],{}," 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,1575,1577],{"id":1576},"reset-a-ranking","Reset a ranking",[641,1579,1580,1585,1594],{},[644,1581,1582,1584],{},[36,1583,146],{}," removes your own ranking or all of your dots.",[644,1586,1587,1590,1591,1593],{},[36,1588,1589],{},"Clear rankings",", the delete icon beside ",[36,1592,146],{},", is for a moderator and deletes the rankings for everyone on that tab.",[644,1595,1596,1597,1599],{},"Choose ",[36,1598,1484],{}," in the Bucket tab to stop enforcing a ranking.",[11,1601,1602,1603,1605,1606,559],{},"If the ranking you clear was the enforced one, the Bucket tab returns to ",[36,1604,1484],{}," by itself. With a completed session, the Bucket tab allows only ",[36,1607,1484],{},[15,1609,1611],{"id":1610},"when-the-rankings-are-deleted","When the rankings are deleted",[11,1613,1614,1615,559],{},"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 ",[36,1616,1484],{},[11,1618,1619],{},"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,1621,1623],{"id":1622},"completed-sessions-lock-the-bucket-table","Completed sessions lock the bucket table",[11,1625,1626],{},"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,1628,1629,1630,1632,1633,1635],{},"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 ",[36,1631,146],{},", and the ranking dropdown allows only ",[36,1634,1484],{},". Cancel or accept the completed sessions to unlock the table.",{"title":66,"searchDepth":67,"depth":67,"links":1637},[1638,1639,1640,1641,1642,1643,1644,1645,1646],{"id":1372,"depth":67,"text":1373},{"id":1397,"depth":67,"text":1398},{"id":1446,"depth":67,"text":1447},{"id":1475,"depth":67,"text":1476},{"id":1530,"depth":67,"text":1531},{"id":1553,"depth":67,"text":1554},{"id":1576,"depth":67,"text":1577},{"id":1610,"depth":67,"text":1611},{"id":1622,"depth":67,"text":1623},"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",[1652,1653,1654],"affinity ranking","dot voting","backlog refinement",{},12,"\u002Ftutorials\u002Faffinity-and-dot-ranking",{"title":1348,"description":1648},{"loc":1657,"lastmod":1647},"affinity-and-dot-ranking","tutorials\u002Fen\u002Faffinity-and-dot-ranking","tutorial\u002Faffinity-and-dot-ranking","rcWzwNos5qn1ewoWDRh93HZS_38wLdC3_wwXb-YKeio",{"id":1665,"title":1666,"body":1667,"dateModified":292,"datePublished":292,"description":1898,"extension":74,"heading":1899,"image":1900,"imageAlt":1899,"keywords":1901,"locale":81,"meta":1905,"navigation":83,"order":1906,"path":1907,"section":86,"seo":1908,"sitemap":1909,"slug":1910,"stem":1911,"translationKey":1912,"__hash__":1913},"tutorials\u002Ftutorials\u002Fen\u002Funderstanding-charts.md","Understanding the charts | Tutorials | Scrumpy Planning Poker",{"type":8,"value":1668,"toc":1891},[1669,1672,1676,1695,1700,1710,1732,1737,1740,1745,1748,1751,1754,1763,1768,1771,1774,1777,1785,1790,1793,1796,1800,1815,1819,1822,1825,1844,1847,1851,1863,1868,1871,1874,1888],[11,1670,1671],{},"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,1673,1675],{"id":1674},"the-result-chart","The result chart",[11,1677,1678,1679,1681,1682,1684,1685,731,1688,744,1691,1694],{},"Open a completed session and select ",[36,1680,1466],{},". While open voting is running, ",[36,1683,1466],{}," updates as votes arrive. The chart counts how many participants voted each value. With the three votes ",[36,1686,1687],{},"2 sp",[36,1689,1690],{},"5 sp",[36,1692,1693],{},"8 sp",", it shows three equal parts or bars.",[23,1696],{"alt":1697,"caption":1698,"stem":1699},"A pie chart with one vote each for 2, 5, and 8 story points","Pie result chart","tutorial-chart-pie",[11,1701,1702,1703,731,1705,744,1707,1709],{},"The pie legend sits below the chart and lists ",[36,1704,1687],{},[36,1706,1690],{},[36,1708,1693],{},", 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,1711,1712,1713,1716,1717,1720,1721,731,1724,1727,1728,1731],{},"Your chart type is personal and does not change anyone else's view. Open your Jira avatar menu, choose ",[36,1714,1715],{},"Scrumpy Poker",", find ",[36,1718,1719],{},"Chart type",", and select ",[36,1722,1723],{},"Pie",[36,1725,1726],{},"Vertical bar",", or ",[36,1729,1730],{},"Horizontal bar",". The choice follows you across spaces and applies to every result you open.",[23,1733],{"alt":1734,"caption":1735,"stem":1736},"A vertical bar chart with one vote each for 2, 5, and 8 story points","Vertical bar result chart","tutorial-chart-vertical-bar",[11,1738,1739],{},"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.",[23,1741],{"alt":1742,"caption":1743,"stem":1744},"A horizontal bar chart with one vote each for 2, 5, and 8 story points","Horizontal bar result chart","tutorial-chart-horizontal-bar",[11,1746,1747],{},"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,1749,1750],{},"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,1752,266],{"id":1753},"quadrant",[11,1755,1756,1757,1759,1760,1762],{},"A perspective with two parameters shows a ",[36,1758,266],{}," tab after ",[36,1761,1466],{}," once the session completes. Each axis is one parameter, drawn with its real values, including negative ones.",[23,1764],{"alt":1765,"caption":1766,"stem":1767},"A quadrant chart with three voters and the averaged position","Quadrant chart","tutorial-chart-quadrant",[11,1769,1770],{},"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,1772,1773],{},"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,1775,368],{"id":1776},"radar",[11,1778,1779,1780,1759,1782,1784],{},"A perspective with three or more parameters shows a ",[36,1781,368],{},[36,1783,1466],{}," once the session completes. Each ray is one parameter, scaled from its minimum at the centre to its maximum on the outer ring.",[23,1786],{"alt":1787,"caption":1788,"stem":1789},"A radar chart with three voters and the averaged polygon","Radar chart","tutorial-chart-radar",[11,1791,1792],{},"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,1794,1795],{},"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,1797,1799],{"id":1798},"heat-map","Heat map",[11,1801,1802,1803,1805,1806,1808,1809,1811,1812,1814],{},"Open a planning session, switch the edit mode to ",[36,1804,1256],{},", select a card perspective such as ",[36,1807,1074],{},", open the ",[36,1810,1284],{}," tab, and select ",[36,1813,1466],{},". The heat map compares every listed work item in one picture.",[23,1816],{"alt":1817,"caption":1799,"stem":1818},"A heat map with three voters across ten work items","tutorial-chart-heatmap",[11,1820,1821],{},"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,1823,1824],{},"The heat map has no legend. The card labels and the numbers in the cells are the key:",[641,1826,1827,1834,1841],{},[644,1828,1829,1830,1833],{},"A dark cell with ",[36,1831,1832],{},"3"," means all three voters agree.",[644,1835,1836,1837,1840],{},"Three separate ",[36,1838,1839],{},"1"," cells in a row mean the team split three ways.",[644,1842,1843],{},"A grey row means the work item has no votes yet.",[11,1845,1846],{},"Use it to spot the work items that need another round of discussion and the ones that are already settled.",[15,1848,1850],{"id":1849},"scatter","Scatter",[11,1852,1853,1854,1856,1857,1859,1860,1862],{},"Open the same ",[36,1855,1284],{}," tab for a free-scale perspective such as ",[36,1858,917],{}," and select ",[36,1861,1466],{},". The scatter chart compares the story points voted for every listed work item.",[23,1864],{"alt":1865,"caption":1866,"stem":1867},"A scatter chart with three voters across ten work items","Scatter chart","tutorial-chart-scatter",[11,1869,1870],{},"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,1872,1873],{},"The scatter chart has no legend. Read each row from left to right:",[641,1875,1876,1879,1882,1885],{},[644,1877,1878],{},"Dots close together mean the team agrees on that work item.",[644,1880,1881],{},"Dots spread far apart mean the estimates differ, and the work item needs discussion.",[644,1883,1884],{},"The dashed cross is the average that becomes the estimate.",[644,1886,1887],{},"A dot far from the cross is an outlier worth talking about.",[11,1889,1890],{},"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":66,"searchDepth":67,"depth":67,"links":1892},[1893,1894,1895,1896,1897],{"id":1674,"depth":67,"text":1675},{"id":1753,"depth":67,"text":266},{"id":1776,"depth":67,"text":368},{"id":1798,"depth":67,"text":1799},{"id":1849,"depth":67,"text":1850},"Read the estimation charts: pie, bar, radar, scatter, quadrant and heatmap views of a vote.","Understanding the charts","\u002Fog\u002Ftutorial-understanding-charts.jpg",[1902,1903,1904,1229],"estimation charts","heatmap","scatter plot",{},13,"\u002Ftutorials\u002Funderstanding-charts",{"title":1666,"description":1898},{"loc":1907,"lastmod":292},"understanding-charts","tutorials\u002Fen\u002Funderstanding-charts","tutorial\u002Funderstanding-charts","5yoIYYZbaXtR0HixB8a1KIP-qKjmY_9_kuDp-7ZXYUg",{"id":1915,"title":1916,"body":1917,"dateModified":2059,"datePublished":2059,"description":2060,"extension":74,"heading":1931,"image":2061,"imageAlt":1931,"keywords":2062,"locale":81,"meta":2066,"navigation":83,"order":2067,"path":2068,"section":86,"seo":2069,"sitemap":2070,"slug":2071,"stem":2072,"translationKey":2073,"__hash__":2074},"tutorials\u002Ftutorials\u002Fen\u002Fcapacity-planning.md","Capacity planning | Tutorials | Scrumpy Planning Poker",{"type":8,"value":1918,"toc":2049},[1919,1922,1926,1941,1945,1948,1952,1960,1965,1969,1972,1977,1981,1994,1998,2001,2004,2009,2013,2019,2023,2027,2033,2037,2044],[11,1920,1921],{},"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,1923,1925],{"id":1924},"start-with-the-sprints-you-finished","Start with the sprints you finished",[11,1927,1928,1929,1932,1933,1936,1937,1940],{},"Open the space page and choose the ",[36,1930,1931],{},"Capacity planning"," tab. Select your planning session, then select ",[36,1934,1935],{},"Plan sprint",". In the ",[36,1938,1939],{},"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.",[23,1942],{"alt":1943,"caption":1939,"stem":1944},"The Plan sprint dialog with three past sprints selected","tutorial-capacity-plan-sprint-past",[11,1946,1947],{},"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,1949,1951],{"id":1950},"add-the-active-and-future-sprints-you-want-to-plan","Add the active and future sprints you want to plan",[11,1953,1401,1954,1957,1958,559],{},[36,1955,1956],{},"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 ",[36,1959,1049],{},[23,1961],{"alt":1962,"caption":1963,"stem":1964},"The Sprints tab of the Plan sprint dialog with an active sprint selected","Active and future sprints","tutorial-capacity-plan-sprint-future",[15,1966,1968],{"id":1967},"the-board-selector-decides-which-sprints-you-can-plan","The board selector decides which sprints you can plan",[11,1970,1971],{},"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.",[23,1973],{"alt":1974,"caption":1975,"stem":1976},"The board selector at the top left of the capacity planning page","Board selector","tutorial-capacity-board-selector",[15,1978,1980],{"id":1979},"add-and-remove-work-items","Add and remove work items",[11,1982,1983,1984,1986,1987,1990,1991,559],{},"With a sprint selected in the table, use ",[36,1985,1045],{}," 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 ",[36,1988,1989],{},"Remove",". Removing an item changes the plan, not Jira, until you select ",[36,1992,1993],{},"Apply",[15,1995,1997],{"id":1996},"read-the-capacity-timeline","Read the capacity timeline",[11,1999,2000],{},"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,2002,2003],{},"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.",[23,2005],{"alt":2006,"caption":2007,"stem":2008},"The capacity table with seven work items and the timeline turning red above capacity","Capacity timeline","tutorial-capacity-timeline",[15,2010,2012],{"id":2011},"set-up-the-team","Set up the team",[11,2014,1401,2015,2018],{},[36,2016,2017],{},"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.",[23,2020],{"alt":2021,"caption":2017,"stem":2022},"The Team capacity table with three team members and their hours","tutorial-capacity-team",[15,2024,2026],{"id":2025},"agree-on-the-sprint-goal","Agree on the sprint goal",[11,2028,1401,2029,2032],{},[36,2030,2031],{},"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,2034,2036],{"id":2035},"vote-on-a-work-item-and-chat","Vote on a work item and chat",[11,2038,2039,2040,2043],{},"Select a work item in the table, then open a perspective tab to vote with the same cards you use in Refinement\u002Fgrooming. A ",[36,2041,2042],{},"Chat"," tab appears for the selected work item, so the team can discuss that item without leaving the capacity plan.",[23,2045],{"alt":2046,"caption":2047,"stem":2048},"The perspective voting panel and the Chat tab for a planned work item","Vote and chat","tutorial-capacity-voting-chat",{"title":66,"searchDepth":67,"depth":67,"links":2050},[2051,2052,2053,2054,2055,2056,2057,2058],{"id":1924,"depth":67,"text":1925},{"id":1950,"depth":67,"text":1951},{"id":1967,"depth":67,"text":1968},{"id":1979,"depth":67,"text":1980},{"id":1996,"depth":67,"text":1997},{"id":2011,"depth":67,"text":2012},{"id":2025,"depth":67,"text":2026},{"id":2035,"depth":67,"text":2036},"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",[2063,2064,2065],"capacity planning","sprint capacity","velocity",{},14,"\u002Ftutorials\u002Fcapacity-planning",{"title":1916,"description":2060},{"loc":2068,"lastmod":2059},"capacity-planning","tutorials\u002Fen\u002Fcapacity-planning","tutorial\u002Fcapacity-planning","dXqFjEQiGF7gHvaxbkFg7mAJK_PdEsz8aLt9oMCwdxI",{"id":2076,"title":2077,"body":2078,"dateModified":2059,"datePublished":2059,"description":2151,"extension":74,"heading":2152,"image":2153,"imageAlt":2152,"keywords":2154,"locale":81,"meta":2158,"navigation":83,"order":2159,"path":2160,"section":86,"seo":2161,"sitemap":2162,"slug":2163,"stem":2164,"translationKey":2165,"__hash__":2166},"tutorials\u002Ftutorials\u002Fen\u002Farchiving.md","Archiving your plans | Tutorials | Scrumpy Planning Poker",{"type":8,"value":2079,"toc":2146},[2080,2083,2087,2102,2107,2110,2114,2124,2129,2132,2136],[11,2081,2082],{},"Archiving keeps a permanent record of a planning session or a capacity plan in Confluence. The team can look back later and see what was estimated, what was planned, and why. A space administrator chooses the Confluence space in space settings before anyone can archive.",[15,2084,2086],{"id":2085},"archive-a-refinement-session","Archive a refinement session",[11,2088,1401,2089,2091,2092,2095,2096,2098,2099,2101],{},[36,2090,1023],{}," tab, select the planning session, and select ",[36,2093,2094],{},"Archive"," next to ",[36,2097,1314],{},". The dialog shows the planning window and a preview of the work items with accepted estimates that will be written. Select ",[36,2100,2094],{}," to create the page.",[23,2103],{"alt":2104,"caption":2105,"stem":2106},"The Refinement\u002Fgrooming archive dialog with the preview of accepted estimates","Refinement archive preview","tutorial-archive-planning",[11,2108,2109],{},"The generated page keeps the planning title, description, start and end time, the participants, and every accepted estimate with its perspective, votes, participants, and moderator.",[15,2111,2113],{"id":2112},"archive-a-capacity-plan","Archive a capacity plan",[11,2115,1401,2116,2118,2119,2121,2122,2101],{},[36,2117,1931],{}," tab, select an active or future sprint in the combined table, and select ",[36,2120,2094],{}," in the toolbar. The dialog previews the sprint and its dates, the sprint goal and its votes, the capacity decision, and the velocity summary. The team and work item tables are written to the page as well. Select ",[36,2123,2094],{},[23,2125],{"alt":2126,"caption":2127,"stem":2128},"The Capacity planning archive dialog with the sprint summary and velocity","Capacity archive preview","tutorial-archive-capacity",[11,2130,2131],{},"The generated page keeps the planning window, the sprint and goal, the goal votes, the velocity and target capacity, the team with hours and utilization, and the planned work items in order.",[15,2133,2135],{"id":2134},"find-the-pages-later","Find the pages later",[11,2137,2138,2139,2141,2142,2145],{},"Planning session archives sit under the ",[36,2140,881],{}," parent page. Capacity archives sit under the ",[36,2143,2144],{},"Plannings"," parent page, in a child page named after the space and \"Capacity planning\". Archiving the same sprint again updates its page instead of creating a duplicate.",{"title":66,"searchDepth":67,"depth":67,"links":2147},[2148,2149,2150],{"id":2085,"depth":67,"text":2086},{"id":2112,"depth":67,"text":2113},{"id":2134,"depth":67,"text":2135},"Archive planning sessions, capacity plans, stand-ups and retrospectives to Confluence, with a clear page hierarchy.","Archiving your plans","\u002Fog\u002Ftutorial-archiving.jpg",[2155,2156,2157],"confluence archive","planning archive","retrospective archive",{},15,"\u002Ftutorials\u002Farchiving",{"title":2077,"description":2151},{"loc":2160,"lastmod":2059},"archiving","tutorials\u002Fen\u002Farchiving","tutorial\u002Farchiving","LUADFXzNR2iP2wk39AwMP3Kv49FDRx0r3OwXBe_zD0Y",{"id":2168,"title":2169,"body":2170,"dateModified":1115,"datePublished":2464,"description":2465,"extension":74,"heading":2466,"image":2467,"imageAlt":2466,"keywords":2468,"locale":81,"meta":2472,"navigation":83,"order":2473,"path":2474,"section":86,"seo":2475,"sitemap":2476,"slug":2477,"stem":2478,"translationKey":2479,"__hash__":2480},"tutorials\u002Ftutorials\u002Fen\u002Fleading-a-standup.md","Leading a standup | Tutorials | Scrumpy Planning Poker",{"type":8,"value":2171,"toc":2454},[2172,2178,2182,2200,2205,2208,2212,2215,2218,2224,2229,2233,2238,2242,2267,2274,2278,2284,2287,2292,2317,2322,2326,2337,2345,2350,2394,2398,2404,2417,2433,2438,2442],[11,2173,2174,2175,2177],{},"A standup is the easiest meeting to run in Scrumpy. Open the tab, pick the running sprint, and talk through the cards in the order the team sees them. Everything you change stays in the standup until you press ",[36,2176,1993],{},", so you can rearrange the board while you talk without touching Jira.",[15,2179,2181],{"id":2180},"pick-the-planning-session-board-and-sprint","Pick the planning session, board, and sprint",[11,2183,1401,2184,2187,2188,2191,2192,2195,2196,2199],{},[36,2185,2186],{},"Standup"," tab and pick a planning session from the tabs above the board. Pick the ",[36,2189,2190],{},"board"," first, then the ",[36,2193,2194],{},"sprint",". The sprint list only shows the sprints that are running right now, so the standup opens on the work the team is doing today. The sprint name and goal sit above the columns, and the link icon opens the sprint in Jira. When the space has no board, pick a saved ",[36,2197,2198],{},"filter"," instead, and the standup shows the work items that filter returns, with one column per status.",[23,2201],{"alt":2202,"caption":2203,"stem":2204},"The board and sprint selectors above the standup","Choose the board and the running sprint","tutorial-standup-sprint",[11,2206,2207],{},"Only a moderator changes the shared board. A voter or guest who picks another sprint does so only for their own browser tab.",[15,2209,2211],{"id":2210},"read-the-board","Read the board",[11,2213,2214],{},"Every column of the board is a lane, in the board's own order. The cards follow the shared standup order, which starts as the order of the sprint in Jira. Each card shows the assignee, the priority, the key as a link, the estimate, and one or two lines of the summary. A card with an estimate shows it as a badge, so the team can see the size without opening Jira. A work item the team has passed shows a small green check right of its key.",[11,2216,2217],{},"In this example the To Do column holds the most work, one card has a red flag, and two cards were already moved while the team talked. The two moved cards carry an undo button next to their checkbox. Three cards carry the green passed check, and the two cards of the absent teammate are gray and dimmed.",[11,2219,1084,2220,2223],{},[36,2221,2222],{},"Max per column"," in the toolbar to cap how many cards a column loads and shows. Work items beyond the cap stay in Jira and are loaded when you raise the cap. A work item the standup already loaded keeps its place and staged changes while it is hidden.",[23,2225],{"alt":2226,"caption":2227,"stem":2228},"The standup board with cards in every column","The sprint as a standup board","tutorial-standup-board",[15,2230,2232],{"id":2231},"flag-a-work-item-that-needs-attention","Flag a work item that needs attention",[11,2234,2235,2236,559],{},"Select the flag at the right of a card to mark it for the team. A card that is already flagged in Jira opens with a red flag. Select it again to clear the flag. The flag shows for everyone right away, and it is written to the Jira Flagged field when you press ",[36,2237,1993],{},[15,2239,2241],{"id":2240},"move-work-items-without-leaving-the-standup","Move work items without leaving the standup",[11,2243,2244,2245,2248,2249,2252,2253,2256,2257,2259,2260,2262,2263,2266],{},"Use the ",[36,2246,2247],{},"Move to"," dropdown on a card to change its status or its place in the lane. ",[36,2250,2251],{},"By status"," offers the statuses the card can reach in Jira, and ",[36,2254,2255],{},"By rank"," moves the card one place up or down. Select several cards with their checkboxes to move them together. A card with a staged status move keeps ",[36,2258,2251],{}," disabled until you undo or apply that move, while ",[36,2261,2255],{}," stays available. The statuses are read when you open the menu, so the first open can take a moment and shows ",[36,2264,2265],{},"Loading statuses"," until they arrive.",[11,2268,2269,2270,2273],{},"The change is shared with the team immediately, but it is not written to Jira yet. The moved card shows an undo button next to its checkbox. Select it to remove that staged change right away, without a confirmation and without changing Jira. ",[36,2271,2272],{},"Discard changes"," is the button that asks you to confirm before it clears everything.",[15,2275,2277],{"id":2276},"follow-the-same-standup-in-the-status-table","Follow the same standup in the Status table",[11,2279,263,2280,2283],{},[36,2281,2282],{},"Status"," tab at the left of the side panel shows the same standup in a second view. It is not another list: every work item of the sprint is there, in the same columns and the same order, with the same flags and the same staged moves. Move a work item in the table and its card moves on the board at the same time.",[11,2285,2286],{},"Each board column is a wide row with its name in the middle, and the work items of that column sit under it. A row shows the work type, the priority, the flag, the key, the green passed check, the undo button, and the estimate, so the whole sprint fits in a short list. That makes the table quick to scan, and sometimes it is simply easier to walk through the work items here than on the board.",[23,2288],{"alt":2289,"caption":2290,"stem":2291},"The Status table with the same work items and staged moves as the board","The same standup as a compact table","tutorial-standup-order",[641,2293,2294,2301,2304,2307,2314],{},[644,2295,2296,2297,2300],{},"Select the round button at the left of a row to make that work item the one under discussion, exactly like clicking its card. Everyone else sees a yellow ",[36,2298,2299],{},"M"," on that row.",[644,2302,2303],{},"Drag a row to change its place in its column, or drop it under another column to move it there when the workflow allows it.",[644,2305,2306],{},"Select the flag to stage a flag, and the undo button to remove a staged change. These are the same buttons and the same staged moves as on the board.",[644,2308,2309,2310,2313],{},"A green check in the narrow column after the key means the team has passed that work item: the moderator forwarded its countdown, or moved the selection on after the countdown ran out. The same check appears next to the key on the card and in the ",[36,2311,2312],{},"Assignee"," table.",[644,2315,2316],{},"A moderator can move and flag every work item, a voter only the work items assigned to them, and a guest reads the table.",[11,2318,2319,2321],{},[36,2320,1993],{}," writes the new order and the staged moves to Jira from here too.",[15,2323,2325],{"id":2324},"see-who-is-in-the-room","See who is in the room",[11,2327,263,2328,2330,2331,2333,2334,2336],{},[36,2329,2312],{}," tab follows ",[36,2332,2282],{}," at the left of the side panel. It groups the same work items by the person doing them, so the standup can walk through the team person by person instead of column by column. ",[36,2335,1288],{}," sits last and holds the work items that have no assignee.",[11,2338,2339,2340,2342,2343,2313],{},"Every assignee is a wide row with the person's name in the middle, and that person's work items sit under it, in the same board order. A row shows the same facts as the ",[36,2341,2282],{}," table: the work type, the priority, the flag, the key, the green passed check, the undo button, and the estimate. The check and the undo button are the same ones you see on the board and in the ",[36,2344,2282],{},[23,2346],{"alt":2347,"caption":2348,"stem":2349},"The Assignee table with the team grouped by person, one absent assignee, and the same passed checks","The same standup grouped by person","tutorial-standup-assignee",[641,2351,2352,2360,2369,2372,2377,2383,2389],{},[644,2353,2354,2355,2357,2358,559],{},"Drag a work item into another person's row to give it to them. The board avatar, the card color, and the ",[36,2356,2282],{}," row show the new person right away, but Jira changes only when you press ",[36,2359,1993],{},[644,2361,263,2362,2364,2365,2368],{},[36,2363,2222],{}," cap also applies here, so the table lists only the work items the board shows. A person whose work items all sit beyond the cap is not listed, in the table or in the ",[36,2366,2367],{},"Participants"," picker, until you raise the cap.",[644,2370,2371],{},"A moderator can give any work item to another person. A voter can give only their own work items. Guests read the table.",[644,2373,263,2374,2376],{},[36,2375,2367],{}," picker below the table lists everyone whose checkbox is checked. A moderator clears the checkbox at the left of an assignee row to remove that person from the picker and mark them absent. The row stays, with the checkbox unchecked and disabled, because the work items still belong to that person. Add the person back in the picker to check it again. Clearing a person who has no work items removes their row. The choice is shared with the team right away.",[644,2378,2379,2380,2382],{},"When a person is absent, their work items cannot be selected, from this table, from the ",[36,2381,2282],{}," table, or by clicking the card. Their cards use a gray border with dimmed text and avatar, so the team can tell them apart, and they lose the countdown pause, resume, and forward buttons.",[644,2384,2385,2386,2388],{},"With the ",[36,2387,2312],{}," tab open, the countdown forward button walks this table and skips every absent person, so the standup continues with the next teammate.",[644,2390,2391,2393],{},[36,2392,1288],{}," is always present and has no checkbox.",[15,2395,2397],{"id":2396},"apply-the-changes-to-jira","Apply the changes to Jira",[11,2399,2400,2401,2403],{},"This is the step that makes the changes real. Press ",[36,2402,1993],{}," in the action bar under the board. Scrumpy writes the new status of every moved work item, the new order of the sprint, the staged flags, and the new assignees to Jira, in one go.",[11,2405,2406,2407,2409,2410,2412,2413,2416],{},"A moderator can also archive the standup with ",[36,2408,2094],{},", which sits before ",[36,2411,1993],{}," and appears when a Confluence space is configured for archives. The dialog lists the planning window, the sprint, board, or filter, every assignee with presence and presentation time, and every work item with its status, presentation time, and changes. A staged change is marked ",[36,2414,2415],{},"Pending",". Archiving never changes Jira or the staged changes.",[11,2418,2419,2420,2422,2423,2425,2426,2428,2429,2432],{},"Without ",[36,2421,1993],{},", nothing is saved to Jira. Closing the tab or picking another sprint leaves Jira exactly as it was. If you change your mind, press ",[36,2424,2272],{}," and confirm the dialog instead. Discard removes every staged change and clears every passed check, and it does not touch Jira. ",[36,2427,1993],{}," clears the passed checks too, because the walkthrough is over. ",[36,2430,2431],{},"Reload sprints and work items"," reads the sprint from Jira again.",[23,2434],{"alt":2435,"caption":2436,"stem":2437},"The action bar with the pending changes and the Apply button","Apply writes the standup to Jira","tutorial-standup-apply",[15,2439,2441],{"id":2440},"keep-everyone-in-step","Keep everyone in step",[11,2443,2444,2445,2447,2448,2450,2451,2453],{},"The moderator clicks the card the team is talking about, and everyone locked to the moderator follows the same card. The countdown at the right of the action bar follows that card, so each work item gets the same amount of time. When the ",[36,2446,2312],{}," tab is open, the forward button moves through the people in that table and skips every absent teammate; on any other tab it follows the board. Select ",[36,2449,1314],{}," after ",[36,2452,1993],{}," when the session is done, and the planning session and its standup are removed.",{"title":66,"searchDepth":67,"depth":67,"links":2455},[2456,2457,2458,2459,2460,2461,2462,2463],{"id":2180,"depth":67,"text":2181},{"id":2210,"depth":67,"text":2211},{"id":2231,"depth":67,"text":2232},{"id":2240,"depth":67,"text":2241},{"id":2276,"depth":67,"text":2277},{"id":2324,"depth":67,"text":2325},{"id":2396,"depth":67,"text":2397},{"id":2440,"depth":67,"text":2441},"2026-11-15","Lead a standup in Scrumpy: pick the sprint, follow the speaking order, flag blockers and apply status moves.","Leading a standup","\u002Fog\u002Ftutorial-leading-a-standup.jpg",[2469,2470,2471],"daily standup","standup board","jira standup",{},16,"\u002Ftutorials\u002Fleading-a-standup",{"title":2169,"description":2465},{"loc":2474,"lastmod":1115},"leading-a-standup","tutorials\u002Fen\u002Fleading-a-standup","tutorial\u002Fleading-a-standup","G3s5x-Jy40FmGpEPfhchMsjxbL93ImE5ucBaVVLHWXo",{"id":2482,"title":2483,"body":2484,"dateModified":1115,"datePublished":2464,"description":2714,"extension":74,"heading":2715,"image":2716,"imageAlt":2715,"keywords":2717,"locale":81,"meta":2721,"navigation":83,"order":2722,"path":2723,"section":86,"seo":2724,"sitemap":2725,"slug":2726,"stem":2727,"translationKey":2728,"__hash__":2729},"tutorials\u002Ftutorials\u002Fen\u002Frunning-a-retrospective.md","Running a retrospective | Tutorials | Scrumpy Planning Poker",{"type":8,"value":2485,"toc":2705},[2486,2489,2491,2510,2513,2517,2520,2527,2532,2536,2545,2552,2555,2559,2572,2577,2591,2595,2602,2607,2621,2625,2637,2659,2670,2675,2679,2693,2696],[11,2487,2488],{},"A retrospective takes minutes to set up and keeps the whole team on the same page at the end of a sprint. Add notes to three columns, like the ones you agree with, group the related ones, and turn the best of them into action items that become Jira work items.",[15,2490,2181],{"id":2180},[11,2492,1401,2493,2496,2497,2499,2500,2502,2503,2506,2507,559],{},[36,2494,2495],{},"Retrospective"," tab and pick a planning session from the tabs above the retrospective board. Pick the ",[36,2498,2190],{},", then the ",[36,2501,2194],{}," that just ended. The last six started sprints are listed, so the sprint you want is normally the first one. When the board has no started sprint, the sprint selector is hidden and the retrospective works for the board. When the space has no board, the retrospective works for the planning session. The ",[36,2504,2505],{},"type"," dropdown on the right changes the three column names, for example ",[36,2508,2509],{},"Start \u002F Stop \u002F Continue",[11,2511,2512],{},"Guests can read the retrospective. Moderators and voters can add notes and like them.",[15,2514,2516],{"id":2515},"add-a-note-to-each-column","Add a note to each column",[11,2518,2519],{},"Under each column name, select the add button with the plus icon. An empty note appears and its editor is ready, so you type straight away. Your notes sit on the right of the column and the notes from other participants sit on the left.",[11,2521,2522,2523,2526],{},"During the ",[36,2524,2525],{},"Feedback"," stage the notes from other people stay face down, so nobody is influenced by what the others wrote. Your own notes stay visible to you.",[23,2528],{"alt":2529,"caption":2530,"stem":2531},"The retrospective board with notes in all three columns","Notes for the good, the bad, and the ugly","tutorial-retro-board",[15,2533,2535],{"id":2534},"like-and-group-the-notes","Like and group the notes",[11,2537,2538,2539,500,2542,2544],{},"Switch the ",[36,2540,2541],{},"Stage",[36,2543,138],{}," when the team has finished writing. The notes are revealed and everyone can like the ones worth acting on. The like button shows how many people agree, and in this example three voters took part, with one, two, and three likes on different cards.",[11,2546,2547,2548,2551],{},"Select several notes in the same column, then choose ",[36,2549,2550],{},"Group notes",". Related notes join one card, and the group keeps one like count for all of them. Grouping is available from the Vote stage on and is disabled during Feedback. In the middle column three notes are grouped into one card, so the discussion stays together.",[11,2553,2554],{},"A moderator can also highlight notes without grouping them. A highlighted note is filled with the light accent colour, and everyone sees the same fill. Here two notes are highlighted for the discussion.",[15,2556,2558],{"id":2557},"follow-the-same-notes-in-the-status-table","Follow the same notes in the Status table",[11,2560,263,2561,2563,2564,119,2566,2568,2569,2571],{},[36,2562,2282],{}," tab at the left of the side panel shows the same retrospective as a compact table. The ",[36,2565,2282],{},[36,2567,2312],{}," tabs appear from the ",[36,2570,138],{}," stage on. The three columns are wide bucket rows, and the notes of each column sit under their column in board order. A row shows the selection checkbox, the author, and the first line of the note, shortened with an ellipsis. A group is one row, with the first line of each note stacked and separated by a dashed line.",[23,2573],{"alt":2574,"caption":2575,"stem":2576},"The Status table with the same notes and group as the board","The same retrospective grouped by column","tutorial-retro-status",[641,2578,2579,2582,2585,2588],{},[644,2580,2581],{},"Drag a row into another column to move the note there. Dragging inside its own column changes only its order. Grouped notes travel together as one row.",[644,2583,2584],{},"A moderator can move any row, a voter only their own notes, and a guest reads the table. A row the viewer may not move returns to its place.",[644,2586,2587],{},"A column holds at most 200 notes, so a drop into a full column is refused and the row returns.",[644,2589,2590],{},"The checkbox is the same selection as on the board. Ticking a row ticks its note on the board, and ticking a note on the board ticks its row. A group row ticks every note in the group. Select notes here to group them or to create action items from them.",[15,2592,2594],{"id":2593},"walk-the-notes-person-by-person-in-the-assignee-table","Walk the notes person by person in the Assignee table",[11,2596,263,2597,2330,2599,2601],{},[36,2598,2312],{},[36,2600,2282],{},". It groups the same notes by the person who wrote them, in the order the authors first appear on the board. A group sits under the author of its first note. Each person is a wide bucket row, and their notes sit under it with the same columns as the Status table.",[23,2603],{"alt":2604,"caption":2605,"stem":2606},"The Assignee table with the notes grouped by author","The same retrospective grouped by author","tutorial-retro-assignee",[641,2608,2609,2612,2615,2618],{},[644,2610,2611],{},"Drag a note into another person's bucket to make that person its author. The note header on the board changes right away. A group moves together, so every note in the group takes the new author.",[644,2613,2614],{},"A moderator can reassign any note. A voter can reassign only their own notes. A guest reads the table.",[644,2616,2617],{},"You can drop a note only under a person who already has a note in the retrospective, because only they have a bucket.",[644,2619,2620],{},"The checkboxes and the shared selection work the same as in the Status table, so you can select notes here too.",[15,2622,2624],{"id":2623},"turn-notes-into-action-items","Turn notes into action items",[11,2626,2538,2627,500,2629,2632,2633,2636],{},[36,2628,2541],{},[36,2630,2631],{},"Actions",". Select a note or a group, then choose ",[36,2634,2635],{},"Create action items",". Each selected note or group becomes one row in the action items table, with the note text as the summary and the authors and likes beside it. Drag a row to change its place in the table. Everyone sees the new order, and the archive keeps it.",[11,2638,2639,2640,2643,2644,2646,2647,2649,2650,2652,2653,2656,2657,559],{},"For each row, pick the Jira ",[36,2641,2642],{},"work type"," in the Type column. Then press ",[36,2645,1993],{},". Scrumpy creates a Jira work item for every action item with a work type and links it in the Work item column. Action items set to ",[36,2648,519],{}," are skipped, and a second ",[36,2651,1993],{}," without an edit stays disabled. Once a Jira work item is created from an action item, its estimate appears in the ",[36,2654,2655],{},"Estimate"," column and you can estimate it in the voting tabs next to ",[36,2658,2042],{},[11,2660,2661,2663,2664,2666,2667,2669],{},[36,2662,2272],{}," sits before ",[36,2665,1993],{}," and appears to a moderator. It asks for confirmation and removes every note, action item, and the timer of the retrospective on screen. It is disabled when the retrospective has nothing to discard. The ",[36,2668,2042],{}," tab in the side panel holds the full planning session conversation, including messages from the work items your action items link to.",[23,2671],{"alt":2672,"caption":2673,"stem":2674},"The action items with a linked Jira work item","Action items become Jira work items","tutorial-retro-action-items",[15,2676,2678],{"id":2677},"guide-the-session-with-stages-and-the-timer","Guide the session with stages and the timer",[11,2680,263,2681,2683,2684,2686,2687,2689,2690,2692],{},[36,2682,2541],{}," dropdown sits in the action bar with the countdown. ",[36,2685,2525],{}," is for writing, ",[36,2688,138],{}," for choosing, and ",[36,2691,2631],{}," for turning notes into work. A line below the notes explains what the current stage is for, and everyone sees it. Only a moderator changes the stage.",[11,2694,2695],{},"A timer keeps each stage inside its timebox. The first note you add in Feedback starts the countdown, and while a countdown runs the stage is locked. When the countdown ends, or when a moderator presses the fast-forward button, the stage ends early and everyone moves to the next one. In the Actions stage the timer controls are disabled.",[11,2697,2698,2699,2701,2702,2704],{},"When the team is done, ",[36,2700,2094],{}," saves the retrospective to Confluence. It is available in the Actions stage only. ",[36,2703,1314],{}," closes the planning session and removes its notes, action items, standup, and chat.",{"title":66,"searchDepth":67,"depth":67,"links":2706},[2707,2708,2709,2710,2711,2712,2713],{"id":2180,"depth":67,"text":2181},{"id":2515,"depth":67,"text":2516},{"id":2534,"depth":67,"text":2535},{"id":2557,"depth":67,"text":2558},{"id":2593,"depth":67,"text":2594},{"id":2623,"depth":67,"text":2624},{"id":2677,"depth":67,"text":2678},"Run a retrospective in Jira: add notes, group them, vote, create action items and archive the result.","Running a retrospective","\u002Fog\u002Ftutorial-running-a-retrospective.jpg",[2718,2719,2720],"sprint retrospective","retrospective board","action items",{},17,"\u002Ftutorials\u002Frunning-a-retrospective",{"title":2483,"description":2714},{"loc":2723,"lastmod":1115},"running-a-retrospective","tutorials\u002Fen\u002Frunning-a-retrospective","tutorial\u002Frunning-a-retrospective","ZthKA7-wmBPaegvb5BtG0p9GVOyzegAsoIIstoRSIfU",1795345588861]