[{"data":1,"prerenderedAt":2051},["ShallowReactive",2],{"blog-en-manage-sprint-dependencies-with-chained-pull-requests":3,"blog-related-en-manage-sprint-dependencies-with-chained-pull-requests":203,"blog-chapter-en-manage-sprint-dependencies-with-chained-pull-requests":606},{"id":4,"title":5,"author":6,"body":7,"dateModified":178,"datePublished":179,"description":180,"extension":181,"heading":182,"image":183,"imageAlt":16,"keywords":184,"locale":190,"meta":191,"navigation":192,"path":193,"reviewed":192,"seo":194,"sitemap":195,"slug":200,"stem":201,"translationKey":200,"__hash__":202},"blog\u002Fblog\u002Fen\u002Fmanage-sprint-dependencies-with-chained-pull-requests.md","Sprint dependencies and chained pull requests | AELBOX","AELBOX",{"type":8,"value":9,"toc":157},"minimark",[10,22,25,34,39,44,53,56,60,63,68,71,75,78,82,85,89,92,100,105,109,112,116,119,123,126,130,133,137,140,144,147,151,154],[11,12,13],"p",{},[14,15],"img",{"alt":16,"height":17,"loading":18,"src":19,"width":20,"fetchPriority":21},"A metal chain, planning poker cards and a coffee cup on a table",960,"eager","\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fcoffee-table-chain.webp",1600,"high",[11,23,24],{},"Sprints often contain dependent tickets, either within one team or across several Scrum teams. In a perfect world, dependencies would not exist; in practice, business needs win and dependencies are added to shorten the release cycle. This article describes one way to manage dependent tasks in software teams.",[11,26,27],{},[14,28],{"alt":29,"height":30,"loading":31,"src":32,"width":30,"decoding":33},"Dependencies between tasks",336,"lazy","\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fblog-dep1.png","async",[11,35,36],{},[37,38,29],"em",{},[40,41,43],"h2",{"id":42},"the-old-fashioned-way","The old-fashioned way",[11,45,46,47,52],{},"The straightforward approach is to start a task as soon as its dependency is merged into the main branch. With that approach, some team members sit idle until a task is ready. Eventually there is little or no time left for the remaining dependent tasks. The last tasks are carried over, and ",[48,49,51],"a",{"href":50},"\u002Fblog\u002Fcomparison-metrics-for-agile-teams","the team is unhappy",".",[11,54,55],{},"Why does this happen even though capacity is correctly estimated? This happens mostly because of idle time while waiting for colleagues to finish. Even small delays compound, especially in short sprints.",[40,57,59],{"id":58},"working-on-dependent-tasks-simultaneously","Working on dependent tasks simultaneously",[11,61,62],{},"There is a way to do this with a small overhead. When team members work on tasks simultaneously, there are several advantages.",[64,65,67],"h3",{"id":66},"better-collaboration","Better collaboration",[11,69,70],{},"When team members work simultaneously on dependent tasks, it resembles pair programming. One person must understand the upstream task; the other must understand the downstream task. The team gains broader knowledge of the problems being solved.",[64,72,74],{"id":73},"avoiding-the-idle-time","Avoiding the idle time",[11,76,77],{},"When tasks run concurrently, nobody waits for a fix to land. Everyone can work at once, with more ad-hoc discussion as questions come up.",[64,79,81],{"id":80},"pull-requests-ready-for-code-review-earlier","Pull requests ready for code review earlier",[11,83,84],{},"When your branch is based on a colleague's branch, approving the original pull request is easier. You already understand how the upstream ticket was implemented, and the original branch has been tested and reviewed throughout implementation. It is no longer unfamiliar territory.",[40,86,88],{"id":87},"using-chained-stacked-pull-requests","Using chained (stacked) pull requests",[11,90,91],{},"This level of concurrency requires the right tooling. With Git-based version control, it is straightforward. The steps below describe the process.",[11,93,94],{},[14,95],{"alt":96,"height":97,"loading":31,"src":98,"width":99,"decoding":33},"Dependency tree",438,"\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fdep-img2.png",800,[11,101,102],{},[37,103,104],{},"Dependency tree (working on 6 dependent tasks simultaneously)",[64,106,108],{"id":107},"outline-the-dependencies-clearly","Outline the dependencies clearly",[11,110,111],{},"Define the dependency chain during sprint planning. The pull request chain then follows that definition exactly. Changing the chain mid-development is expensive because of rebasing.",[64,113,115],{"id":114},"start-with-the-root-tasks-first","Start with the root tasks first",[11,117,118],{},"Every dependency chain has root tasks that depend on nothing else. Work on them can start on day one.",[64,120,122],{"id":121},"do-core-implementation-first","Do core implementation first",[11,124,125],{},"This may conflict with test-driven development, where tests come first. To keep the pull request chain manageable, implement the core first. That gives dependent team members access sooner.",[64,127,129],{"id":128},"organize-and-code-review-in-a-fifo-queue","Organize and code review in a FIFO queue",[11,131,132],{},"The first branch created should be reviewed and merged first. Each merge triggers CI; if it breaks the main build, the problem is fixed while it is still small.",[40,134,136],{"id":135},"the-overhead","The overhead",[11,138,139],{},"Maintaining a chain of dependent branches has benefits, but also some drawbacks.",[64,141,143],{"id":142},"rebasing-or-merging","Rebasing or merging",[11,145,146],{},"The chain must be kept in sync, which takes effort. Modern tools offer one-click synchronization with the base branch when there are no conflicts. Use it on demand, when it is safe to pull in upstream changes. When the build is green and the feature works, sync.",[64,148,150],{"id":149},"teamwork","Teamwork",[11,152,153],{},"A dependency chain needs a collaborative team whose members are willing to talk to each other. It cannot work if people work in isolation.",[11,155,156],{},"Dependent tickets are best kept out of the current sprint. When business needs require them to run in parallel, a chain of derived branches is a practical way to manage the dependency overhead.",{"title":158,"searchDepth":159,"depth":159,"links":160},"",2,[161,162,168,174],{"id":42,"depth":159,"text":43},{"id":58,"depth":159,"text":59,"children":163},[164,166,167],{"id":66,"depth":165,"text":67},3,{"id":73,"depth":165,"text":74},{"id":80,"depth":165,"text":81},{"id":87,"depth":159,"text":88,"children":169},[170,171,172,173],{"id":107,"depth":165,"text":108},{"id":114,"depth":165,"text":115},{"id":121,"depth":165,"text":122},{"id":128,"depth":165,"text":129},{"id":135,"depth":159,"text":136,"children":175},[176,177],{"id":142,"depth":165,"text":143},{"id":149,"depth":165,"text":150},"2026-11-21","2018-05-27","Dependent tickets stall a sprint while people wait. Learn how stacked pull requests keep work moving and reduce idle time.","md","Managing sprint dependencies with chained pull requests","\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fcoffee-table-chain.jpg",[185,186,187,188,189],"sprint dependencies","stacked pull requests","chained pull requests","code review","agile delivery","en",{},true,"\u002Fblog\u002Fen\u002Fmanage-sprint-dependencies-with-chained-pull-requests",{"title":5,"description":180},{"loc":193,"images":196,"lastmod":178},[197,198,199],{"loc":19},{"loc":32},{"loc":98},"manage-sprint-dependencies-with-chained-pull-requests","blog\u002Fen\u002Fmanage-sprint-dependencies-with-chained-pull-requests","wvh2xXsMf-_D4su-7k6V7w5M5HeQzIs6vYvyGaF6jn8",[204,346,510],{"id":205,"title":206,"author":6,"body":207,"dateModified":178,"datePublished":325,"description":326,"extension":181,"heading":327,"image":328,"imageAlt":213,"keywords":329,"locale":190,"meta":335,"navigation":192,"path":336,"reviewed":192,"seo":337,"sitemap":338,"slug":343,"stem":344,"translationKey":343,"__hash__":345},"blog\u002Fblog\u002Fen\u002Fcomparison-metrics-for-agile-teams.md","Comparison metrics for agile teams | AELBOX",{"type":8,"value":208,"toc":316},[209,216,219,223,226,234,238,242,245,249,252,260,264,272,276,279,282,289,293,296,303,306,310,313],[11,210,211],{},[14,212],{"alt":213,"height":214,"loading":18,"src":215,"width":20,"fetchPriority":21},"A ruler, planning poker cards and a coffee cup on a table",958,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Fcoffee-table-ruler.webp",[11,217,218],{},"Comparing agile teams is difficult, and it is worth asking why we compare them at all. How does comparing teams in different domains actually help?",[40,220,222],{"id":221},"creating-a-competition","Creating a competition",[11,224,225],{},"Teams should not be ranked against each other on arbitrary metrics. That only demotivates people. Instead, metrics should give every team an equal opportunity to compete. Performance then improves because teams want it to, not because someone is pushing.",[11,227,228],{},[14,229],{"alt":230,"height":231,"loading":31,"src":232,"width":233,"decoding":33},"Create a competition",487,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun2.png",525,[11,235,236],{},[37,237,230],{},[40,239,241],{"id":240},"the-metrics-for-creating-equal-opportunities","The metrics for creating equal opportunities",[11,243,244],{},"Here are four basic metrics for comparing teams. They measure each team's ability to compete on equal ground, nothing more. Comparable metrics create equal opportunities.",[64,246,248],{"id":247},"successful-sprints","Successful sprints",[11,250,251],{},"If a sprint were only a time frame, it would serve no purpose. A sprint is a milestone and needs a goal. The sprint goal (the most important set of stories) is the larger milestone; completing every story is the smaller one. Hold a cross-team demo at the end of each sprint where teams present what they delivered. That healthy competition encourages teams to finish their sprint goals. People need a visible goal to be motivated.",[11,253,254],{},[14,255],{"alt":256,"height":257,"loading":31,"src":258,"width":259,"decoding":33},"Sprint to a goal",680,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun1.png",874,[11,261,262],{},[37,263,256],{},[11,265,266,267,271],{},"Could this turn into a game of over- and under-commitment? If a team under-commits, the demo makes it obvious: there is less to show. If it over-commits, the demo becomes ",[268,269,270],"strong",{},"yet another failed sprint",". Delivering what the team committed to builds the motivation to do more. Teams feel satisfied with the work.",[64,273,275],{"id":274},"velocity-stability-and-the-honest-estimation","Velocity stability and the honest estimation",[11,277,278],{},"This is knowledge work, not assembly-line work. If nobody on the team understands a problem well enough to estimate its solution, the problem was not researched in advance.",[11,280,281],{},"A time-boxed spike in the previous sprint, followed by a team review of the findings, makes it easy to split the implementation into smaller stories and estimate them properly. For complex work, write a fuller technical design document that lists the implementation stories.",[11,283,284,285,52],{},"The spike and the design work are themselves stories that can be estimated. The key is defining the structure and sequence of work for a complex solution. Instead of committing to a story the team does not understand, create a research task to fill the gap. Then estimation is ",[48,286,288],{"href":287},"\u002Fblog\u002Fsheepherding-story-points","grounded in evidence",[64,290,292],{"id":291},"capacity-predictability-avoiding-unexpected-work","Capacity predictability (avoiding unexpected work)",[11,294,295],{},"Research comes first; implementation follows. As research uncovers problems, new tickets are created and estimated. You then have a much clearer picture of the next sprint. Known work can be estimated and planned; unknown work gets a time-boxed research ticket before it is estimated. The discipline is splitting large work into small, estimable pieces.",[11,297,298,299,52],{},"Complex work can start early, even if only to discover that it needs its own set of stories. That still reduces the ",[48,300,302],{"href":301},"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint","risk of the unknown",[11,304,305],{},"Support and production firefighting usually run in a time-boxed Kanban flow outside the sprint. There, time to first response and SLA breaches become the comparison metrics.",[64,307,309],{"id":308},"team-availability-time-spent-on-tasks-divided-by-total-time-in-a-sprint","Team availability (time spent on tasks divided by total time in a sprint)",[11,311,312],{},"Availability is the share of time team members spend on estimated work. If one team is pulled into training, knowledge sharing or other internal work more often than others, fix the imbalance. The only way to keep velocity stable is to keep availability stable. When availability between teams is equal, the other comparison metrics will work.",[11,314,315],{},"Comparing teams is not about punishing low performance, but about increasing motivation and the spirit to compete and deliver more. That is why those metrics should not be visible to individual team members: they are a tool for coaching, not for public rankings. By tracking these metrics and guiding Scrum Masters indirectly, you give teams equal footing to compete.",{"title":158,"searchDepth":159,"depth":159,"links":317},[318,319],{"id":221,"depth":159,"text":222},{"id":240,"depth":159,"text":241,"children":320},[321,322,323,324],{"id":247,"depth":165,"text":248},{"id":274,"depth":165,"text":275},{"id":291,"depth":165,"text":292},{"id":308,"depth":165,"text":309},"2018-05-04","Metrics should create equal ground, not a leaderboard. Four comparison metrics that motivate agile teams without punishing them.","Comparison metrics for agile teams","\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Fcoffee-table-ruler.jpg",[330,331,332,333,334],"agile metrics","team velocity","agile teams","scrum","capacity",{},"\u002Fblog\u002Fen\u002Fcomparison-metrics-for-agile-teams",{"title":206,"description":326},{"loc":336,"images":339,"lastmod":178},[340,341,342],{"loc":215},{"loc":232},{"loc":258},"comparison-metrics-for-agile-teams","blog\u002Fen\u002Fcomparison-metrics-for-agile-teams","7dD24JRfvLNCanpoMQPK1XHg24wBljL3TZETU2V8M7M",{"id":347,"title":348,"author":6,"body":349,"dateModified":178,"datePublished":487,"description":488,"extension":181,"heading":489,"image":490,"imageAlt":355,"keywords":491,"locale":190,"meta":496,"navigation":192,"path":497,"reviewed":192,"seo":498,"sitemap":499,"slug":507,"stem":508,"translationKey":507,"__hash__":509},"blog\u002Fblog\u002Fen\u002Fsheepherding-story-points.md","Sheepherding story points: anchoring in planning poker | AELBOX",{"type":8,"value":350,"toc":478},[351,357,360,364,371,379,383,387,390,393,400,404,407,411,414,419,423,427,430,437,441,445,448,453,457,461,472,475],[11,352,353],{},[14,354],{"alt":355,"height":17,"loading":18,"src":356,"width":20,"fetchPriority":21},"A flock of sheep and planning poker cards on a coffee table","\u002Fblog\u002Fsheepherding-story-points\u002Fcoffee-table-sheep.webp",[11,358,359],{},"Story point estimation is often neglected or done in chat rooms and open meetings where everyone can see or hear every vote. Knowing how others voted distorts the outcome and produces inaccurate estimates. Repeated inaccurate estimates lead to flawed plans and delayed or canceled deliveries. Here is what happens in an open vote.",[40,361,363],{"id":362},"the-characters-in-voting","The characters in voting",[11,365,366,367,370],{},"Several characters show up in an open estimation vote. The estimate depends on who goes first, and it is usually far from honest. Why does the order matter so much in an open vote? Because of the ",[268,368,369],{},"sheep effect",": the anchoring bias that makes other team members copy the first estimate.",[11,372,373],{},[14,374],{"alt":375,"height":376,"loading":31,"src":377,"width":378,"decoding":33},"The sheep effect",746,"\u002Fblog\u002Fsheepherding-story-points\u002Fsheep-1.png",1779,[11,380,381],{},[37,382,375],{},[64,384,386],{"id":385},"the-overconfident-voter","The overconfident voter",[11,388,389],{},"Every team has at least one member who believes they know the system best. They usually vote first, because the answers seem obvious to them. They often overlook details that can derail the estimate. Those details can be uncovered in advance, but only if someone prompts a discussion. That cannot happen in an open vote.",[11,391,392],{},"This person usually votes lower than the honest estimate. Perhaps only they could finish the story that quickly, and only with luck.",[11,394,395],{},[14,396],{"alt":386,"height":397,"loading":31,"src":398,"width":399,"decoding":33},290,"\u002Fblog\u002Fsheepherding-story-points\u002Fimg7.png",600,[11,401,402],{},[37,403,386],{},[11,405,406],{},"Everyone else follows, so the task looks easy and doable by anyone in the allotted time. In practice, someone else usually ends up doing it.",[64,408,410],{"id":409},"the-quiet-voter","The quiet voter",[11,412,413],{},"There is usually more than one quiet voter, and they are afraid to vote first. They wait for someone else to vote so they can copy it. They rarely join the discussion and answer only when asked. They vote second, just before the disengaged voters.",[11,415,416],{},[14,417],{"alt":410,"height":397,"loading":31,"src":418,"width":399,"decoding":33},"\u002Fblog\u002Fsheepherding-story-points\u002Fimg5.png",[11,420,421],{},[37,422,410],{},[64,424,426],{"id":425},"the-disengaged-voter","The disengaged voter",[11,428,429],{},"They are hard to pin down during implementation, but their behavior is obvious during voting. They always vote last and copy someone else's estimate. If the estimates differ, they pick the most common one. They do not want to explain why they chose a lower or higher number, so they avoid collaborating in refinement and dodge questions.",[11,431,432],{},[14,433],{"alt":426,"height":434,"loading":31,"src":435,"width":436,"decoding":33},353,"\u002Fblog\u002Fsheepherding-story-points\u002Fimg4.png",758,[11,438,439],{},[37,440,426],{},[64,442,444],{"id":443},"the-tired-voter","The tired voter",[11,446,447],{},"Some team members cannot stay focused for long and miss key parts of the discussion. They lose context and either guess or hunt for the most common vote to copy.",[11,449,450],{},[14,451],{"alt":444,"height":397,"loading":31,"src":452,"width":399,"decoding":33},"\u002Fblog\u002Fsheepherding-story-points\u002Fimg6.png",[11,454,455],{},[37,456,444],{},[40,458,460],{"id":459},"how-to-keep-the-attention-during-estimation","How to keep the attention during estimation",[11,462,463,464,468,469,471],{},"Estimation matters because only honest story points can ",[48,465,467],{"href":466},"\u002Fblog\u002Fcorrectly-estimating-release-deadline","keep a project on track to its release date",". The key to honest estimation is to counter the ",[268,470,369],{},", whether you use paper cards or software.",[11,473,474],{},"Team members should never see each other's estimates until the moderator reveals them. This way the quiet voter starts thinking, the disengaged voter gets interested and the tired voter wakes up. The best question to ask, especially when someone disagrees with the group, is \"why did you vote X story points?\" That starts a conversation about the real implementation issues. Closed questions such as \"would you agree with X story points?\" invite a meaningless \"yes\".",[11,476,477],{},"A good estimation tool makes refinement more engaging and keeps everyone alert and ready to discuss, so even complex stories get better estimates.",{"title":158,"searchDepth":159,"depth":159,"links":479},[480,486],{"id":362,"depth":159,"text":363,"children":481},[482,483,484,485],{"id":385,"depth":165,"text":386},{"id":409,"depth":165,"text":410},{"id":425,"depth":165,"text":426},{"id":443,"depth":165,"text":444},{"id":459,"depth":159,"text":460},"2018-04-30","Open votes let the first estimate anchor the room. See how the sheep effect skews story points and how to run planning poker honestly.","Sheepherding story points","\u002Fblog\u002Fsheepherding-story-points\u002Fcoffee-table-sheep.jpg",[492,493,494,369,495],"story points","planning poker","anchoring bias","agile estimation",{},"\u002Fblog\u002Fen\u002Fsheepherding-story-points",{"title":348,"description":488},{"loc":497,"images":500,"lastmod":178},[501,502,503,504,505,506],{"loc":356},{"loc":377},{"loc":398},{"loc":418},{"loc":435},{"loc":452},"sheepherding-story-points","blog\u002Fen\u002Fsheepherding-story-points","m0FgZBGi6-ktByr0j85XgV8pgG-BtNxA3Fip11a4DC8",{"id":511,"title":512,"author":6,"body":513,"dateModified":178,"datePublished":586,"description":587,"extension":181,"heading":588,"image":589,"imageAlt":519,"keywords":590,"locale":190,"meta":595,"navigation":192,"path":596,"reviewed":192,"seo":597,"sitemap":598,"slug":603,"stem":604,"translationKey":603,"__hash__":605},"blog\u002Fblog\u002Fen\u002Fthe-10-percent-scrumban-rule-for-every-sprint.md","The 10% Scrumban rule for every sprint | AELBOX",{"type":8,"value":514,"toc":581},[515,522,530,534,537,545,549,553,556,560,563,566,574,578],[11,516,517],{},[14,518],{"alt":519,"height":520,"loading":18,"src":521,"width":20,"fetchPriority":21},"Planning poker cards and a Kanban board on a coffee table",959,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fcoffee-table-scrumban.webp",[11,523,524,525,529],{},"Many teams plan to use exactly the capacity shown in their Jira plan. That is often a mistake and leads to failed sprints. Why does it happen when the ",[48,526,528],{"href":527},"\u002Fblog\u002Fthe-importance-of-predictable-velocity","capacity calculations"," look so precise?",[40,531,533],{"id":532},"the-rush-to-deliver-more","The rush to deliver more",[11,535,536],{},"Product Owners tend to push for higher velocity after every successful sprint, a natural reaction to the latest results. If the team completed a certain number of story points last sprint, it is expected to complete more next sprint. This repeats until a sprint fails. The push is an attempt to test the team's limits. In our experience, it is counter-productive. It ultimately demotivates the team, who come to see every future sprint as doomed.",[11,538,539],{},[14,540],{"alt":541,"height":542,"loading":31,"src":543,"width":544,"decoding":33},"The doomed sprint",349,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fimg1.png",400,[11,546,547],{},[37,548,541],{},[40,550,552],{"id":551},"the-hectic-end-of-a-sprint-during-a-delivery-rush","The hectic end of a sprint during a delivery rush",[11,554,555],{},"When capacity is planned to fill the sprint exactly, any delay or realized risk creates pressure to work at a frantic pace at the end. The team then delivers less than promised because stress takes over. That end-of-sprint rush should be eliminated.",[40,557,559],{"id":558},"let-the-team-deliver-more-by-its-own-will","Let the team deliver more by its own will",[11,561,562],{},"Plan only 90% of the team's capacity and reserve the remaining 10% for unplanned backlog work. Those tasks are pulled from the backlog in Scrumban fashion during the sprint. The buffer absorbs risk and lets the team finish the sprint (or at least the sprint goal) a few days early. If an external dependency threatens the sprint, a buffered task can replace the problematic one.",[11,564,565],{},"That 10% is not part of the sprint commitment. If risk does not materialize, the team delivers it as extra work; if something goes wrong, the buffer is consumed but the sprint goal and commitment are still met. Monitor how much of the buffer is used: if it regularly reaches 20%, for example, it is time to raise the team's velocity by 10% while keeping the 10% buffer.",[11,567,568],{},[14,569],{"alt":570,"height":571,"loading":31,"src":572,"width":573,"decoding":33},"Deliver early, deliver extra",320,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fimg3-1.png",296,[11,575,576],{},[37,577,570],{},[11,579,580],{},"Our experience shows that this is when employees work without pressure and contribute the most. Velocity can then increase at the team's own pace, without outside pressure and with less stress. The increase feels natural and sustainable.",{"title":158,"searchDepth":159,"depth":159,"links":582},[583,584,585],{"id":532,"depth":159,"text":533},{"id":551,"depth":159,"text":552},{"id":558,"depth":159,"text":559},"2018-04-28","Committing to full capacity makes every sprint fragile. A 10% Scrumban buffer absorbs risk, protects the sprint goal and lets velocity grow naturally.","The 10% Scrumban rule for every sprint","\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fcoffee-table-scrumban.jpg",[591,592,593,594,333],"scrumban","sprint capacity","agile buffer","velocity",{},"\u002Fblog\u002Fen\u002Fthe-10-percent-scrumban-rule-for-every-sprint",{"title":512,"description":587},{"loc":596,"images":599,"lastmod":178},[600,601,602],{"loc":521},{"loc":543},{"loc":572},"the-10-percent-scrumban-rule-for-every-sprint","blog\u002Fen\u002Fthe-10-percent-scrumban-rule-for-every-sprint","opFsZGR01i-_Ve2m9OgpL6tVmwOz0coJhY_PzMJbUJk",{"id":607,"title":608,"body":609,"dateModified":178,"datePublished":2032,"description":2033,"extension":181,"heading":2034,"image":2035,"imageAlt":2034,"keywords":2036,"locale":190,"meta":2041,"navigation":192,"order":2042,"path":2043,"section":2044,"seo":2045,"sitemap":2046,"slug":2047,"stem":2048,"translationKey":2049,"__hash__":2050},"guide\u002Fguide\u002Fen\u002Fplanning-sessions.md","Planning Sessions | Scrumpy Planning Poker",{"type":8,"value":610,"toc":2004},[611,614,621,625,632,638,712,727,730,734,739,761,778,791,804,808,811,815,842,846,878,893,896,899,914,917,923,927,955,958,962,979,991,995,1005,1011,1014,1018,1025,1031,1037,1057,1072,1075,1078,1082,1092,1194,1221,1224,1227,1231,1246,1249,1274,1277,1283,1300,1304,1307,1331,1334,1338,1341,1362,1368,1388,1391,1394,1397,1418,1432,1435,1438,1501,1509,1512,1515,1530,1543,1550,1553,1558,1561,1578,1584,1591,1594,1597,1600,1625,1628,1631,1634,1645,1648,1651,1661,1681,1699,1705,1716,1734,1737,1756,1759,1762,1765,1777,1783,1787,1802,1817,1831,1835,1852,1856,1859,1894,1898,1905,1908,1916,1923,1943,1953,1956,1960,1967,1970,1976],[11,612,613],{},"Planning sessions group related work items for organized estimation. They help you prepare for sprint planning by collecting work items and tracking estimation progress across perspectives.",[11,615,616,617,620],{},"Planning sessions live on the Space Estimations page. If a space administrator hides that page in space settings, the ",[268,618,619],{},"Add to planning"," action on work items is hidden with it.",[40,622,624],{"id":623},"creating-a-planning-session","Creating a Planning Session",[11,626,627,628,631],{},"From the ",[268,629,630],{},"Refinement\u002Fgrooming"," tab on the Space Estimations page:",[633,634],"docs-figure",{"alt":635,"caption":636,"stem":637},"The Create planning session dialog with the title, description, and schedule","Creating a planning session","guide-planning-create",[639,640,641,648,651,669,696],"ol",{},[642,643,644,645,52],"li",{},"Click ",[268,646,647],{},"Create",[642,649,650],{},"Enter a title, such as \"Sprint 42\". Each title must be unique per space. A title is required: if the field is empty or contains only spaces, it is marked in error and a message tells you that the name of the planning session is required.",[642,652,653,654,657,658,661,662,665,666,668],{},"Optionally add a description and a schedule. The ",[268,655,656],{},"Show timer"," checkbox is checked by default. Clear it to hide the schedule and create the planning session without a timer. While it is checked, choose the ",[268,659,660],{},"Regular"," tab to set a start date and time on the left and a duration of 15, 30, 45, 60, 90, or 120 minutes on the right, all on one line, with the end time shown below the duration. The dialog shows when the session ends, and the end moves to the next day when the duration crosses midnight. Choose the ",[268,663,664],{},"Long lasting"," tab to set a start and an end date and time yourself; the start sits on the left and the end on the right of one line. You can pick a date and type any time; the time list suggests every 15 minutes, and a typed time is always kept. Past dates and times are allowed. The dialog opens with the next half hour and 30 minutes already filled in. Clearing a start date puts today back, clearing an end date puts the day after the start back, and clearing a time puts the next half hour back, so the fields never stay empty. The end must be later than the start. ",[268,667,647],{}," also stays disabled while the title is empty or contains only spaces.",[642,670,671,672,675,676,680,681,684,685,688,689,692,693,695],{},"Optionally add a ",[268,673,674],{},"Video\u002Fscreen share"," link, such as ",[677,678,679],"code",{},"https:\u002F\u002Fmeet.example.com\u002Fsprint-42",". The link must be a full address that starts with ",[677,682,683],{},"http:\u002F\u002F"," or ",[677,686,687],{},"https:\u002F\u002F",". While the field holds a valid link, a video icon appears inside the field; click it to open the link in a new tab. An incomplete address such as ",[677,690,691],{},"meet.example.com\u002Fsprint-42"," is marked in error and ",[268,694,647],{}," stays disabled until you fix it or clear the field.",[642,697,644,698,700,701,704,705,708,709,711],{},[268,699,647],{},". The dialog closes right away and the new planning session appears in the list immediately. If it cannot be saved, it is removed again.\nOnly moderators can create planning sessions. With no sessions yet, moderators see a prompt to create the first one, while non-moderators see an informational message that explains how a space administrator can assign roles from the space settings Permissions tab. Each planning session appears as its own tab, and a newly created session is focused automatically. While a planning session is open, its ",[268,702,703],{},"Edit"," and ",[268,706,707],{},"Delete"," actions sit in the row above the tabs, just before ",[268,710,647],{},". They are not shown while there is no planning session to act on. The planning session tab you last opened is remembered for the current browser tab, so a reload returns you to it. If that planning session no longer exists, the first planning session opens instead.",[11,713,714,715,718,719,722,723,726],{},"The same planning sessions also appear as tabs on the ",[268,716,717],{},"Capacity planning",", ",[268,720,721],{},"Standup",", and ",[268,724,725],{},"Retrospective"," tabs. The planning session you select is shared between those tabs, so switching tab keeps the same session open. See the Sprint standups and Sprint retrospectives guides.",[11,728,729],{},"Planning sessions are kept for three months (90 days) after their last change and are removed automatically after that.",[40,731,733],{"id":732},"editing-and-deleting","Editing and Deleting",[11,735,644,736,738],{},[268,737,703],{}," on a planning session to change its title, description, video link, or date range. Changes appear for everyone viewing the Space Estimations page without a refresh. The dialog closes as soon as you confirm, and the change shows in the list right away. If the change cannot be saved, the previous values come back and a message tells you that the planning session could not be saved.",[11,740,741,742,745,746,748,749,751,752,754,755,757,758,760],{},"The title is required: if you clear it, the field is marked in error, a message tells you that the name of the planning session is required, and ",[268,743,744],{},"Apply"," does not save the change. The schedule has the same two tabs as the create dialog: ",[268,747,660],{}," takes a start and a duration, and ",[268,750,664],{}," takes a start and an end. A session saved with one of the offered durations opens on the ",[268,753,660],{}," tab with that duration selected; any other length opens on the ",[268,756,664],{}," tab. The ",[268,759,656],{}," checkbox controls the schedule: clear it to remove the timer, and a session without a timer opens with it cleared. While it is checked, clearing a start date puts today back, clearing an end date puts the day after the start back, and clearing a time puts the next half hour back, so the fields never stay empty. The end must be later than the start. The time list suggests every 15 minutes, and you can type any time.",[11,762,763,764,766,767,684,769,771,772,774,775,777],{},"The ",[268,765,674],{}," link is optional and has the same rules as on the create dialog: it must be a full ",[677,768,683],{},[677,770,687],{}," address, and a value that is not one is marked in error and keeps ",[268,773,744],{}," disabled. Clear the field to remove the link. When a planning session has a link, every participant header shows a small red video icon just before the role badge: on the planning session side panel, in ",[268,776,717],{},", in alternative voting, and in the work item voting panel. Click the icon to join the video or screen-sharing session in a new tab. The icon appears as soon as the link is saved, without a reload, and disappears when the link is cleared.",[11,779,780,781,783,784,684,787,790],{},"A moderator can also change the description in place. In the ",[268,782,630],{}," tab, click the description above the planning table, type the new text, and click away. There is no ",[268,785,786],{},"OK",[268,788,789],{},"Cancel"," button: the text saves when the field loses focus, appears for everyone right away, and returns to the saved text if the save fails. A session with no description shows a placeholder you can click to add one.",[11,792,793,794,796,797,799,800,52],{},"To remove a planning session, use ",[268,795,707],{}," in the row above the tabs, beside ",[268,798,647],{},". It removes the planning session and all of its items permanently after a confirmation. It also removes its planning-session chat, the work item chat messages and reactions for its items, its ranking records, capacity planning data, standup data, retrospective data, and any linked voting sessions. See ",[48,801,803],{"href":802},"#deleting-a-planning-session","Deleting a Planning Session",[40,805,807],{"id":806},"adding-work-items","Adding Work Items",[11,809,810],{},"You can add work items to a planning session in two ways.",[64,812,814],{"id":813},"from-the-work-item-view","From the Work Item View",[11,816,817,818,821,822,824,825,828,829,832,833,835,836,838,839,841],{},"Open a Jira work item, open the ",[268,819,820],{},"Scrumpy"," panel, and click ",[268,823,619],{},". You can also open the same dialog from the work item's ",[268,826,827],{},"more actions"," (",[268,830,831],{},"...",") menu by choosing ",[268,834,619],{},". Adding a work item to a planning session is a moderator action: voters, guests, and anyone else see a note that only moderators can add work items, instead of the picker. The dialog preselects the planning session you used last on this space; when the space has no planning sessions, ",[268,837,647],{}," is selected instead. Choose another existing session, or choose ",[268,840,647],{}," to create one inline with a title and description; a title is required before the item can be added. A work item can belong to only one planning session in a space. If it is already in the selected session, you are told that it is already there. If it is in another session, you are told which one and it is not added; remove it from that session first. The dialog closes after the item is added. Each planning session you open loads its work items. Switching to another session loads that session once, and returning to one you already opened shows its work items right away.",[64,843,845],{"id":844},"add-from-jira-filter","Add from Jira Filter",[11,847,644,848,851,852,854,855,857,858,860,861,864,865,868,869,871,872,874,875,877],{},[268,849,850],{},"Add from filter"," to import work items from a saved Jira filter, a sprint, a capacity planning session, or a retrospective. The picker starts with a ",[268,853,717],{}," group that lists the planning sessions whose capacity plan has at least one planned work item. Select one to preview every planned work item across that capacity session's sprints. A ",[268,856,725],{}," 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 ",[268,859,725],{}," group is hidden when no action item is linked to a work item. If the space has a Scrum board, the picker then shows an ",[268,862,863],{},"Active sprints"," group that lists the active and future sprints, and a ",[268,866,867],{},"Backlog"," group with one entry per Scrum board. The ",[268,870,863],{}," group appears only when the space has at least one active or future sprint. The ",[268,873,867],{}," group appears whenever the space has a Scrum board, even when no sprint is active or planned; Kanban spaces show neither group. Select a sprint to preview its work items, or select a Scrum board under ",[268,876,867],{}," to preview that board's work items that are not in any sprint. Only work items from this space are listed.",[11,879,880,881,884,885,888,889,892],{},"Below the backlog, the picker lists the space's Kanban boards under ",[268,882,883],{},"Boards","; pick one to preview the work items on that board. Scrum boards are not listed there, because the sprint and backlog entries already cover them. Then come favourited filters under ",[268,886,887],{},"Favorite",", your own filters under ",[268,890,891],{},"My filters",", and shared filters under their owner's name; favourited filters show a star. Type in the picker to search Jira by any part of a filter name. The same text also narrows the sprint, backlog, and board lists and every filter group. Scrumpy asks Jira for the first 100 shared filters that match. When more shared filters match than that, the dialog says it shows the first ones, and typing more of the name narrows the list. To start over, clear the picker: the chosen filter is dropped, the search box empties, and the first 100 shared filters return. Select a filter to preview its work items, tick the ones you want, and add them. A work item that already belongs to a planning session is marked with that session's title and cannot be added again, even when that session is not open in another tab. You can create filters on the Jira filters page. A planning session can only hold work items from its own space, so any work item from another space cannot be added; the preview lists only this space's work items and says so below the table. You can also add only work items you can open in Jira: a work item hidden from you stays out of the session, even if you know its key.",[11,894,895],{},"Only work items you can open in Jira can be added. If a work item is hidden from you by Jira issue-level security, Scrumpy rejects the add, and that work item is omitted from the planning table for you.",[11,897,898],{},"In the preview you can:",[900,901,902,905,908,911],"ul",{},[642,903,904],{},"Tick individual work items, or use the header checkbox to select all selectable ones on the page you are looking at.",[642,906,907],{},"Page through long results below the table. The preview shows 100 work items per page, and your ticks stay when you change page.",[642,909,910],{},"Reorder rows by dragging them. The ticked items are added in the order the preview shows, across every page.",[642,912,913],{},"See Type, Work item, Status, and Summary columns. The Type column shows the icon of the work item's type, including newer and custom types. The Type and Work item column headers and all their cells are center aligned. A warning-colored status icon in the Status column marks work items that cannot be added. Hover the icon to see why: it is not from this space, it is already in this planning session, or it is already in another planning session in the space, and the tooltip names that session.",[11,915,916],{},"The preview loads at most 500 work items. When a filter matches more, the dialog says it shows the first 500.",[11,918,919,922],{},[268,920,921],{},"Add"," stays disabled until you select at least one work item.",[40,924,926],{"id":925},"managing-items","Managing Items",[900,928,929,935,941],{},[642,930,931,934],{},[268,932,933],{},"Drag and drop",": Reorder items by dragging rows (moderators only). Everyone sees the new order right away, without a reload, and the perspective rows stay below the work items.",[642,936,937,940],{},[268,938,939],{},"Select",": Tick the checkboxes to select items for bulk actions.",[642,942,943,946,947,950,951,954],{},[268,944,945],{},"Highlight",": Use the radio button to select a work item for estimation. It loads into the Voting Panel on the right, so you can estimate directly from the planning table. When no work item is selected, the right panel shows a planning session side panel with a ",[268,948,949],{},"Details"," tab for the no-selection message and a ",[268,952,953],{},"Chat"," tab for the planning session chat.",[11,956,957],{},"The Type and Work item columns in the planning table are center aligned. The affinity and dot ranking columns, when they appear, are center aligned as well.",[64,959,961],{"id":960},"edit-mode","Edit mode",[11,963,763,964,966,967,970,971,974,975,978],{},[268,965,961],{}," dropdown to the right of the session description chooses how voting is driven: ",[268,968,969],{},"Single voting"," (the default) or ",[268,972,973],{},"Bulk voting",". A moderator changes the shared mode, and it appears for everyone right away, so every participant follows the same mode. A voter can also change the mode. That change applies only to that voter, unchecks ",[268,976,977],{},"Lock to moderator",", and is remembered for the current browser tab. Checking the lock again returns the dropdown to the moderator's current mode. The moderator's mode is saved with the planning session. A voter's local mode is not shared and does not change what the moderator sees.",[11,980,981,982,984,985,987,988,52],{},"To the right of the ",[268,983,961],{}," dropdown, the app switcher button opens ",[268,986,717],{}," on the same planning session tab. Its tooltip says ",[268,989,990],{},"Switch to capacity planning",[64,992,994],{"id":993},"visible-perspectives","Visible perspectives",[11,996,997,998,1000,1001,1004],{},"The perspectives dropdown sits just before the ",[268,999,961],{}," dropdown. It chooses which perspectives the planning table shows, as a column and as a row in bulk voting, and which perspective tabs appear in the voting panel on the right. It appears only when the space has more than one perspective. When the dropdown is empty it shows ",[268,1002,1003],{},"All perspectives",", which is also the default for every planning session.",[11,1006,1007,1008,1010],{},"A moderator changes the list for everyone, and it updates without a reload. A voter can narrow the list for themselves. That change unchecks ",[268,1009,977],{}," and stays in the current browser tab. Checking the lock again returns the moderator's list. A guest always follows the moderator's list.",[11,1012,1013],{},"Only the perspectives in the list are offered for the bulk Start, Pause, Resume, Complete, Restart, Cancel, and Accept actions. If the moderator hides the perspective that is currently open in the right panel, the panel returns to the highlighted work item. A perspective you add later appears automatically until someone narrows the list.",[64,1015,1017],{"id":1016},"who-is-highlighted","Who is highlighted",[11,1019,1020,1021,1024],{},"Moderators pick the highlighted work item for everyone, and the selected row shows a yellow ",[268,1022,1023],{},"M"," with the tooltip \"Work item currently selected by the moderator\".",[11,1026,1027,1028,1030],{},"In bulk mode a moderator can instead select a perspective row, which opens alternative voting for it. That selection is also shared, and it replaces any selected work item. Other participants see the same yellow ",[268,1029,1023],{}," in the first column of that perspective row, with the tooltip \"Perspective currently selected by the moderator\".",[11,1032,1033,1034,1036],{},"The selected perspective is also the perspective tab of the inline voting panel, so highlighting a work item opens that tab. Participants who are locked to the moderator follow the moderator's tab, and a yellow ",[268,1035,1023],{}," badge marks it, even when it matches the tab they are on. The badge stays visible when you clear the lock, so you can always see where the moderator is. It is shown only while the moderator's selected work item is the one being shown; it is hidden when an unlocked participant focuses a different work item.",[11,1038,763,1039,1041,1042,1044,1045,1047,1048,1050,1051,1053,1054,1056],{},[268,1040,1023],{}," is also your pointer to the moderator's view. While you follow the moderator, your highlighted row and the ",[268,1043,1023],{}," row are the same. When you pick a row yourself, your highlight moves to that row and the ",[268,1046,1023],{}," stays on the moderator's row, so you can see how far you have drifted. The same holds for the inline panel: the ",[268,1049,1023],{}," stays on the moderator's tab after you open another one. Following the moderator also means that the moderator switches tabs for you: while ",[268,1052,977],{}," is on, every work item and tab the moderator opens opens for you too. Detaching is one click: pick another row, tab, or edit mode, or clear ",[268,1055,977],{}," yourself.",[11,1058,1059,1060,1062,1063,718,1065,718,1067,722,1069,1071],{},"By default, other participants follow the moderator's work item selection, edit mode, and alternative-voting tab. A ",[268,1061,977],{}," checkbox (on by default) controls this. It applies to the planning tab you are on: ",[268,1064,630],{},[268,1066,717],{},[268,1068,721],{},[268,1070,725],{},". It also controls the space page tab: when the moderator switches between those tabs, a locked participant viewing the same planning session moves to the same tab and stays locked. When you switch between those tabs yourself, the checkbox clears, so you start detached on the new tab. Switching to Getting started, Tutorials, or Dashboard and back does not clear it.",[11,1073,1074],{},"If you pick a row, switch the edit mode, or open another alternative-voting tab yourself, the lock turns off. 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. Clearing the lock keeps the right panel on the tab you were following; it does not jump back to a tab you opened earlier. Your local choices survive a reload but are not shared with anyone else and do not change what the moderator sees.",[11,1076,1077],{},"Turn the lock back on to follow the moderator again; the edit mode dropdown and the alternative-voting tab then return to the moderator's current choices.",[64,1079,1081],{"id":1080},"bulk-actions","Bulk actions",[11,1083,1084,1085,1088,1089,1091],{},"Below the table, a ",[268,1086,1087],{},"Perspective"," select (disabled until you tick at least one work item) chooses which perspective the session actions apply to, followed by icon-only actions. The open list starts with a ",[268,1090,1087],{}," heading that you cannot choose. Each action has a tooltip stating that it applies to the selected work items. The chosen perspective and the ticked work items are remembered for the current browser tab, so a reload restores them.",[1093,1094,1095,1108],"table",{},[1096,1097,1098],"thead",{},[1099,1100,1101,1105],"tr",{},[1102,1103,1104],"th",{},"Action",[1102,1106,1107],{},"What it does",[1109,1110,1111,1122,1132,1142,1155,1165,1174,1184],"tbody",{},[1099,1112,1113,1119],{},[1114,1115,1116],"td",{},[268,1117,1118],{},"Start",[1114,1120,1121],{},"Opens voting sessions for the ticked items in the chosen perspective",[1099,1123,1124,1129],{},[1114,1125,1126],{},[268,1127,1128],{},"Pause",[1114,1130,1131],{},"Pauses their started sessions. Sessions that are already paused are skipped, and perspectives with asynchronous voting are skipped because their sessions cannot be paused",[1099,1133,1134,1139],{},[1114,1135,1136],{},[268,1137,1138],{},"Resume",[1114,1140,1141],{},"Resumes their paused sessions. Perspectives with asynchronous voting are skipped because their sessions cannot be resumed",[1099,1143,1144,1149],{},[1114,1145,1146],{},[268,1147,1148],{},"Complete",[1114,1150,1151,1152,1154],{},"Completes their started sessions. A session with no votes (no real estimate) is cancelled instead, matching the voting panel's ",[268,1153,1148],{}," button. Votes made only with the extra emoji cards count as no votes",[1099,1156,1157,1162],{},[1114,1158,1159],{},[268,1160,1161],{},"Restart",[1114,1163,1164],{},"Restarts their completed sessions in place. The new round starts right away with the configured required voters, and the completed result and its votes are discarded. The work item keeps its place in the perspective's rankings",[1099,1166,1167,1171],{},[1114,1168,1169],{},[268,1170,789],{},[1114,1172,1173],{},"Cancels their voting sessions, including completed ones",[1099,1175,1176,1181],{},[1114,1177,1178],{},[268,1179,1180],{},"Accept",[1114,1182,1183],{},"Accepts their completed sessions and writes the estimates to Jira. The estimate appears in the perspective column right away. If the Jira write fails, the session and the column return to their previous state and an error dialog explains why",[1099,1185,1186,1191],{},[1114,1187,1188],{},[268,1189,1190],{},"Remove",[1114,1192,1193],{},"Removes the ticked items from the planning session",[11,1195,1196,1197,1199,1200,1202,1203,1205,1206,1208,1209,1211,1212,1214,1215,1217,1218,1220],{},"An action is disabled when no ticked work item applies: ",[268,1198,1118],{}," when every session has already started, ",[268,1201,1128],{}," when there is no active session or the perspective uses asynchronous voting, ",[268,1204,1138],{}," when there is no paused session or the perspective uses asynchronous voting, ",[268,1207,1148],{}," when there is no started session, ",[268,1210,1161],{}," when there is no completed session, ",[268,1213,789],{}," when no ticked item has a session, ",[268,1216,1180],{}," when there is no completed session, and ",[268,1219,1190],{}," until something is ticked. Removing the highlighted item clears the highlight.",[11,1222,1223],{},"Each action takes effect in the table immediately. The rows are added, paused, resumed, completed, restarted, or removed right away, and the buttons enable or disable from those updated rows, so the same action cannot run twice. There is no spinner. The inline voting panel on the right changes in the same moment, and a vote or session action made in the panel updates the table row at the same moment too. You never need to wait for a refresh to see the other side catch up. If the change cannot be saved, both the table and the panel return to the previous state.",[11,1225,1226],{},"After a drag or a bulk removal, the table updates right away. The change is confirmed in the background, and if the write fails the previous order returns.",[40,1228,1230],{"id":1229},"bulk-voting","Bulk Voting",[11,1232,1233,1234,1236,1237,1239,1240,1242,1243,1245],{},"Anyone can switch the ",[268,1235,961],{}," from ",[268,1238,969],{}," to ",[268,1241,973],{},". A moderator changes the shared mode, and a voter switches locally. In bulk mode, the planning table keeps all of its rows and buttons, and its perspective cells become voting controls, so the description, the ",[268,1244,961],{}," dropdown, the buttons, the progress bar, and the estimation panel all stay in place.",[11,1247,1248],{},"A perspective cell shows a voting control only when that work item has a started session in that perspective:",[900,1250,1251,1258,1261],{},[642,1252,1253,1254,1257],{},"A clearable dropdown of the deck's cards (for example \"2 sp\" or \"XXL\"), with the extra cards grouped under an ",[268,1255,1256],{},"Extra cards"," heading, preselected with your current vote.",[642,1259,1260],{},"A number field bounded by the perspective's minimum and maximum for free scale perspectives. The field always shows an \"sp\" suffix after the number. When the perspective converts story points to a duration, it also shows a short duration such as \"1d 4h\" beside the suffix. Clearing the field removes the vote, restores the work item's original estimate as the field value, and marks the field as needing a vote. The clear control is always visible and is disabled until the field has a value.",[642,1262,1263,1264,1267,1268,1270,1271,1273],{},"A parametric result in a read-only numeric field with an \"sp\" suffix, a compact withdraw control, and one compact edit vote control inside the suffix area. When you have not voted yet, the field shows the work item's current estimate when it is numeric and is marked as needing a vote. Opening the edit control calculates the current result and shows it in the field straight away, using the perspective formula and the parameter values in the popup. The popup has one compact number field per parameter, labelled with the parameter name and bounded by its minimum and maximum, and a centered primary ",[268,1265,1266],{},"Vote"," button below the parameters. Changing a parameter updates the value in the field immediately. The edit control is hidden while the popup is open and comes back when it closes. ",[268,1269,1266],{}," closes the popup and casts the result. Clicking outside the popup closes it without saving and restores the previous vote, or returns to the empty error field when there was no vote. When a vote already exists and you have not changed a parameter, ",[268,1272,1266],{}," stays disabled. Press the withdraw control to remove the current parametric vote immediately. The field shows the work item's original estimate again and is marked as needing a vote, and the withdraw control and the \"sp\" suffix stay visible while the withdraw control is disabled. The converted duration and the wider field appear only when the estimation target writes a time value: a time board or a Time field. The numeric fields have a fixed width for each combination of story points and duration, so the columns line up and a field does not change size while you type. A numeric board or a story points field shows story points only, and the perspective settings explain that the duration is not written. Scrumpy remembers the last parameter values you used for the current voting session and puts them back when you reopen the editor. It also opens on the parameter positions recorded with your vote, even when you cast it in the voting panel, so both places always show the same positions. A new voting session starts again from each slider's midpoint. The positions you have not voted with yet are kept only in your browser for the open page, not saved with the vote.",[11,1275,1276],{},"When the session is active and not paused, a compact pause control sits beside the voting control and uses the same height. Pressing it pauses that work item's voting session and hides the control immediately. If the pause fails, the control returns. The pause control is not shown for a paused session or for asynchronous voting.",[11,1278,1279,1280,1282],{},"Changing a control casts your vote for that work item and perspective. The value appears right away and stays in place while it is saved, including when closed voting is on. If the save fails, the control returns to your previous vote. In a free scale field, type the number and then click away to save it. Clearing the dropdown (or emptying the number field) removes your vote, exactly like clicking the same voting card again. Parametric is different: opening the editor shows the calculated result in the cell, editing the fields only updates that preview, and the ",[268,1281,1266],{}," button in the popup casts the result. When a session completes or is cancelled, its voting control disappears and the cell returns to its usual state or estimate.",[11,1284,1285,1286,1288,1289,1291,1292,1295,1296,1299],{},"Until you vote in a cell, the control shows the work item's current estimate as a placeholder, or ",[268,1287,1266],{}," when there is none, and the control is marked as needing a vote. Choosing a value clears that hint. Free-scale and parametric cells show the original numeric estimate in the field until you vote. In a parametric cell, opening the editor replaces that estimate with the calculated result, even before your first vote, and closing without pressing ",[268,1290,1266],{}," restores the previous vote or the original estimate and its red error state. When the current estimate is stored as a time value (a time board or a Time field), the bulk editor converts it back to story points with the ",[268,1293,1294],{},"Story points to hours"," factor, so a 20-hour estimate appears as ",[268,1297,1298],{},"2.5"," in a field that edits story points; the parametric editor also keeps the 20-hour duration beside the value.",[64,1301,1303],{"id":1302},"perspective-rows-and-ranking-columns","Perspective rows and ranking columns",[11,1305,1306],{},"In bulk mode the table also lists one selectable row per perspective below the work items. Free scale perspectives show the Affinity, Dot, and Bucket tabs: the Bucket tab lists the work items from the smallest to the largest estimate with a gap row between different estimates, because there are no cards to drop work items under. Parametric perspectives show the Affinity, Dot, and Bucket tabs too: their Bucket tab lists the same estimates, but a vote is edited through its sliders instead of a field. Each row has a checkbox, a radio to select it for alternative voting, and the perspective name. These rows always stay at the bottom: they cannot be dragged, and a work item cannot be dropped on or below them.",[11,1308,1309,1310,1313,1314,1317,1318,704,1320,1322,1323,1326,1327,1330],{},"While a perspective has rankings, its row shows a regular ",[268,1311,1312],{},"Affinity"," badge and a regular ",[268,1315,1316],{},"Dot"," badge for everyone, one for each ranking the perspective has. A perspective with no rankings shows no badges. Rankings are cleared from the ",[268,1319,1312],{},[268,1321,1316],{}," panels: the affinity ",[268,1324,1325],{},"Clear rankings"," delete icon clears affinity only, and the dot one clears dots only. If the cleared ranking was the enforced ranking for the bucket table, the bucket ranking mode also returns to ",[268,1328,1329],{},"No ranking",". The rankings disappear right away; if the clear cannot be saved, they come back.",[11,1332,1333],{},"A perspective that has affinity rankings is followed by an affinity ranking column, and one that has dot rankings by a dot ranking column, each shown when that ranking exists. Each work item's value is a badge: its affinity position, or its dot count (0 when it has no dots). The ranking column headers and badges are center aligned.",[40,1335,1337],{"id":1336},"alternative-voting","Alternative Voting",[11,1339,1340],{},"Selecting a perspective row opens alternative voting for that perspective in place of the work item voting panel. A perspective row and a work item row cannot both be selected: selecting a perspective row clears the selected work item.",[11,1342,1343,1344,684,1346,1349,1350,1352,1353,718,1355,1357,1358,1361],{},"The perspective you last opened in alternative voting and the ",[268,1345,1266],{},[268,1347,1348],{},"Results"," sub-tab are remembered for the current browser tab. While ",[268,1351,977],{}," is on, the outer tab (",[268,1354,1312],{},[268,1356,1316],{},", or ",[268,1359,1360],{},"Bucket",") follows the moderator's current tab. The moderator's tab is saved with the planning session and appears for everyone right away.",[11,1363,1364,1365,1367],{},"A yellow ",[268,1366,1023],{}," badge marks the tab the moderator is viewing while the moderator has the same perspective open, even when it is the same tab you are on. It is hidden when the moderator has selected a work item or another perspective. If you click another tab, the lock turns off. Clicking the moderator's tab again does not change the lock. Checking the lock returns you to the moderator's tab.",[11,1369,1370,1371,718,1373,722,1375,1377,1378,1381,1382,1384,1385,1387],{},"The panel has three tabs: ",[268,1372,1312],{},[268,1374,1316],{},[268,1376,1360],{},". Each tab shows the perspective title in bold, its description, and the settings gear link above its table. All three tabs list the work items that apply to the perspective and have an active, paused, or completed voting session. A work item leaves the panels when its session is cancelled or accepted. Every table has a lock column after the ",[268,1379,1380],{},"Work item"," column. Its header shows the locked padlock. A fully locked panel shows the lock icon on every work item. A single work item that cannot be moved, such as a completed session in a bucket table, shows the locked padlock icon. To the right of the ",[268,1383,1360],{}," tab, the panel shows a ",[268,1386,953],{}," tab, then the same role badge and sound bell as the voting panel: the badge links to the Permissions settings, the bell toggles sound notifications, and the Chat tab shows the planning session chat.",[11,1389,1390],{},"In every tab, hovering a work item key shows its Jira summary, the same tooltip the planning table uses. The summaries come from the ones the planning table already loaded, so switching tabs does not read Jira again. If a summary is not available, the key shows without a tooltip.",[11,1392,1393],{},"Cancelling or accepting a work item's voting session removes it from both rankings for that perspective and from the Affinity, Dot, and Bucket panels. Starting a new session for the item adds it back unranked, at the end of the affinity order and without a dot.",[64,1395,1312],{"id":1396},"affinity",[11,1398,1399,1400,704,1402,1404,1405,1407,1408,1410,1411,1413,1414,1417],{},"Affinity ranks the work items. It has two sub-tabs, ",[268,1401,1266],{},[268,1403,1348],{},": ",[268,1406,1266],{}," holds the table and all the controls, and ",[268,1409,1348],{}," shows a bar chart of the ranking. Every participant sees ",[268,1412,1348],{},", whether or not ",[268,1415,1416],{},"Open voting"," is on.",[11,1419,1420,1421,1424,1425,1428,1429,1431],{},"To the right of the perspective title, a moderator sets the ranking algorithm: ",[268,1422,1423],{},"Mean rank"," (averages the participants' rankings) or ",[268,1426,1427],{},"Median rank"," (uses the middle of their positions). Only a moderator can change it, and the choice is shared live. If the change is refused, the selector returns to the last saved algorithm. If the enforced ranking is ",[268,1430,1312],{}," and the bucket panel has a vote or a completed session, the affinity table is locked: you cannot rerank, withdraw, or change the algorithm, and the lock column shows the lock icon on every work item. The other ranking stays editable.",[11,1433,1434],{},"On the Vote tab, only voters can drag, and the table is read-only for everyone else. Drag a row to change its position. A short hint above the table reminds voters to drag work items; it disappears for you as soon as you move a row, without waiting for the save. The affinity rank column in the planning table follows your move at once, so the ranks there never lag behind the table you are dragging.",[11,1436,1437],{},"The table shows these columns:",[1093,1439,1440,1450],{},[1096,1441,1442],{},[1099,1443,1444,1447],{},[1102,1445,1446],{},"Column",[1102,1448,1449],{},"Meaning",[1109,1451,1452,1462,1471,1481,1491],{},[1099,1453,1454,1459],{},[1114,1455,1456],{},[268,1457,1458],{},"Type",[1114,1460,1461],{},"The icon of the work item's type, including newer and custom types",[1099,1463,1464,1468],{},[1114,1465,1466],{},[268,1467,1380],{},[1114,1469,1470],{},"Issue key",[1099,1472,1473,1478],{},[1114,1474,1475],{},[268,1476,1477],{},"My rank",[1114,1479,1480],{},"Your own position (1 for the top row), shown in a plain badge",[1099,1482,1483,1488],{},[1114,1484,1485],{},[268,1486,1487],{},"Deviation",[1114,1489,1490],{},"The gap between your rank and the group rank (your rank minus the group rank), shown as a signed number. It is a plain badge below 1, yellow below 2, and red otherwise",[1099,1492,1493,1498],{},[1114,1494,1495],{},[268,1496,1497],{},"Rank",[1114,1499,1500],{},"The work item's shared position (1 is best), computed with the selected algorithm. The header and cells are right aligned",[11,1502,1503,1504,704,1506,1508],{},"Until you submit a ranking, the ",[268,1505,1477],{},[268,1507,1487],{}," cells stay empty. They fill in when you rank, and clear again when you withdraw.",[11,1510,1511],{},"The Type, Work item, My rank, and Deviation column headers and all their cells are center aligned. Every displayed work item takes part, even when no one has rearranged it.",[11,1513,1514],{},"Your ranking is saved as you drag and shared live, so the other participants see the new order. Your own order is remembered per planning session and perspective, so a reload restores it, and it also follows you into your other open windows.",[11,1516,1517,1518,1521,1522,1524,1525,1527,1528,52],{},"Below the table you see the participants who have submitted a ranking. The participants group updates right away as you rank or withdraw, without waiting for the server. A voter can withdraw their own ranking with ",[268,1519,1520],{},"Withdraw",", which returns the table to the work item order and removes their ranking from the consensus right away. A moderator can clear all affinity rankings with the ",[268,1523,1325],{}," delete icon, shown to moderators and disabled until rankings exist. The participant row appears once someone has ranked, while the ",[268,1526,1325],{}," icon stays visible and becomes enabled. The tooltip on the icon explains that it deletes the rankings for all users. If affinity was the enforced ranking, clearing it also returns the bucket ranking mode to ",[268,1529,1329],{},[11,1531,1532,1533,1536,1537,1539,1540,1542],{},"A moderator can also send the shared ranking to Jira. The ",[268,1534,1535],{},"Sync to Jira"," transition icon sits after ",[268,1538,1520],{}," and before ",[268,1541,1325],{},", and only a moderator sees it.",[900,1544,1545],{},[642,1546,1547,1549],{},[268,1548,1535],{}," ranks the listed work items in Jira in their shared rank order. 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. The work item ranked 1 stays where it is in Jira, and the other listed work items follow it in rank order, so the listed work items form one ranked block while other work in the space keeps its place.",[11,1551,1552],{},"The icon shows a spinner while it runs. Hover the icon to see a note that pressing it synchronizes the affinity ranking with the Jira rank. If Jira refuses the change, an error appears below the controls and you can try again. Jira must allow you to rank work items for this to work.",[11,1554,763,1555,1557],{},[268,1556,1348],{}," tab shows a horizontal bar chart of each work item's position, best at the top. It is read-only.",[64,1559,1316],{"id":1560},"dot",[11,1562,1563,1564,704,1566,1404,1568,1570,1571,1573,1574,1413,1576,1417],{},"Dot ranks the work items by dots. It has two sub-tabs, ",[268,1565,1266],{},[268,1567,1348],{},[268,1569,1266],{}," holds the table and the controls, and ",[268,1572,1348],{}," shows a horizontal bar chart of each work item's total dots, lowest at the top, with no controls. Every participant sees ",[268,1575,1348],{},[268,1577,1416],{},[11,1579,1580,1581,1583],{},"A moderator sets the dot budget below the table. A per-participant budget is between 1 and the number of work items, because each participant can dot a work item once. A shared budget has no upper limit: it can be any number at least the dots already placed. If the enforced ranking is ",[268,1582,1316],{}," and the bucket panel has a vote or a completed session, the dot table is locked: you cannot place or remove dots or withdraw, and the lock column shows the lock icon on every work item. The other ranking stays editable.",[11,1585,1586,1587,1590],{},"Tick ",[268,1588,1589],{},"Share this budget between participants"," to make it one shared pool given first come, first served. The budget is not shared by default, so each participant gets the full budget. Everyone sees the same budget; non-moderators see only how many dots remain.",[11,1592,1593],{},"Your own budget change appears at once; if the server refuses it, the number field and the sharing checkbox return to the last saved values. If you change the number quickly, the field keeps your latest value instead of flickering back to an earlier one. A late update never replaces a newer budget, and a budget change and a ranking change do not overwrite each other. If you switch to a shared budget that is lower than the dots already given, all dot rankings are reset and a dismissable message tells you why.",[11,1595,1596],{},"Each work item can hold at most one dot per participant. Clicking an unvoted row's dot spends one of your dots, and clicking a dotted row gives it back.",[11,1598,1599],{},"The table shows Type, Work item, Dot, and Rank columns. No column is sortable and the rows cannot be dragged. The Type, Work item, and Dot column headers and cells are center aligned, and the Dot header shows the medium stroke-weight dot icon instead of the word. The Rank header and cells are right aligned. The Type, Work item, and Rank columns use the planning table's minimum widths:",[900,1601,1602,1607,1612,1617],{},[642,1603,1604,1606],{},[268,1605,1316],{}," holds a small button with a dot icon. Click it to place your dot, click again to remove it, returning the dot to the budget. It is disabled once your budget is empty and the work item has no dot.",[642,1608,1609,1611],{},[268,1610,1497],{}," is the total number of dots the work item holds across all participants.",[642,1613,1614,1616],{},[268,1615,1520],{}," clears your dots and returns your whole budget.",[642,1618,1619,1621,1622,1624],{},[268,1620,1535],{}," transition icon, beside ",[268,1623,1520],{},", is available to every participant, including non-moderators, and stays enabled whenever at least one work item is listed. It adds your Jira vote to every work item you have dotted in this panel and removes your Jira vote from every work item you have not dotted. The button shows a spinner while it runs. Hover the button to see a note that pressing it synchronizes your dot votes with your Jira votes. If Jira rejects a vote, an error appears below the controls and you can try again. Jira must allow users to vote on issues for this to work.",[11,1626,1627],{},"A short hint above the table reminds voters to place dots; it disappears for you as soon as you place your first dot, without waiting for the save. The dot rank column in the planning table follows each dot at once, so the counts there never lag behind the dots you place. If the shared pool is already used up by other participants when your dot reaches the server, the dot is not kept: it disappears from the table, your dots return to the last saved selection, and a dismissable informational message saying the shared dot budget is exhausted replaces the hint.",[11,1629,1630],{},"The number field cannot be set below the dots already given: its minimum is the dots the participant with the most dots has given, or the whole placed pool when the budget is shared. Switching to a shared budget below the placed dots resets all dot rankings instead.",[11,1632,1633],{},"The dots left are shown in a badge colored by how many remain: grey above half, yellow above a quarter, and red otherwise.",[11,1635,1636,1637,1639,1640,1642,1643,1330],{},"A moderator can clear all dot rankings with the ",[268,1638,1325],{}," delete icon beside ",[268,1641,1520],{},", shown to moderators and disabled while no dot rankings are visible. The tooltip on the icon explains that it deletes the rankings for all users. The icon follows your local dots immediately: it is enabled as soon as you place a dot and disabled again when the last dot is removed, before the save reaches the server. If dot was the enforced ranking, clearing the dot rankings, including the reset when switching to a shared budget, also returns the bucket ranking mode to ",[268,1644,1329],{},[11,1646,1647],{},"The participants who have dotted a work item are shown below the table, and that row keeps its place before anyone has dotted, so the budget controls and description do not move when the first dot appears. The group updates right away as you dot or withdraw, without waiting for the server.",[64,1649,1360],{"id":1650},"bucket",[11,1652,1653,1654,1657,1658,1660],{},"Bucket groups the work items under the cards as buckets. Only the perspective's enabled cards are shown: the active cards of its sequence plus the enabled extra cards. A ",[268,1655,1656],{},"No estimate"," row at the top holds the work items you have not voted on in this session. A short hint above the table in the ",[268,1659,1266],{}," tab reminds voters to drag a work item under a card; it disappears for you after your first drop.",[11,1662,1663,1664,704,1666,1668,1669,1671,1672,1674,1675,1677,1678,1680],{},"The Bucket panel has two tabs below the perspective description: ",[268,1665,1266],{},[268,1667,1348],{},". ",[268,1670,1266],{}," holds the table and its hint. ",[268,1673,1348],{}," shows a vote heat map, and every participant sees the tab whether ",[268,1676,1416],{}," is on or off. The voters group, the ",[268,1679,1520],{}," button, and the description stay below the tabs, so they do not move when you switch tabs.",[11,1682,1683,1684,1686,1687,1689,1690,1692,1693,1695,1696,1698],{},"A completed session keeps your recorded vote in the table, so its work item stays under its card until the session is cancelled or accepted. When the perspective has an enforced ranking and at least one voting session in the bucket panel is completed, bucket voting is locked: you cannot drag work items or use ",[268,1685,1520],{},", and the ranking selector allows only ",[268,1688,1329],{},". A message explains the lock. A completed session also cannot be moved or re-estimated when the bucket panel is not fully locked. Cancel or accept completed sessions to unlock them. A work item you have voted on in this session starts under the card matching your vote; a vote stored before the session does not affect where it starts. When your vote arrives, the work item moves under its card without dragging, and removing your vote returns it to No estimate. Drag a work item under a card row to vote for that card, and drop it under ",[268,1691,1656],{}," to clear the vote. The move appears right away and is saved in the background. If the save fails, the work item returns to the card it was under before the drop. A voter can withdraw all of their votes for the items in this panel with ",[268,1694,1520],{}," below the voters group. The items return to ",[268,1697,1656],{}," right away, and the button is disabled once the voter has no votes left in the panel.",[11,1700,1701,1702,1704],{},"Each card row shows the card image at 32 pixels high in the Type column, its label in bold in the Work item column (story points with the \" sp\" suffix, T-Shirt sizes with their size), and the card name in regular text left aligned in the Participants column (the configured title, or the built-in playful title such as \"Low hanging fruit\" for 1 sp). The Type and Work item column headers and every cell in those columns are center aligned. When the perspective writes a time value, the card label has a small centered duration below it. A T-shirt card also shows its mapped story points there, for example \"3 sp · 2 days\"; it shows only the units the perspective writes. When neither is written, no small text appears. The ",[268,1703,1656],{}," row shows the backlog icon in the Type column, center aligned, and has no text label. Card and No estimate rows are highlighted and cannot be dragged. The Participants column also shows each work item's vote progress, for example \"33% or 1 out of 3 voted.\". The participants row below the table keeps its place before anyone has voted, so the description below it does not move when the first vote appears. The voters group updates right away when you vote or withdraw, without waiting for the server.",[11,1706,763,1707,1709,1710,1712,1713,1715],{},[268,1708,1348],{}," tab shows a heat map of the votes per work item and estimate. Each column is an enabled card, each row is a work item, and the cell colour moves from the warning colour to the error colour as more participants vote the same card for the same work item. The number in the cell is the vote count. The heat map stretches across the full width of the bucket panel. With ",[268,1711,1416],{}," on, it counts every participant's votes. With ",[268,1714,1416],{}," off, it counts your own votes and every vote of completed sessions; the rest of the votes stay hidden until their session completes. The moderator sees the same scope as everyone else.",[11,1717,1718,1719,1721,1722,1357,1725,1728,1729,704,1731,1733],{},"A moderator sets the bucket table's ranking mode from the control beside the perspective title: ",[268,1720,1329],{}," (the default, plain table), ",[268,1723,1724],{},"Affinity ranking",[268,1726,1727],{},"Dot ranking",". Only a moderator can change it, and a ranking option becomes available once someone has submitted that ranking. The plain table has no Rank column. ",[268,1730,1724],{},[268,1732,1727],{}," add a Rank column on the right, where each work item shows its rank in a regular lozenge and a card row leaves that cell empty.",[11,1735,1736],{},"The choice is saved on the planning session and applies to everyone. If the change is refused, the selector returns to the last saved mode.",[11,1738,1739,1740,684,1742,1236,1744,1746,1747,1749,1750,1752,1753,1755],{},"Switching into ",[268,1741,1724],{},[268,1743,1727],{},[268,1745,1329],{},", or between the two ranking modes, moves every listed work item to ",[268,1748,1656],{}," right away, before the server responds. If the change is refused, the previous mode and votes return. Switching back to ",[268,1751,1329],{}," keeps the votes. If the last session for an enforced ranking is cancelled or accepted, the bucket ranking mode returns to ",[268,1754,1329],{}," automatically. A completed session keeps the ranking enforced and locks it until the session is cancelled or accepted.",[11,1757,1758],{},"When a ranking is enforced, the planning session tab shows a dismissable informational message above the table in both single and bulk voting. The single voting panel in the issue view shows the same message above the cards. In both places, a vote moves the work items that must follow the rank order, so the order is never broken. A work item that shares the voted item's rank is never pulled or pushed; only work items with a different rank move.",[11,1760,1761],{},"If a vote changes more than one voting session, the message is replaced by a warning-style dismissable message that lists the affected work items. Each work item opens its Jira issue view. The voting panel and the bulk voting widgets each keep their own message.",[11,1763,1764],{},"The informational message stays visible in both places while the enforced ranking has recorded rankings, and it disappears after the rankings are cleared. The affected work items message still appears whenever a vote changes more than one session, even after the rankings are cleared.",[11,1766,1767,1768,1770,1771,1773,1774,1776],{},"Once an enforced ranking has at least one vote or completed session in the bucket table, that ranking is locked so the votes and their order cannot be scrambled. An affinity-enforced ranking locks drag and drop in the affinity table and makes its algorithm selector read-only; a dot-enforced ranking disables the dot column and ",[268,1769,1520],{}," button. A completed session also locks bucket voting and allows the ranking selector to switch only to ",[268,1772,1329],{},". A notice appears in the affected tab, and the other ranking tab stays editable. Changing into or between enforced rankings clears the votes; with a completed session, only switching to ",[268,1775,1329],{}," is allowed.",[11,1778,1779,1780,1782],{},"In the ranked views, work items are listed from best to worst, and each row shows a ",[268,1781,1497],{}," column. Work items of equal rank can be reordered freely within the same card or the No estimate group, but the card rows never move and keep their configured order. No estimate work items stay in the No estimate group at the top. Reordering within the same card or No estimate cannot cross a rank boundary: you cannot drop the item below a better-ranked item or above a worse-ranked item. A refused reorder snaps back and casts no votes. Dropping a work item under a different card is a card assignment: the same push and pull applies as before, so the final item order stays rank-sorted and a run of other work items can move under that card. Work items that share the dragged item's rank are never pulled or pushed; only the dragged item changes card among its rank peers. The Rank header and cells are right aligned. Scrumpy estimates every work item that lands under the card together, not only the one you dragged, so they all get that card's estimate. A free scale perspective follows the same rule with the estimate in place of the card: with a ranking enforced, changing an estimate also moves the work items the change passes to the new estimate, from the estimate field, from the single voting panel and from a planning table bulk field alike, so the rank order stays intact. This holds even when the perspective also has the extra cards enabled, because the numeric estimate always follows the estimate rules.",[64,1784,1786],{"id":1785},"free-scale-bucket","Free scale Bucket",[11,1788,1789,1790,1792,1793,1795,1796,1798,1799,1801],{},"A free scale perspective has no cards, so its Bucket tab replaces the card rows with gap rows. A completed session keeps your recorded vote, so its work item stays at its estimate instead of moving to ",[268,1791,1656],{}," until the session is cancelled or accepted. A completed session cannot be moved or re-estimated. When the ranking is enforced and a completed session exists, every free scale estimate field is disabled and the lock column shows the lock icon on every work item. The ",[268,1794,1266],{}," tab lists the work items from the smallest to the largest estimate. Work items with the same estimate sit together, and no gap row separates them. A highlighted gap row between two different estimates shows the distance, for example \"3 sp gap\". Its height is relative to the other gap rows in the table: the smallest gap present is 21 pixels high and the largest gap present is 90 pixels high, and any gap in between is scaled proportionally, so a table whose gaps are 4 sp, 5 sp and 6 sp still shows 21 pixels, 56 pixels and 90 pixels. Every gap row in a table with one gap, or with gaps of the same size, keeps the 21 pixel height. Work items without a story point vote sit in a highlighted ",[268,1797,1656],{}," group at the top. A narrow first column draws the story point timeline. It has no labels: a 4 pixel line starts at the first work item's dot and ends at the last work item's dot, each work item row with an estimate has a 12 pixel dot on it, and the first and last estimated work items have a 16 pixel dot with a 4 pixel hollow center that closes the timeline. When the perspective writes a time value, each estimation field shows the humanized duration in small text below the story points, centered. The ",[268,1800,1656],{}," group has no dot and no line, so a work item without an estimate never shows a circle on the timeline. Gap rows have no dot, no vertical padding or margins, draw their stretch of the timeline as a dotted line of 4 pixel squares with 4 pixel gaps, and keep their height to show the distance between estimates.",[11,1803,1804,1805,1807,1808,1810,1811,1813,1814,1816],{},"Each work item row shows its Jira key, a compact story point field, and the ",[268,1806,1497],{}," column from the selected ranking mode. Type in the field and click away to save an exact estimate. With a ranking enforced, changing an estimate keeps the ascending rank order: the work items the change passes take the new estimate and join that estimate group, work items of the same rank stay where they are, and withdrawing the estimate also clears the better-ranked estimated work items above it, the way dropping a card into No estimate works. A cross-circle ",[268,1809,1520],{}," button inside the field clears that one vote without editing the number. Drag a work item into a gap to set its estimate to the rounded midpoint of the two neighbouring estimates, drag it onto another work item to give it the same estimate, or drag it into ",[268,1812,1656],{}," to withdraw its vote. The move appears right away and is saved in the background; if the save fails, the row returns to the previous estimate. A voter can withdraw every vote in the panel with ",[268,1815,1520],{}," below the voters group. The description stays below the tabs.",[11,1818,763,1819,1821,1822,1824,1825,1827,1828,1830],{},[268,1820,1348],{}," tab shows the recorded votes in a chart: the horizontal axis is story points, each work item has its own row, and every vote is a dot in that work item's colour. Votes at the same story points fan out so they stay visible. The axis labels are whole story point numbers. A dashed cross marks the perspective's averaged story points on each work item row, rounded to a whole number. The cross appears only when more than one participant voted on that work item; with a single vote it would sit on the dot, so it is hidden. Like the card bucket, every participant sees ",[268,1823,1348],{},". With ",[268,1826,1416],{}," on, the chart plots every participant's vote. With ",[268,1829,1416],{}," off, it plots your own votes and every vote of completed sessions, and the moderator follows the same scope.",[64,1832,1834],{"id":1833},"parametric-bucket","Parametric Bucket",[11,1836,1837,1838,1841,1842,1844,1845,1848,1849,1851],{},"A parametric perspective has a Bucket tab with the same layout, ordering, gap rows and timeline as the free scale one, with two differences. Nothing can be dragged: the table is read only and every vote is cast from its row or from the voting panel. Each row shows the computed result in a read only, compact, subtle number field with the ",[268,1839,1840],{},"sp"," suffix, a cross-circle ",[268,1843,1520],{}," button and an ",[268,1846,1847],{},"Edit vote"," button inside the field. The edit button opens the same slider popup as the planning table, and pressing ",[268,1850,1266],{}," there saves that work item's vote with its slider positions. When the perspective writes a time value, the humanized duration of the result appears in small text below the field, centred. With a ranking enforced, a vote from this tab, from the voting panel or from the planning table bulk field keeps the ascending rank order the same way a free scale vote does, and the work items it passes take the same result and slider positions. A work item that already voted shows its recorded sliders when the popup opens, so the numbers always match the saved result.",[40,1853,1855],{"id":1854},"perspective-columns","Perspective Columns",[11,1857,1858],{},"The table shows a column for every perspective that applies to the work item's type; cells for perspectives that do not apply are left blank. Each cell displays:",[900,1860,1861,1867,1873],{},[642,1862,1863,1866],{},[268,1864,1865],{},"Participation percentage",": the fraction of voters who have voted, shown as a color-coded badge (red below 25%, yellow below 50%, grey below 75%, blue below 100%, and green at 100%). It appears only when required voters are set.",[642,1868,1869,1872],{},[268,1870,1871],{},"Voting session state",": In progress, Paused, or Complete, shown as a badge.",[642,1874,1875,1878,1879,1882,1883,1882,1886,1889,1890,1893],{},[268,1876,1877],{},"Current estimate",": the latest estimate value from Jira, shown when no session is active. Each configured estimate field appears as its own badge in the order story points, time, T-shirt size, separated by middle dots; a field that is not configured is omitted. Story points show an \"sp\" suffix, time values show work-day durations, and T-shirt sizes show the size label. Field target badges match the selected fields, so a perspective with story points, time, and T-shirt fields can show ",[677,1880,1881],{},"10 sp"," · ",[677,1884,1885],{},"1 day",[677,1887,1888],{},"S",". With the ",[268,1891,1892],{},"Default"," target, a T-shirt perspective writes the mapped story points to the board and the size label to the T-shirt field; the cell shows the story points and the size label. A time board shows the duration and the size label. A numeric board never shows a duration. The duration appears only when the estimation target writes a time value: a time board or a Time field, or a Field target with both a story points field and a Time field. The bulk voting cell and the inline voting panel use the same units, so a time board shows the duration in the editor preview and in the open-voting badges, while a numeric board keeps story points. If you change the perspective's estimation target, sequence, story points field, time field, T-shirt field, story points to hours, or estimation board while the planning table is open, the perspective column reloads its values from Jira, so the shown estimates match the new configuration without a page reload.",[40,1895,1897],{"id":1896},"progress-and-status","Progress and Status",[11,1899,1900,1901,1904],{},"When a planning session has a date range, its panel shows a progress bar and a status below the buttons at the bottom: ",[268,1902,1903],{},"Completed"," once the end date has passed, a countdown before the start date, or the remaining time while it is in progress.",[40,1906,803],{"id":1907},"deleting-a-planning-session",[11,1909,1910,1911,796,1913,1915],{},"When a planning session is no longer needed, click ",[268,1912,707],{},[268,1914,647],{},". A confirmation appears first, because deleting a planning session removes it and all of its items permanently, so it disappears from the tab list. Deleting it also removes every record that belongs to the planning session: its chat, the work item chat and reactions of its items, rankings, capacity planning data, standup data, retrospective data, and linked voting sessions.",[11,1917,1918,1919,1922],{},"If there are still active voting sessions, the confirmation becomes a ",[268,1920,1921],{},"Pending estimation sessions"," warning with three choices:",[900,1924,1925,1931,1937],{},[642,1926,1927,1930],{},[268,1928,1929],{},"Do nothing"," (the default): delete the planning session without accepting or cancelling its voting sessions first. The linked voting sessions are removed with the planning session.",[642,1932,1933,1936],{},[268,1934,1935],{},"Cancel all",": cancel every voting session, including completed ones, before deleting the planning session.",[642,1938,1939,1942],{},[268,1940,1941],{},"Accept completed",": accept the estimates of every completed voting session, including any value the moderator set, before deleting the planning session.",[11,1944,1945,1946,1949,1950,1952],{},"Choose ",[268,1947,1948],{},"Go back"," to keep the planning session. The dialog closes as soon as you confirm and the planning session disappears from the tab list right away. If it cannot be deleted, it comes back. If a Jira write fails during ",[268,1951,1941],{},", the work items whose write succeeded are accepted, the failed session stays completed so it can be retried, and an error dialog after the delete lists the failed work item and the reason.",[11,1954,1955],{},"If another moderator deletes a planning session while your page is open, its tab disappears from your list by itself and the first remaining session opens. You see no error message and nothing asks you to reload.",[40,1957,1959],{"id":1958},"estimating-inline","Estimating Inline",[11,1961,1962,1963,1966],{},"The Refinement\u002Fgrooming tab keeps an inline Voting Panel in a fixed column on the right. Highlight a work item to load it into the panel; until you pick one, it shows a ",[268,1964,1965],{},"No work item selected"," empty state.",[11,1968,1969],{},"The panel and the planning table stay in step while you work. A vote, a pause, a resume, a completion, a cancellation, or a changed required-voter list made in one place appears in the other straight away. An accepted estimate updates both places as soon as the estimate is written. If a save fails, both places return to the previous state together.",[11,1971,1972,1973,1975],{},"The work item key in the table shows the summary in a tooltip. When a moderator edits the summary in the panel's ",[268,1974,949],{}," tab, the tooltip updates without a reload. When a perspective estimates with a board, the current estimate comes from Jira's board estimation, so it appears even when the estimation field is hidden from the work item screen.",[11,1977,1978,1979,704,1981,1983,1984,1986,1987,1989,1990,1993,1994,1997,1998,2000,2001,2003],{},"The inline panel has ",[268,1980,1266],{},[268,1982,949],{}," while the session runs, plus ",[268,1985,1348],{}," with open voting and the perspective's chart tab when the perspective is parametric. ",[268,1988,949],{}," shows a ",[268,1991,1992],{},"Summary"," label above the current Jira summary and a ",[268,1995,1996],{},"Description"," label above the work item description rendered as rich text; participants who are not moderators see the description without an avatar. It is read once per work item and reused while the page stays open; a summary or description change made in the Details tab appears for other participants without a reload, and an edit in one perspective also updates the Details tab of every other perspective in the same panel; moderators can edit both the summary and the description there, and every participant sees the current Jira content. An edit saves when you click away, switch to another tab, or close the panel, even if the short description pause has not finished. After completion the inline panel keeps ",[268,1999,1348],{},", the chart tab for a parametric perspective, and ",[268,2002,949],{},", with the final result below the tabs.",{"title":158,"searchDepth":159,"depth":159,"links":2005},[2006,2007,2008,2012,2018,2021,2028,2029,2030,2031],{"id":623,"depth":159,"text":624},{"id":732,"depth":159,"text":733},{"id":806,"depth":159,"text":807,"children":2009},[2010,2011],{"id":813,"depth":165,"text":814},{"id":844,"depth":165,"text":845},{"id":925,"depth":159,"text":926,"children":2013},[2014,2015,2016,2017],{"id":960,"depth":165,"text":961},{"id":993,"depth":165,"text":994},{"id":1016,"depth":165,"text":1017},{"id":1080,"depth":165,"text":1081},{"id":1229,"depth":159,"text":1230,"children":2019},[2020],{"id":1302,"depth":165,"text":1303},{"id":1336,"depth":159,"text":1337,"children":2022},[2023,2024,2025,2026,2027],{"id":1396,"depth":165,"text":1312},{"id":1560,"depth":165,"text":1316},{"id":1650,"depth":165,"text":1360},{"id":1785,"depth":165,"text":1786},{"id":1833,"depth":165,"text":1834},{"id":1854,"depth":159,"text":1855},{"id":1896,"depth":159,"text":1897},{"id":1907,"depth":159,"text":803},{"id":1958,"depth":159,"text":1959},"2026-07-26","Create planning sessions in Jira, add work items from a filter or work item view, and estimate a backlog in bulk.","Planning Sessions","\u002Fog\u002Fguide-planning-sessions.jpg",[2037,2038,2039,2040],"sprint planning","backlog refinement","bulk voting","jira planning",{},8,"\u002Fgetting-started\u002Fplanning-sessions","guide",{"title":608,"description":2033},{"loc":2043,"lastmod":178},"planning-sessions","guide\u002Fen\u002Fplanning-sessions","guide\u002Fplanning-sessions","Fqq0SvXd6Di2LRZ7TN9xfb0KrOEosUwjoiSwxpkPlcs",1795345544798]