[{"data":1,"prerenderedAt":1494},["ShallowReactive",2],{"tutorial-en-capacity-planning":3},{"doc":4,"prev":180,"next":443,"related":538},{"id":5,"title":6,"body":7,"dateModified":160,"datePublished":160,"description":161,"extension":162,"heading":25,"image":163,"imageAlt":25,"keywords":164,"locale":168,"meta":169,"navigation":170,"order":171,"path":172,"section":173,"seo":174,"sitemap":175,"slug":176,"stem":177,"translationKey":178,"__hash__":179},"tutorials\u002Ftutorials\u002Fen\u002Fcapacity-planning.md","Capacity planning | Tutorials | Scrumpy Planning Poker",{"type":8,"value":9,"toc":148},"minimark",[10,14,19,35,40,43,47,58,63,67,70,75,79,93,97,100,103,108,112,118,122,126,132,136,143],[11,12,13],"p",{},"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,16,18],"h2",{"id":17},"start-with-the-sprints-you-finished","Start with the sprints you finished",[11,20,21,22,26,27,30,31,34],{},"Open the space page and choose the ",[23,24,25],"strong",{},"Capacity planning"," tab. Select your planning session, then select ",[23,28,29],{},"Plan sprint",". In the ",[23,32,33],{},"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.",[36,37],"docs-figure",{"alt":38,"caption":33,"stem":39},"The Plan sprint dialog with three past sprints selected","tutorial-capacity-plan-sprint-past",[11,41,42],{},"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,44,46],{"id":45},"add-the-active-and-future-sprints-you-want-to-plan","Add the active and future sprints you want to plan",[11,48,49,50,53,54,57],{},"Open the ",[23,51,52],{},"Sprints"," tab in the same dialog and tick the active or future sprints you want to include. You can plan several sprints at once, so the team can compare the next few weeks in one view. Select ",[23,55,56],{},"Add",".",[36,59],{"alt":60,"caption":61,"stem":62},"The Sprints tab of the Plan sprint dialog with an active sprint selected","Active and future sprints","tutorial-capacity-plan-sprint-future",[15,64,66],{"id":65},"the-board-selector-decides-which-sprints-you-can-plan","The board selector decides which sprints you can plan",[11,68,69],{},"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.",[36,71],{"alt":72,"caption":73,"stem":74},"The board selector at the top left of the capacity planning page","Board selector","tutorial-capacity-board-selector",[15,76,78],{"id":77},"add-and-remove-work-items","Add and remove work items",[11,80,81,82,85,86,89,90,57],{},"With a sprint selected in the table, use ",[23,83,84],{},"Add from filter"," to bring in work items from a saved Jira filter, a sprint, or a Refinement\u002Fgrooming session. Drag a work item to reorder it inside its sprint, or drag it onto another sprint row to move it. To remove items, tick them and select ",[23,87,88],{},"Remove",". Removing an item changes the plan, not Jira, until you select ",[23,91,92],{},"Apply",[15,94,96],{"id":95},"read-the-capacity-timeline","Read the capacity timeline",[11,98,99],{},"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,101,102],{},"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.",[36,104],{"alt":105,"caption":106,"stem":107},"The capacity table with seven work items and the timeline turning red above capacity","Capacity timeline","tutorial-capacity-timeline",[15,109,111],{"id":110},"set-up-the-team","Set up the team",[11,113,49,114,117],{},[23,115,116],{},"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.",[36,119],{"alt":120,"caption":116,"stem":121},"The Team capacity table with three team members and their hours","tutorial-capacity-team",[15,123,125],{"id":124},"agree-on-the-sprint-goal","Agree on the sprint goal",[11,127,49,128,131],{},[23,129,130],{},"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,133,135],{"id":134},"vote-on-a-work-item-and-chat","Vote on a work item and chat",[11,137,138,139,142],{},"Select a work item in the table, then open a perspective tab to vote with the same cards you use in Refinement\u002Fgrooming. A ",[23,140,141],{},"Chat"," tab appears for the selected work item, so the team can discuss that item without leaving the capacity plan.",[36,144],{"alt":145,"caption":146,"stem":147},"The perspective voting panel and the Chat tab for a planned work item","Vote and chat","tutorial-capacity-voting-chat",{"title":149,"searchDepth":150,"depth":150,"links":151},"",2,[152,153,154,155,156,157,158,159],{"id":17,"depth":150,"text":18},{"id":45,"depth":150,"text":46},{"id":65,"depth":150,"text":66},{"id":77,"depth":150,"text":78},{"id":95,"depth":150,"text":96},{"id":110,"depth":150,"text":111},{"id":124,"depth":150,"text":125},{"id":134,"depth":150,"text":135},"2026-11-10","Plan the next sprints from recent velocity, read the capacity timeline and apply the plan to Jira.","md","\u002Fog\u002Ftutorial-capacity-planning.jpg",[165,166,167],"capacity planning","sprint capacity","velocity","en",{},true,14,"\u002Ftutorials\u002Fcapacity-planning","tutorial",{"title":6,"description":161},{"loc":172,"lastmod":160},"capacity-planning","tutorials\u002Fen\u002Fcapacity-planning","tutorial\u002Fcapacity-planning","dXqFjEQiGF7gHvaxbkFg7mAJK_PdEsz8aLt9oMCwdxI",{"id":181,"title":182,"body":183,"dateModified":425,"datePublished":425,"description":426,"extension":162,"heading":427,"image":428,"imageAlt":427,"keywords":429,"locale":168,"meta":434,"navigation":170,"order":435,"path":436,"section":173,"seo":437,"sitemap":438,"slug":439,"stem":440,"translationKey":441,"__hash__":442},"tutorials\u002Ftutorials\u002Fen\u002Funderstanding-charts.md","Understanding the charts | Tutorials | Scrumpy Planning Poker",{"type":8,"value":184,"toc":418},[185,188,192,214,219,229,251,256,259,264,267,270,274,283,288,291,294,298,306,311,314,317,321,339,343,346,349,370,373,377,390,395,398,401,415],[11,186,187],{},"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,189,191],{"id":190},"the-result-chart","The result chart",[11,193,194,195,198,199,201,202,205,206,209,210,213],{},"Open a completed session and select ",[23,196,197],{},"Results",". While open voting is running, ",[23,200,197],{}," updates as votes arrive. The chart counts how many participants voted each value. With the three votes ",[23,203,204],{},"2 sp",", ",[23,207,208],{},"5 sp",", and ",[23,211,212],{},"8 sp",", it shows three equal parts or bars.",[36,215],{"alt":216,"caption":217,"stem":218},"A pie chart with one vote each for 2, 5, and 8 story points","Pie result chart","tutorial-chart-pie",[11,220,221,222,205,224,209,226,228],{},"The pie legend sits below the chart and lists ",[23,223,204],{},[23,225,208],{},[23,227,212],{},", 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,230,231,232,235,236,239,240,205,243,246,247,250],{},"Your chart type is personal and does not change anyone else's view. Open your Jira avatar menu, choose ",[23,233,234],{},"Scrumpy Poker",", find ",[23,237,238],{},"Chart type",", and select ",[23,241,242],{},"Pie",[23,244,245],{},"Vertical bar",", or ",[23,248,249],{},"Horizontal bar",". The choice follows you across spaces and applies to every result you open.",[36,252],{"alt":253,"caption":254,"stem":255},"A vertical bar chart with one vote each for 2, 5, and 8 story points","Vertical bar result chart","tutorial-chart-vertical-bar",[11,257,258],{},"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.",[36,260],{"alt":261,"caption":262,"stem":263},"A horizontal bar chart with one vote each for 2, 5, and 8 story points","Horizontal bar result chart","tutorial-chart-horizontal-bar",[11,265,266],{},"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,268,269],{},"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,271,273],{"id":272},"quadrant","Quadrant",[11,275,276,277,279,280,282],{},"A perspective with two parameters shows a ",[23,278,273],{}," tab after ",[23,281,197],{}," once the session completes. Each axis is one parameter, drawn with its real values, including negative ones.",[36,284],{"alt":285,"caption":286,"stem":287},"A quadrant chart with three voters and the averaged position","Quadrant chart","tutorial-chart-quadrant",[11,289,290],{},"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,292,293],{},"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,295,297],{"id":296},"radar","Radar",[11,299,300,301,279,303,305],{},"A perspective with three or more parameters shows a ",[23,302,297],{},[23,304,197],{}," once the session completes. Each ray is one parameter, scaled from its minimum at the centre to its maximum on the outer ring.",[36,307],{"alt":308,"caption":309,"stem":310},"A radar chart with three voters and the averaged polygon","Radar chart","tutorial-chart-radar",[11,312,313],{},"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,315,316],{},"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,318,320],{"id":319},"heat-map","Heat map",[11,322,323,324,327,328,331,332,335,336,338],{},"Open a planning session, switch the edit mode to ",[23,325,326],{},"Bulk voting",", select a card perspective such as ",[23,329,330],{},"Scrum",", open the ",[23,333,334],{},"Bucket"," tab, and select ",[23,337,197],{},". The heat map compares every listed work item in one picture.",[36,340],{"alt":341,"caption":320,"stem":342},"A heat map with three voters across ten work items","tutorial-chart-heatmap",[11,344,345],{},"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,347,348],{},"The heat map has no legend. The card labels and the numbers in the cells are the key:",[350,351,352,360,367],"ul",{},[353,354,355,356,359],"li",{},"A dark cell with ",[23,357,358],{},"3"," means all three voters agree.",[353,361,362,363,366],{},"Three separate ",[23,364,365],{},"1"," cells in a row mean the team split three ways.",[353,368,369],{},"A grey row means the work item has no votes yet.",[11,371,372],{},"Use it to spot the work items that need another round of discussion and the ones that are already settled.",[15,374,376],{"id":375},"scatter","Scatter",[11,378,379,380,382,383,386,387,389],{},"Open the same ",[23,381,334],{}," tab for a free-scale perspective such as ",[23,384,385],{},"Time"," and select ",[23,388,197],{},". The scatter chart compares the story points voted for every listed work item.",[36,391],{"alt":392,"caption":393,"stem":394},"A scatter chart with three voters across ten work items","Scatter chart","tutorial-chart-scatter",[11,396,397],{},"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,399,400],{},"The scatter chart has no legend. Read each row from left to right:",[350,402,403,406,409,412],{},[353,404,405],{},"Dots close together mean the team agrees on that work item.",[353,407,408],{},"Dots spread far apart mean the estimates differ, and the work item needs discussion.",[353,410,411],{},"The dashed cross is the average that becomes the estimate.",[353,413,414],{},"A dot far from the cross is an outlier worth talking about.",[11,416,417],{},"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":149,"searchDepth":150,"depth":150,"links":419},[420,421,422,423,424],{"id":190,"depth":150,"text":191},{"id":272,"depth":150,"text":273},{"id":296,"depth":150,"text":297},{"id":319,"depth":150,"text":320},{"id":375,"depth":150,"text":376},"2026-11-02","Read the estimation charts: pie, bar, radar, scatter, quadrant and heatmap views of a vote.","Understanding the charts","\u002Fog\u002Ftutorial-understanding-charts.jpg",[430,431,432,433],"estimation charts","heatmap","scatter plot","agile metrics",{},13,"\u002Ftutorials\u002Funderstanding-charts",{"title":182,"description":426},{"loc":436,"lastmod":425},"understanding-charts","tutorials\u002Fen\u002Funderstanding-charts","tutorial\u002Funderstanding-charts","5yoIYYZbaXtR0HixB8a1KIP-qKjmY_9_kuDp-7ZXYUg",{"id":444,"title":445,"body":446,"dateModified":160,"datePublished":160,"description":522,"extension":162,"heading":523,"image":524,"imageAlt":523,"keywords":525,"locale":168,"meta":529,"navigation":170,"order":530,"path":531,"section":173,"seo":532,"sitemap":533,"slug":534,"stem":535,"translationKey":536,"__hash__":537},"tutorials\u002Ftutorials\u002Fen\u002Farchiving.md","Archiving your plans | Tutorials | Scrumpy Planning Poker",{"type":8,"value":447,"toc":517},[448,451,455,472,477,480,484,494,499,502,506],[11,449,450],{},"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,452,454],{"id":453},"archive-a-refinement-session","Archive a refinement session",[11,456,49,457,460,461,464,465,468,469,471],{},[23,458,459],{},"Refinement\u002Fgrooming"," tab, select the planning session, and select ",[23,462,463],{},"Archive"," next to ",[23,466,467],{},"Complete",". The dialog shows the planning window and a preview of the work items with accepted estimates that will be written. Select ",[23,470,463],{}," to create the page.",[36,473],{"alt":474,"caption":475,"stem":476},"The Refinement\u002Fgrooming archive dialog with the preview of accepted estimates","Refinement archive preview","tutorial-archive-planning",[11,478,479],{},"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,481,483],{"id":482},"archive-a-capacity-plan","Archive a capacity plan",[11,485,49,486,488,489,491,492,471],{},[23,487,25],{}," tab, select an active or future sprint in the combined table, and select ",[23,490,463],{}," 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 ",[23,493,463],{},[36,495],{"alt":496,"caption":497,"stem":498},"The Capacity planning archive dialog with the sprint summary and velocity","Capacity archive preview","tutorial-archive-capacity",[11,500,501],{},"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,503,505],{"id":504},"find-the-pages-later","Find the pages later",[11,507,508,509,512,513,516],{},"Planning session archives sit under the ",[23,510,511],{},"Estimations"," parent page. Capacity archives sit under the ",[23,514,515],{},"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":149,"searchDepth":150,"depth":150,"links":518},[519,520,521],{"id":453,"depth":150,"text":454},{"id":482,"depth":150,"text":483},{"id":504,"depth":150,"text":505},"Archive planning sessions, capacity plans, stand-ups and retrospectives to Confluence, with a clear page hierarchy.","Archiving your plans","\u002Fog\u002Ftutorial-archiving.jpg",[526,527,528],"confluence archive","planning archive","retrospective archive",{},15,"\u002Ftutorials\u002Farchiving",{"title":445,"description":522},{"loc":531,"lastmod":160},"archiving","tutorials\u002Fen\u002Farchiving","tutorial\u002Farchiving","LUADFXzNR2iP2wk39AwMP3Kv49FDRx0r3OwXBe_zD0Y",{"id":539,"title":540,"body":541,"dateModified":1480,"datePublished":1481,"description":1482,"extension":162,"heading":25,"image":1483,"imageAlt":25,"keywords":1484,"locale":168,"meta":1486,"navigation":170,"order":435,"path":1487,"section":1488,"seo":1489,"sitemap":1490,"slug":176,"stem":1491,"translationKey":1492,"__hash__":1493},"guide\u002Fguide\u002Fen\u002Fcapacity-planning.md","Capacity planning | Scrumpy Planning Poker",{"type":8,"value":542,"toc":1465},[543,546,553,556,573,604,609,613,625,628,640,646,652,658,662,665,668,724,734,737,740,743,751,765,768,774,781,809,821,824,829,840,849,855,861,880,884,890,910,913,929,933,939,942,945,971,974,984,987,992,995,999,1033,1039,1042,1045,1080,1083,1096,1103,1106,1110,1115,1147,1150,1154,1157,1176,1182,1186,1213,1269,1275,1279,1288,1294,1298,1306,1310,1318,1338,1341,1345,1348,1374,1380,1394,1397,1423,1426,1429,1433,1462],[11,544,545],{},"Capacity planning helps a Scrum team decide how much work fits into the next sprints. Scrumpy looks at the estimates your team completed in recent sprints. That average per team member is your velocity. A board that estimates in story points uses story points, and a board that estimates in time uses the original time estimates and shows them as durations such as 2 days, 4 hours. Capacity uses the estimation field configured on the selected board. If the space also has another story point field, the board's field is the one that counts.",[11,547,548,549,552],{},"Scrumpy then compares the work already planned for the next sprints with the capacity your team really has. The target capacity for a current or future sprint is that per-member velocity multiplied by the sprint's team size and adjusted by the team's utilization and time off. The ",[23,550,551],{},"Deviation"," dropdown sets how far the plan may differ from the target before a badge turns green or red. The working week settings decide which days count as working days and how many hours a full working day counts for.",[11,554,555],{},"In the Capacity planning tab you can:",[350,557,558,561,564,567,570],{},[353,559,560],{},"Add the closed sprints that set your velocity and the active or future sprints you want to plan.",[353,562,563],{},"See every sprint and its work items in one table, with the estimated total and the target range.",[353,565,566],{},"Adjust each team member's utilization and working hours for the sprint.",[353,568,569],{},"Rank the work items, or open a perspective tab and vote on them.",[353,571,572],{},"Apply the plan to Jira, or archive a sprint to Confluence.",[11,574,575,576,578,579,582,583,586,587,590,591,594,595,598,599,601,602,57],{},"Capacity belongs to a planning session. Open the ",[23,577,25],{}," tab on the space page and choose a planning session tab. When the session you last opened is no longer available, the first planning session opens instead. The ",[23,580,581],{},"Create"," button creates a planning session without leaving the tab. The planning session description, when one is set, appears at the top of the left side above the board selector and spans only the left side, so the right side starts higher and the tables line up. A moderator can click the description to change it in place, and it saves when the field loses focus with no ",[23,584,585],{},"OK"," or ",[23,588,589],{},"Cancel"," buttons. The same planning sessions also appear on the ",[23,592,593],{},"Standup"," and ",[23,596,597],{},"Retrospective"," tabs, where you can run a sprint standup or retrospective. See the Sprint standups and Sprint retrospectives guides. When no description is set, a moderator sees a placeholder they can click to add one. Each board in the planning session keeps its own planned sprints, selected sprint, selected work item, selected team member, and open right-side tab. Switching boards does not clear another board's choices, and switching back restores them. The switch happens at once: the board's saved sprint, work item, and team member selection and its estimation unit change immediately, and the previous board's sprints are hidden while the new board loads. A board you already opened in this tab shows its sprints immediately and refreshes in the background. When the space page opens on the ",[23,600,25],{}," tab, the tab loads its boards and sprints together with the planning session tabs, so the table appears in one step. If you open the tab later, it loads its boards and sprints when you select it. If the space has no Scrum board, the tab tells you that a Scrum board is needed. A new planning session starts with no sprints, so add the sprints you want to plan with ",[23,603,29],{},[11,605,606],{},[23,607,608],{},"Everything you change on this screen is virtual: the sprints, the order, the team capacity, and the work item moves stay in Scrumpy. Jira changes only when you select Apply.",[15,610,612],{"id":611},"plan-the-sprints","Plan the sprints",[11,614,615,616,618,619,621,622,57],{},"Only the sprints you add to the selected board's view appear in the table. Select ",[23,617,29],{},", next to ",[23,620,84],{}," in the toolbar, to open the sprint picker. The picker shows only sprints whose origin board is the board selected in the action bar. Sprints that originated on another board are not listed and cannot be added. Each sprint's estimate appears in a regular lozenge, for example ",[23,623,624],{},"3 sp",[11,626,627],{},"The picker has two tabs:",[350,629,630,635],{},[353,631,632,634],{},[23,633,33],{}," lists closed sprints. Past sprints with a saved team are needed to calculate the velocity. Select at least 3 past sprints for a proper velocity calculation. If you select fewer, the velocity is calculated from the ones you selected. A past sprint with no team yet shows 0% in the Team column and does not count; select it and populate its team first.",[353,636,637,639],{},[23,638,52],{}," lists active and future sprints. Select at least one of them before you can add the selection.",[11,641,642,643,645],{},"Both tabs list their sprints by start date, oldest first. Each row has a checkbox, the sprint name with its goal below it, its status, its start and end dates, and its estimate. The sprint column is headed ",[23,644,130],{},", because each row is one sprint. The estimate is the completed estimate for a past sprint and the currently allocated estimate for an active or future sprint. On a time board the estimate appears as a badge. The start and end dates are read only.",[11,647,648,649,651],{},"Use the checkbox in the header to select every sprint that is currently listed in the tab. Above the table on the right, the search box filters the sprints by name. The ",[23,650,33],{}," tab also has a dropdown that chooses how many of the most recent closed sprints to show: 3, 6, or 9. The default is 3. The choice is remembered in this browser tab.",[11,653,654,655,657],{},"Sprints that are already in the planning session appear checked and cannot be selected again. ",[23,656,56],{}," is enabled only when at least one active sprint is selected. Past sprints are optional.",[15,659,661],{"id":660},"read-the-sprints","Read the sprints",[11,663,664],{},"The left side shows the combined sprint table. Sprint rows and work item rows share the same columns, so every value lines up vertically:",[36,666],{"alt":25,"caption":25,"stem":667},"guide-capacity",[350,669,670,676,682,691,700,706,711],{},[353,671,672,675],{},[23,673,674],{},"Type"," shows the sprint icon on a sprint row and the work item type icon on a work item row. The column header uses the work-item icon.",[353,677,678,681],{},[23,679,680],{},"Priority"," shows the work item's Jira priority icon in its Jira color. Sprint rows leave it empty. The column header uses the priority-medium icon.",[353,683,684,687,688,690],{},[23,685,686],{},"Sprint \u002F Work item"," shows the sprint name in bold, which opens the sprint in Jira in a new tab, or the work item key. A sprint goal appears in small text below the sprint name and stays on one line: a goal that is too long is shortened with an ellipsis. Moderators edit the goal in the ",[23,689,130],{}," tab.",[353,692,693,696,697,699],{},[23,694,695],{},"Rank"," shows the saved ordinal rank of each work item in its sprint. Current and future sprint rows show a moderator-only customize button instead, and a work item without a rank shows 0. The column appears only when you select ",[23,698,695],{}," in the columns dropdown. Everyone sees the saved numbers read only.",[353,701,702,705],{},[23,703,704],{},"Status"," shows the sprint state on a sprint row. On a work item row it shows the work item's Jira status until the work item starts. An In Progress work item shows its completion percentage instead. On a story point board moderators edit it. On a time board it is read only and derived from the time spent divided by the original time estimate. A Done work item shows a read-only 100%. To Do work items keep their Jira status.",[353,707,708,710],{},[23,709,551],{}," shows values only on sprint rows that have a deviation. Work item rows and sprints without a deviation leave it empty.",[353,712,713,716,717,719,720,723],{},[23,714,715],{},"SP"," on a story point board and ",[23,718,385],{}," on a time board shows the allocated estimate on a sprint row and the estimate on a work item row. Story point values end with ",[23,721,722],{},"sp",". Time values are original time estimates shown as work-day durations such as 2 days, 4 hours. A work item with no estimate leaves the cell empty.",[11,725,726,727,205,729,209,731,733],{},"The ",[23,728,695],{},[23,730,704],{},[23,732,551],{}," columns are centered, and the estimate column is right aligned. These columns take only the width their content needs. Scrumpy reads the estimate through Jira's board estimation, so the value and the timeline appear even when the estimation field is hidden from the work item screen. A work item saved in a sprint plan but hidden from you by Jira issue-level security stays out of the table, the rank list, and the removed list, so the plan never reveals it. Only the sprint row whose radio button is selected is highlighted, and this includes a selected closed sprint. Work item rows are highlighted the same way: only the work item whose radio button is selected is highlighted, and no work item row is highlighted while none is selected. Selecting a work item also selects its parent sprint row, so the team table and the right side follow that sprint.",[11,735,736],{},"Moderators see the capacity timeline in the first column and the bulk selection checkboxes in the second column. Non-moderators see the moderator selection column first, with the capacity timeline second. Each active or future sprint row starts the timeline with a hollow circle, each work item row has a circle, and the last work item row in the sprint ends it with a hollow circle. Closed sprints have no timeline, and the table header has no line. The line and circles use the cumulative estimate from the first work item through the current row, with the estimate total and both range bounds rounded to whole story points, or to the nearest hour on a time board: green below the rounded target capacity minus the deviation, yellow inside the rounded range including both ends, and red above the rounded target capacity plus the deviation. The target capacity is the per-member velocity multiplied by the selected team's size and adjusted by its capacity for that sprint.",[11,738,739],{},"Active and future sprint rows show their allocated estimate as a colored badge using the same rounded bands. Closed sprint rows show their completed estimate with the completion bands described below.",[11,741,742],{},"A current or future sprint row is followed directly by that sprint's work items, so every work item stays grouped under its sprint. A closed sprint row has no work items below it.",[11,744,745,746,586,748,750],{},"When a moderator accepts an estimate in a perspective tab, the ",[23,747,715],{},[23,749,385],{}," value changes right away on the work item row and on its sprint row. Everyone with the tab open sees the new value without reloading. If the accepted work item belongs to a closed sprint, that sprint's totals and the velocity used for the targets are recalculated.",[11,752,753,754,205,757,760,761,764],{},"Each sprint row shows its state: ",[23,755,756],{},"Closed",[23,758,759],{},"Current"," for the sprint that is running now, or ",[23,762,763],{},"Future",". Select a sprint name to open that sprint in Jira in a new tab. A past sprint opens its sprint report, and the current or a future sprint opens the board backlog.",[11,766,767],{},"Use the radio button beside any sprint, including a closed one, to select it. The selected sprint drives the team table. Selecting a work item selects its parent sprint too.",[11,769,770,771,773],{},"Use the checkbox on a sprint row to select the whole sprint. When at least one sprint is checked, ",[23,772,88],{}," asks you to confirm before it removes the sprints, together with their work items, from this capacity plan. Jira is not changed. Their draft plans and team settings stay with the planning session and come back if you add the sprint again. The header checkbox still selects work items only. Bulk selection checkboxes are available to moderators only, and checking a row is never shared with other participants or saved with the planning session.",[11,775,776,777,780],{},"Non-moderators see a yellow ",[23,778,779],{},"M"," badge in that first column instead. It marks the sprint and the work item that the moderator has selected. The badge stays visible whether you follow the moderator or view another sprint or work item locally, so the moderator's place is always clear.",[11,782,783,784,786,787,789,790,792,793,796,797,205,800,209,802,805,806,808],{},"Above the combined table, the Scrum board selector sits at the top left, while the columns and ",[23,785,551],{}," dropdowns sit at the top right. The columns dropdown is available to everyone. It starts with ",[23,788,551],{}," selected. Select ",[23,791,695],{}," to add the Rank column before Status, select ",[23,794,795],{},"Utilization"," to show the Utilization column in the team capacity table, and clear an option to hide its column. A moderator shares the visible columns with everyone who is locked to the moderator. If you pick another selection while you are locked, you detach and keep your own choice in this browser tab. Moderators can change the board and deviation, and non-moderators see the same values read only. The board choice is remembered with the planning session. Selecting another board applies that board and its saved view at once, and the table shows the new board's sprints or its loading state instead of the previous board's rows. Each board keeps its own sprint selection. The board list groups boards under ",[23,798,799],{},"Story points",[23,801,385],{},[23,803,804],{},"No estimation",". Boards without an estimation field appear under ",[23,807,804],{}," and are disabled. The sprint table lists the selected sprints by their start date, oldest first.",[11,810,811,812,814,815,817,818,57],{},"To the right of the ",[23,813,551],{}," dropdown, the app switcher button opens ",[23,816,459],{}," on the same planning session tab. Its tooltip says ",[23,819,820],{},"Switch to refinement\u002Fgrooming",[11,822,823],{},"The velocity is the average completed estimate per team member across the selected closed sprints that have a saved team. On a time board the completed estimate is the original time estimate of the Done work items. Each closed sprint contributes its completed estimate divided by its effective team size: two people at 50% count as one person, and a 2-person team that completed 10 points contributes 5 points per member. The per-member values are then averaged, so a sprint with a bigger team does not outweigh a sprint with a smaller team. A closed sprint with no saved team shows 0% in the Team column and does not count towards the velocity until you populate its team. Adjusting a closed sprint's team size or team capacity changes its contribution and the velocity. The table updates the closed sprint's Team value, the velocity, and every future target as soon as you change a team member's capacity or membership, before the save finishes. If the save fails, the previous values return. The target for an active or future sprint is the per-member velocity multiplied by that sprint's effective team size, which is its headcount adjusted by utilization and time off. For example, 10 points with 2 people and 15 points with 4 people average 4.375 points per member, so a sprint with 3 people at full capacity targets 13.125 points. The timeline and the allocated estimate badges compare the planned estimate with that target, not with the velocity.",[11,825,726,826,828],{},[23,827,551],{}," column shows only a signed estimate badge, rounded to whole story points, or to the nearest hour on a time board. For a closed sprint, the value is the difference between completed and allocated estimate: negative when less was completed and positive when more was completed. For an active or future sprint, it compares the target capacity with the remaining estimate after completion instead: positive when the remaining estimate is below the target and negative when it is above it. The percentage is not displayed.",[11,830,831,832,716,834,836,837,839],{},"The estimate column is ",[23,833,715],{},[23,835,385],{}," on a time board. It shows the completed estimate on a closed sprint row, the allocated estimate on an active or future sprint row, and the estimate of the work item on a work item row. Story point values end with ",[23,838,722],{},". Time values are original time estimates shown as work-day durations such as 2 days, 4 hours. Work item estimates use the same green, yellow, and red bands as the timeline, calculated from the rounded cumulative remaining estimate through that row. Active and future sprint badges use the same rounded target bands from the remaining estimate: green below the range, yellow inside it, and red above it. Closed sprint badges compare the rounded completed estimate with the rounded allocation range: red below it, yellow inside it up to but not including the upper bound, and green at or above the upper bound. All three uses derive their lower and upper bounds from the same rounded healthy-range calculation. Active and future sprint rows show only that one estimate badge in the column.",[11,841,842,843,845,846,848],{},"For an active or future sprint, an In Progress work item shows its completion percentage in the ",[23,844,704],{}," column. On a story point board moderators can change it and everyone else sees it read only. On a time board it is always read only and derived from the time spent divided by the original time estimate. The derived value is rounded to a whole percent and stays between 0 and 100, so time spent above the original estimate counts as 100% and a missing original estimate counts as 0%. A Done work item shows a read-only 100%. To Do work items have no completion field. On a story point board the percentage is saved with the planning session and is never written to Jira. The remaining estimate is the item estimate reduced by its completion, so 2 sp at 50% counts as 1 sp, and on a time board 2 days at 50% counts as 1 day. A Done item counts as 0 remaining. The estimate column still shows the original allocated estimate on sprint and work item rows, while the ",[23,847,551],{}," and timeline use the remaining estimate. Manual completion does not change the velocity.",[11,850,726,851,854],{},[23,852,853],{},"Team"," column after the estimate column shows the team capacity percentage used for the sprint. Active and future sprints, and closed sprints with team members, show the capacity calculated from those members' working time and utilization. The value is read only. A closed sprint with no saved team shows 0% and does not count towards the velocity, and a saved team with no effective capacity also shows 0%. Work item rows leave the Team cell empty.",[11,856,857,858,860],{},"Use the ",[23,859,551],{}," dropdown to allow 0%, 5%, 10%, 15%, 20%, or 25% deviation from the target. The deviation badge uses the regular style when the absolute deviation percentage is within that tolerance. Above the tolerance, a positive deviation is green and a negative deviation is red. The chosen deviation is saved with the planning session's capacity data.",[11,862,863,864,868,869,871,872,875,876,879],{},"Below the table, a right-aligned summary reads \"Team is at ",[865,866,867],"span",{},"capacity"," capacity and velocity of ",[865,870,167],{},", aiming to complete ",[865,873,874],{},"target"," at healthy range of ",[865,877,878],{},"range","\", with the capacity and velocity shown as information badges. The capacity is the selected team's capacity percentage rounded to a whole number, and the velocity is the per-member velocity multiplied by the selected sprint's team size, so it is the full-capacity velocity of that team. The target appears as an information badge with the target capacity rounded to whole story points, or to the nearest hour on a time board. The healthy range uses two information badges, one for the lower bound and one for the upper bound, separated by a dash. Both bounds are the same rounded values used by the timeline and the estimate badges. For example, a 10% deviation around 20.4 sp shows 18 sp - 22 sp, and around 2 days, 4 hours shows 2 days, 2 hours - 2 days, 6 hours. When both ends round to the same value, a single badge shows that value.",[15,881,883],{"id":882},"work-items-and-drag-and-drop","Work items and drag and drop",[11,885,886,887,889],{},"The work item rows below a sprint use the same columns as the sprint rows. The ",[23,888,704],{}," column shows the work item's own Jira status.",[350,891,892,895,901,904,907],{},[353,893,894],{},"Use the radio button on a work item to select it. The selection is remembered with the planning session. Its parent sprint row is selected with it.",[353,896,897,898,900],{},"Use the checkboxes to select work items for ",[23,899,88],{},". The header checkbox selects every work item in the table, across every sprint.",[353,902,903],{},"Use the checkbox on a sprint row to remove that sprint from the planning session, as described above. Sprint checkboxes are separate from the work item header checkbox.",[353,905,906],{},"Drag a work item to reorder it inside its sprint, or drag it onto another sprint row to move it into that sprint.",[353,908,909],{},"Closed sprints are history only, so they have no work items to drag.",[11,911,912],{},"The selection controls store their choice with the selected board's view. Only moderators can change the shared selections. The selected sprint, work item, team member, and right-side tab are remembered with the board view.",[11,914,915,916,919,920,205,922,205,924,209,926,928],{},"Non-moderators see a ",[23,917,918],{},"Lock to moderator"," checkbox below the table. It is checked by default, so your view follows the moderator's sprint, work item, team member, visible columns, and right-side tab. It follows the moderator between ",[23,921,459],{},[23,923,25],{},[23,925,593],{},[23,927,597],{}," for the same planning session. It applies to the planning tab you are on: switching to another planning tab yourself clears it, so you start detached on the new tab. Clear the checkbox to stay on the current view, then choose a sprint, work item, team member, column selection, or tab to look at without changing what anyone else sees. Choosing one clears the lock automatically. Select the checkbox again to return to the moderator's view. The lock is remembered in this browser tab while you stay on the tab. Your local choices stay with the tab where you made them, and they never change what the moderator or other participants see.",[15,930,932],{"id":931},"rank-the-work-items","Rank the work items",[11,934,935,936,938],{},"Select ",[23,937,695],{}," in the columns dropdown to show the Rank column. The column sits before Status and uses only the width its numbers need. A work item without a rank shows 0. Each planning session you open loads its capacity data. Switching to another planning session loads it once, and returning to one you already opened shows its data right away.",[11,940,941],{},"On every current or future sprint row, moderators see a customize button in the Rank cell. Select it to open the ranking dialog for that sprint. Closed sprint rows and the view that non-moderators see have no button.",[11,943,944],{},"The dialog explains that it sets the order of the sprint's work items from the selected ranking. Choose a ranking:",[350,946,947,953,959,965],{},[353,948,949,952],{},[23,950,951],{},"Board rank"," uses the work item's position in the Jira sprint order.",[353,954,955,958],{},[23,956,957],{},"Votes"," uses the number of Jira votes on the work item.",[353,960,961,964],{},[23,962,963],{},"Affinity rank"," uses the selected perspective's affinity ranking from the planning session.",[353,966,967,970],{},[23,968,969],{},"Dot rank"," uses the selected perspective's dot ranking from the planning session.",[11,972,973],{},"A ranking that has no values for the sprint is shown in the dropdown but cannot be selected. This happens when Jira returns no board rank or vote counts, or when the selected perspective has no affinity or dot ranking yet. Nothing in the dialog warns you about it: choose another ranking, or add the missing data in the planning session. When you change the perspective, the ranking falls back to the first option that has values if the current one does not.",[11,975,976,977,586,980,983],{},"Choose ",[23,978,979],{},"Ascending",[23,981,982],{},"Descending"," for the sort order. For Affinity rank and Dot rank, a Perspective dropdown appears beside the other two so you can choose which perspective's ranking to use. The Default perspective is selected first.",[11,985,986],{},"Below the dropdowns, a preview table lists the work items in their new order. It shows the work item type icon, the work item key, and the Rank number in a neutral badge. The Type column header uses the work-item icon. The Rank column uses 10 percent of the preview width, and the Rank header and its cells are right aligned. Rank numbers are bound to the work items, not to their row position. Each source has a natural order: lower Board rank and lower Affinity position are better, while higher Votes and higher Dot counts are better. Ordinal numbers are assigned once in that order, so changing between Ascending and Descending reverses both the rows and the displayed numbers. For Dot rank, Ascending shows the most-dotted work item first, and Descending reverses the whole list, including the work items with 0 dots. With Votes, the Rank cell shows the work item's vote count, including 0, instead of an ordinal position. With Dot rank, a work item with no dots shows 0. A work item with no value for the selected ranking shows 0 and follows the ranked work items. Apply saves a number for every work item in the sprint.",[11,988,935,989,991],{},[23,990,92],{}," to save the new order and the rank numbers for the sprint. The dialog closes and the Rank column shows the numbers. If the save fails, the dialog stays open with an error message, and the previous order stays in place.",[11,993,994],{},"Non-moderators see the saved rank numbers read only. Dragging a work item, adding work items, or removing work items keeps the saved numbers attached to the work items. A work item moved to another sprint or removed from the plan loses its number, and a moved or newly added work item shows 0 until you apply a ranking again. Applying the capacity plan to Jira keeps the rank numbers.",[15,996,998],{"id":997},"plan-the-team","Plan the team",[11,1000,1001,1002,205,1004,1006,1007,1009,1010,1012,1013,1015,1016,1018,1019,1021,1022,1024,1025,594,1027,1029,1030,1032],{},"The right side has ",[23,1003,116],{},[23,1005,130],{},", a tab for each perspective that estimates with the same board you selected, and ",[23,1008,141],{},". The perspective tabs appear only when a work item is selected in the combined table. Their titles stay on one line and are not shortened with an ellipsis. The selected tab is shared with the planning session, so participants who are locked to the moderator follow the moderator's tab. Choosing another tab while locked keeps that tab for you only and clears the lock. A yellow ",[23,1011,779],{}," badge marks the tab the moderator is viewing. Every non-moderator sees it, whether or not ",[23,1014,918],{}," is checked, and it stays on the moderator's tab while you look at another tab locally. ",[23,1017,116],{}," shows the team for the selected sprint. ",[23,1020,130],{}," shows the selected active or future sprint's Jira fields. Each perspective tab shows the voting panel for the selected work item. The ",[23,1023,141],{}," tab at the right end of the tab bar always shows the full session conversation: every message sent from the planning session, plus messages sent from outside the session for the work items in the capacity plan, ordered by publish time. Selecting a work item, selecting no work item, or selecting a closed sprint does not change the conversation. A selected work item only chooses where a new message is sent: the work item chat. With no selection or a closed sprint, a new message goes to the planning session chat. Every work item message keeps its work item key link, in every chat panel. Your own messages sit on the right side of the conversation, and messages from other participants sit on the left. When you select a closed sprint, only ",[23,1026,116],{},[23,1028,141],{}," stay visible, and the ",[23,1031,130],{}," and perspective tabs are hidden. Your role badge and the sound bell always sit at the right end of the tab bar. The badge opens the Permissions settings, and the bell turns sound notifications on or off. When an active or future sprint has no stored team, Scrumpy fills its team from the people assigned to that sprint's work items while those items were In Progress, then stores it for that sprint. A moderator who selects a past sprint with no team is asked first because reading its history can take a while; a non-moderator sees the empty team read only. Cancel selects the sprint without populating its team. If you accept, the dialog stays open with a spinner and a message to wait until population finishes. If nobody was assigned while an item was In Progress, the team stays empty, and selecting the sprint again offers to populate it again. After that, moderators manage the list from the bulk action bar below the table. New assignees are not added automatically once a team is stored. Each sprint keeps its own team list.",[11,1034,1035,1036,1038],{},"The team table follows the sprint selected in the combined table. The checkboxes select team members for the bulk actions. The checkbox in the table header selects everyone at once. The member checkboxes are available to moderators only, are used only for the bulk actions, and are never shared with other participants. Non-moderators see a narrow first column with no header that shows a yellow ",[23,1037,779],{}," badge on the team member whose calendar the moderator has open. The badge stays on that member while you open another member's calendar yourself.",[11,1040,1041],{},"A moderator can change every team member's utilization and working hours. A team member can change their own utilization and working hours for a sprint where they are on the team. This also works for a closed sprint that has a recorded team, so you can correct the team size and team capacity used for the velocity. If the closed sprint has no team yet, you can add members and set their capacity; the sprint starts counting towards the velocity as soon as it has a saved team. Adding or removing a team member updates the team table and every calculated value right away, before the save finishes. If the save fails, the previous team and values return. You can open any team member's calendar. A calendar you cannot change opens read only, and its hours of work and utilization are shown as disabled fields, so the values line up with the editable view.",[11,1043,1044],{},"For each team member:",[350,1046,1047,1050,1053,1063,1071,1074,1077],{},[353,1048,1049],{},"Change the overall utilization percentage to show part-time availability. The default is 100%.",[353,1051,1052],{},"Select the radio button next to the team member to open their calendar, then select the days they cannot work a full day. Select a highlighted day again to remove it. The calendar only shows dates inside the selected sprint, and it opens on the month of the sprint start date instead of the current month. The weekend days chosen in the space's Working week settings are disabled and do not count as working days.",[353,1054,726,1055,1058,1059,1062],{},[23,1056,1057],{},"Hours of work"," column shows the hours the team member can work out of the sprint's total working hours, for example 72h out of 80h. Both values appear as badges. When the calendar is open, each marked day shows a small cross-circle button, its date in a read-only date picker, and an hours field next to it. The hours field accepts 0 to the ",[23,1060,1061],{},"Maximum daily hours"," set in the space's Working week settings (13h by default). A newly marked day starts at 0 hours. Select the cross-circle button to remove that day from the team member's calendar.",[353,1064,726,1065,1067,1068,1070],{},[23,1066,795],{}," column shows the overall utilization. When the calendar is open, a utilization field for every marked day sits next to it. A day with no hours of work keeps its utilization field disabled, because that day adds no capacity. The reverse also holds: a day at 0% utilization keeps its hours of work field disabled, because those hours would be multiplied by zero. When both values are 0, the hours field stays editable so the day can be corrected. The column is hidden until you select ",[23,1069,795],{}," in the columns dropdown, and hiding it also hides the per-day utilization fields of an open calendar.",[353,1072,1073],{},"A marked day starts at 0h. Raise the hours for a partial day, for example 6h. Days you do not mark count as a full working day at 100%, using the work hours from the space's working week settings (8h by default).",[353,1075,1076],{},"A marked day can also be longer than the regular work hours, for example 10h when the work hours are 8h. The extra hours raise that team member's total available hours above the sprint's regular total, for example 44h out of 40h, and increase their share of the team capacity and every target that uses it.",[353,1078,1079],{},"The overall utilization applies on top of each day. With 90% overall utilization, a day with 6h at 60% counts as 3.24h of a normal working day.",[11,1081,1082],{},"Below the team table, moderators see a small note on the right. It explains that to record time off or another deviation from the regular working hours per day, you open the team member's calendar and then select a date during the sprint. It also explains that the team member's sprint utilization is applied on top of each exception day's utilization.",[11,1084,1085,1086,1089,1090,1092,1093,1095],{},"Below the table, moderators see the team bulk action bar. Select ",[23,1087,1088],{},"Add team members"," to open a dialog, choose one or more people, and select ",[23,1091,56],{},". The selected people join the team for the selected planned sprint and start with 100% utilization and full working hours. To remove team members, check them in the table and select ",[23,1094,88],{},". If any selected team member has time off records in that sprint, a confirmation dialog explains that their time off records will be lost. Confirm the removal to continue; if there are no time off records, the members are removed immediately. Removing a team member deletes their saved utilization and time off for that sprint only. Other planned sprints keep their own team lists. Only moderators can add or remove team members.",[11,1097,1098,1099,1102],{},"To clear time off in that sprint, check the members and select ",[23,1100,1101],{},"Clear time off",". A confirmation dialog explains that their time off (Hours of work) entries will be deleted and their utilization reset to 100%. Confirm to continue. Each selected member returns to the regular working hours and full utilization. The clear control stays disabled when no selected member has something to clear.",[11,1104,1105],{},"The selected team member is remembered with the board view. The target updates as you change these values. The leftover value is negative when less was completed than was allocated and positive when more was completed. The leftover badges use the regular style when the absolute leftover percentage is at or below the deviation. Above the deviation, positive is green and negative is red.",[15,1107,1109],{"id":1108},"the-selected-sprint","The selected sprint",[11,1111,726,1112,1114],{},[23,1113,130],{}," tab edits the sprint selected in the combined table. It is available for active and future sprints only. When a closed sprint is selected, the tab is hidden.",[350,1116,1117,1134,1140],{},[353,1118,1119,205,1122,205,1125,209,1128,1131,1132,57],{},[23,1120,1121],{},"Sprint name",[23,1123,1124],{},"Sprint goal",[23,1126,1127],{},"Start date",[23,1129,1130],{},"End date"," are kept in the plan as you edit them. The table shows the new name right away and recalculates the sprint target and team day range from the new dates. Jira is not changed until you select ",[23,1133,92],{},[353,1135,1136,1137,1139],{},"Below the ",[23,1138,1124],{}," field, a square thumbs up button and a square thumbs down button let voters agree or disagree with the text. The number of votes appears beside each button. A voter can vote, select a button again to remove the vote, and the counts update for everyone. Guests see the counts but cannot vote. Votes reset when the goal text changes.",[353,1141,1142,1143,1146],{},"Sprint state changes happen in Jira, not in this tab. To start or complete a sprint, use the Jira backlog or the active sprints page, then select ",[23,1144,1145],{},"Refresh"," in the capacity toolbar to reload the plan. A started sprint shows as the current sprint, and a completed sprint leaves the plan.",[11,1148,1149],{},"Moderators can edit these fields. Non-moderators see the same values read only.",[15,1151,1153],{"id":1152},"vote-on-work-items-from-capacity-planning","Vote on work items from capacity planning",[11,1155,1156],{},"A perspective appears as a tab in the team section when its estimation target is the board and its estimation board is the same board you selected above the combined table. A perspective that writes estimates to Jira fields instead, or estimates with another board, does not appear.",[11,1158,1159,1160,1163,1164,205,1167,209,1169,1172,1173,1175],{},"Select a work item in the combined table, then open its perspective tab to vote. The perspective tabs appear only after a work item is selected. The tab shows the same voting panel as the Refinement\u002Fgrooming tab: the perspective header, the voting cards, the participant list, the session controls, and the final result with ",[23,1161,1162],{},"Accept",". While a session runs, the ",[23,1165,1166],{},"Vote",[23,1168,197],{},[23,1170,1171],{},"Details"," sub-tabs stay inside the perspective tab. The ",[23,1174,1171],{}," sub-tab shows the summary and description of the selected work item, and moderators can edit both there. An edit saves when you click away, switch to another sub-tab, or close the panel, even if the short description pause has not finished. If no work item is selected, the perspective tabs are hidden. When you select a closed sprint, the perspective tabs are hidden.",[11,1177,1178,1179,1181],{},"The summary you edit in the voting panel's ",[23,1180,1171],{}," sub-tab also updates the work item tooltip in the combined table.",[15,1183,1185],{"id":1184},"the-capacity-toolbar","The capacity toolbar",[11,1187,1188,1189,1191,1192,1194,1195,594,1198,1201,1202,1204,1205,594,1207,1209,1210,1212],{},"Below the table, moderators see the same style of toolbar as the Refinement\u002Fgrooming tab. The board selector sits above the top left corner of the combined table, while the ",[23,1190,551],{}," dropdown and the columns control sit above the top right corner. ",[23,1193,92],{}," uses the warning colour. ",[23,1196,1197],{},"Edit",[23,1199,1200],{},"Delete"," sit in the row above the session tabs, beside ",[23,1203,581],{},", and they appear only while a session is open. ",[23,1206,463],{},[23,1208,92],{}," follow ",[23,1211,1145],{}," in the toolbar with a gap; they do not sit at the right edge:",[350,1214,1215,1223,1237,1242,1247,1252,1257,1262],{},[353,1216,1217,1219,1220,1222],{},[23,1218,1197],{},", beside ",[23,1221,581],{},", changes the planning session title, description, and dates. The new title and description appear on the tab, in the planning header, and in the progress bar right away, and they return to the saved values if the save fails. A message then tells you that the planning session could not be saved.",[353,1224,1225,1227,1228,1230,1231,1233,1234,1236],{},[23,1226,84],{}," adds work items from a saved Jira filter, a sprint, a Refinement\u002Fgrooming planning session, or a retrospective to the selected sprint plan. The picker starts with a ",[23,1229,459],{}," group that lists the planning sessions with work items; selecting one previews that session's work items. A ",[23,1232,597],{}," group follows it and lists the planning sessions whose retrospective action items are linked to Jira work items. Select one to preview the linked work items. The ",[23,1235,597],{}," group is hidden when no action item is linked to a work item. It only offers work items from the current space that are not already in the selected sprint plan. To start over, clear the picker: the chosen source is dropped, the search box empties, and the first 100 shared filters return.",[353,1238,1239,1241],{},[23,1240,29],{}," opens the sprint picker described above.",[353,1243,1244,1246],{},[23,1245,88],{}," removes the checked work items from the selected sprint plan, or the checked sprints from the planning session after you confirm. It does not change Jira immediately.",[353,1248,1249,1251],{},[23,1250,1145],{}," reads the sprints and work items from Jira again, including their priorities, summaries, and descriptions. It does not change the plan or Jira.",[353,1253,1254,1256],{},[23,1255,463],{}," creates a Confluence page for the sprint currently selected in the combined table. It is available only when a Confluence space is configured, and it is disabled when a past sprint is selected. The page records the planning session window and duration, the selected sprint and goal, the goal votes, the capacity decision, the velocity summary, the team's hours of work, and the ordered work items with their estimates.",[353,1258,1259,1261],{},[23,1260,92],{}," updates Jira with the plan and the sprint name, goal, and dates you changed.",[353,1263,1264,1219,1266,1268],{},[23,1265,1200],{},[23,1267,1197],{}," above the tabs, closes the planning session. It asks for confirmation, then permanently removes the planning session with its capacity data, votes, notes, action items, standup, and chat.",[11,1270,1271,1272,1274],{},"The planning session progress bar appears below the toolbar. Non-moderators see the ",[23,1273,918],{}," checkbox in the space where the toolbar appears.",[15,1276,1278],{"id":1277},"sprint-goals","Sprint goals",[11,1280,1281,1282,1284,1285,1287],{},"Every sprint goal appears in small text below the sprint name in the table and stays on one line, and a goal that does not fit is shortened with an ellipsis. A sprint without a goal keeps an empty goal line in the table, so the sprint rows and the timeline stay aligned. Moderators edit an active or future sprint goal in the ",[23,1283,130],{}," tab. The goal under the sprint name follows your typing before the draft is saved, and the goal votes reset to 0 as soon as the text changes. The vote buttons stay read only until the goal draft is saved, because the votes always describe the saved goal. A goal change appears for everyone without a reload and reaches Jira when you select ",[23,1286,92],{},". A closed sprint goal is read only. If a goal in Jira contains line breaks, the table shows them as spaces.",[11,1289,1290,1291,1293],{},"The sprint name and dates you change in the ",[23,1292,130],{}," tab also appear in the combined table, the team calendar, and the target as you change them, before the draft is saved. The date fields stay editable while a change is saved, so you can set the start and end dates without waiting, and an older save never rewinds a newer date you picked. A failed save restores the saved name, goal, and dates.",[15,1295,1297],{"id":1296},"move-work-into-the-selected-sprint","Move work into the selected sprint",[11,1299,1300,1301,1303,1304,57],{},"Work items are planned per sprint. Use ",[23,1302,84],{}," to add a work item from a filter, a sprint, a Refinement\u002Fgrooming session, or a retrospective to the selected sprint, drag a work item onto another sprint row to move it into that sprint, or drag within a sprint to reorder its items. The order and sprint membership are saved as a draft. They do not change Jira until you select ",[23,1305,92],{},[15,1307,1309],{"id":1308},"apply-the-plan","Apply the plan",[11,1311,935,1312,1314,1315,1317],{},[23,1313,92],{}," after ",[23,1316,1145],{}," in the toolbar and confirm the change in the dialog. Scrumpy then:",[350,1319,1320,1323,1326,1329,1332,1335],{},[353,1321,1322],{},"Saves the sprint names, goals, and start and end dates you changed.",[353,1324,1325],{},"Moves the planned work items into the selected sprints.",[353,1327,1328],{},"Updates their order inside each sprint using the board's rank field.",[353,1330,1331],{},"Moves work items you removed from a sprint plan to the backlog, but only when they are currently in that sprint. Work items that are in another sprint or already in the backlog stay where they are.",[353,1333,1334],{},"Leaves closed sprints and their estimates unchanged.",[353,1336,1337],{},"Saves a team capacity snapshot for every selected sprint that has a team. The snapshot holds the team members, their working hours, and their utilization, is kept for 12 months, and is not tied to this planning session.",[11,1339,1340],{},"When the update finishes, the page reloads the current Jira data. If Jira refuses part of the change, the page tells you that some sprints could not be updated and keeps the draft so you can try again. A sprint name, goal, or date you have not applied yet is part of the plan, so it also appears in the combined table and in an archive page.",[15,1342,1344],{"id":1343},"archive-the-capacity-plan","Archive the capacity plan",[11,1346,1347],{},"You can save a sprint's capacity plan as a Confluence page, so the team keeps a record of what was planned and why. Only a moderator can archive, and the action is available only after a Confluence space has been configured for the space.",[1349,1350,1351,1357,1362,1365],"ol",{},[353,1352,1353,1354,1356],{},"Select an active or future sprint in the combined table. ",[23,1355,463],{}," is disabled for a closed sprint, because a closed sprint is history only.",[353,1358,935,1359,1361],{},[23,1360,463],{}," in the capacity toolbar.",[353,1363,1364],{},"Review the preview. It shows the sprint and its dates, the sprint goal, the up and down votes, the capacity decision, and the velocity summary. The team and work item tables are written to the Confluence page but are not shown in the dialog.",[353,1366,935,1367,1369,1370,1373],{},[23,1368,463],{}," to create the page, or ",[23,1371,1372],{},"Close"," to leave the capacity plan unchanged.",[11,1375,1376,1377,1379],{},"While the preview loads, ",[23,1378,463],{}," stays disabled. If the preview cannot load, the dialog explains why, and you can close it and try again. When the page is ready, the dialog shows a link to it. If Confluence refuses the page, the dialog shows the reason and your capacity plan is not changed.",[11,1381,1382,1383,1385,1386,1390,1391,1393],{},"The page is written under the ",[23,1384,515],{}," parent page in the configured Confluence space, in a child page named ",[1387,1388,1389],"code",{},"\u003Cspace name> - Capacity planning",". Planning-session archives stay under the separate ",[23,1392,511],{}," parent, so the two kinds of page never overwrite each other. The page title starts with the planning session title, then the sprint name, and the planning start time with the timezone.",[11,1395,1396],{},"The page contains:",[350,1398,1399,1402,1405,1408,1411,1414,1417,1420],{},[353,1400,1401],{},"The planning session title, description, start and end time, and timezone, in the same header as the planning archive page",[353,1403,1404],{},"The planning session duration, as a plain line below that header",[353,1406,1407],{},"The selected sprint name, state, dates, and goal",[353,1409,1410],{},"The up and down votes for the goal",[353,1412,1413],{},"A decision line for the target capacity range",[353,1415,1416],{},"The velocity summary: velocity per member, team velocity, team size, effective team size, team capacity, target capacity, healthy range, planned estimate, remaining estimate, and deviation from target",[353,1418,1419],{},"Every team member in the selected sprint, with their utilization and their hours of work out of the sprint working hours",[353,1421,1422],{},"The work items in their saved order, with their status and estimate",[11,1424,1425],{},"The header is the same one the planning archive page uses: the planning title and description, then the start and end on separate lines, with each date shown as a Confluence date chip and each time highlighted in a blue badge, and the timezone the dates are valid in. The planning duration follows the header as a plain line. The sprint goal and its up and down votes appear centered directly below the sprint name. The team and work item tables use a wider layout, and the Work item column leaves room for a longer summary.",[11,1427,1428],{},"The page shows the capacity plan as it currently appears, including draft changes that you have not applied to Jira yet. On a story point board the values use story points, and on a time board they use work-day durations. Re-archiving the same sprint updates the existing page instead of creating a duplicate.",[15,1430,1432],{"id":1431},"notes","Notes",[350,1434,1435,1438,1444,1447,1453,1456,1459],{},[353,1436,1437],{},"Velocity uses the current completion state of the work items in the closed sprints. A work item that was reopened after its sprint closed counts as not completed. Manual completion percentages on active or future work items do not change the velocity.",[353,1439,1440,1441,1443],{},"The manual completion percentage is saved with the planning session and never written to Jira. ",[23,1442,92],{}," keeps it. On a time board the percentage is not manual: it is recalculated from the current time spent and original time estimate each time the plan loads or refreshes.",[353,1445,1446],{},"Working days exclude Saturdays and Sundays unless you change the weekend days in the space's Working week settings. Mark public holidays as 0h days for each team member.",[353,1448,1449,1450,1452],{},"Velocity uses the saved team size and team capacity of the selected closed sprints. If you select no closed sprints, or none of them has a saved team, the velocity is zero. Before asking you to populate a past sprint that has no saved team, Scrumpy loads the most recent team capacity snapshot from an earlier Apply when one is still available. A past sprint with no saved team and no snapshot shows 0% and does not count. Select it to open its ",[23,1451,116],{}," tab, populate its team, and then correct its size and capacity. A team member who never had a work item In Progress in a sprint does not appear in that sprint's team list.",[353,1454,1455],{},"Removing a sprint from the capacity plan does not delete its saved draft work item order or team settings. Those come back if you add the sprint to the planning session again.",[353,1457,1458],{},"Each planning session has its own capacity data. Switching planning tabs does not change another planning session.",[353,1460,1461],{},"A non-moderator can edit only their own utilization and time off, and only for a sprint where they are on the team. The change is saved for everyone who views that sprint.",[11,1463,1464],{},"Capacity planning data is kept for 90 days after the last change, matching the planning session. Older capacity data is removed automatically. Team capacity snapshots are separate records kept for 12 months after the last Apply that refreshed them.",{"title":149,"searchDepth":150,"depth":150,"links":1466},[1467,1468,1469,1470,1471,1472,1473,1474,1475,1476,1477,1478,1479],{"id":611,"depth":150,"text":612},{"id":660,"depth":150,"text":661},{"id":882,"depth":150,"text":883},{"id":931,"depth":150,"text":932},{"id":997,"depth":150,"text":998},{"id":1108,"depth":150,"text":1109},{"id":1152,"depth":150,"text":1153},{"id":1184,"depth":150,"text":1185},{"id":1277,"depth":150,"text":1278},{"id":1296,"depth":150,"text":1297},{"id":1308,"depth":150,"text":1309},{"id":1343,"depth":150,"text":1344},{"id":1431,"depth":150,"text":1432},"2026-11-21","2026-11-08","Plan sprint capacity from recent velocity, drag work into sprints and let the team vote on what fits.","\u002Fog\u002Fguide-capacity-planning.jpg",[165,166,167,1485],"agile planning",{},"\u002Fgetting-started\u002Fcapacity-planning","guide",{"title":540,"description":1482},{"loc":1487,"lastmod":1480},"guide\u002Fen\u002Fcapacity-planning","guide\u002Fcapacity-planning","o18flU9NCXI_8Fri7sepAw5oIlAYzvcI-Fp5yw9pXO0",1795345576147]