[{"data":1,"prerenderedAt":976},["ShallowReactive",2],{"blog-index-en":3},[4,204,346,510,606,809],{"id":5,"title":6,"author":7,"body":8,"dateModified":179,"datePublished":180,"description":181,"extension":182,"heading":183,"image":184,"imageAlt":17,"keywords":185,"locale":191,"meta":192,"navigation":193,"path":194,"reviewed":193,"seo":195,"sitemap":196,"slug":201,"stem":202,"translationKey":201,"__hash__":203},"blog\u002Fblog\u002Fen\u002Fmanage-sprint-dependencies-with-chained-pull-requests.md","Sprint dependencies and chained pull requests | AELBOX","AELBOX",{"type":9,"value":10,"toc":158},"minimark",[11,23,26,35,40,45,54,57,61,64,69,72,76,79,83,86,90,93,101,106,110,113,117,120,124,127,131,134,138,141,145,148,152,155],[12,13,14],"p",{},[15,16],"img",{"alt":17,"height":18,"loading":19,"src":20,"width":21,"fetchPriority":22},"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",[12,24,25],{},"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.",[12,27,28],{},[15,29],{"alt":30,"height":31,"loading":32,"src":33,"width":31,"decoding":34},"Dependencies between tasks",336,"lazy","\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fblog-dep1.png","async",[12,36,37],{},[38,39,30],"em",{},[41,42,44],"h2",{"id":43},"the-old-fashioned-way","The old-fashioned way",[12,46,47,48,53],{},"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 ",[49,50,52],"a",{"href":51},"\u002Fblog\u002Fcomparison-metrics-for-agile-teams","the team is unhappy",".",[12,55,56],{},"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.",[41,58,60],{"id":59},"working-on-dependent-tasks-simultaneously","Working on dependent tasks simultaneously",[12,62,63],{},"There is a way to do this with a small overhead. When team members work on tasks simultaneously, there are several advantages.",[65,66,68],"h3",{"id":67},"better-collaboration","Better collaboration",[12,70,71],{},"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.",[65,73,75],{"id":74},"avoiding-the-idle-time","Avoiding the idle time",[12,77,78],{},"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.",[65,80,82],{"id":81},"pull-requests-ready-for-code-review-earlier","Pull requests ready for code review earlier",[12,84,85],{},"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.",[41,87,89],{"id":88},"using-chained-stacked-pull-requests","Using chained (stacked) pull requests",[12,91,92],{},"This level of concurrency requires the right tooling. With Git-based version control, it is straightforward. The steps below describe the process.",[12,94,95],{},[15,96],{"alt":97,"height":98,"loading":32,"src":99,"width":100,"decoding":34},"Dependency tree",438,"\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fdep-img2.png",800,[12,102,103],{},[38,104,105],{},"Dependency tree (working on 6 dependent tasks simultaneously)",[65,107,109],{"id":108},"outline-the-dependencies-clearly","Outline the dependencies clearly",[12,111,112],{},"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.",[65,114,116],{"id":115},"start-with-the-root-tasks-first","Start with the root tasks first",[12,118,119],{},"Every dependency chain has root tasks that depend on nothing else. Work on them can start on day one.",[65,121,123],{"id":122},"do-core-implementation-first","Do core implementation first",[12,125,126],{},"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.",[65,128,130],{"id":129},"organize-and-code-review-in-a-fifo-queue","Organize and code review in a FIFO queue",[12,132,133],{},"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.",[41,135,137],{"id":136},"the-overhead","The overhead",[12,139,140],{},"Maintaining a chain of dependent branches has benefits, but also some drawbacks.",[65,142,144],{"id":143},"rebasing-or-merging","Rebasing or merging",[12,146,147],{},"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.",[65,149,151],{"id":150},"teamwork","Teamwork",[12,153,154],{},"A dependency chain needs a collaborative team whose members are willing to talk to each other. It cannot work if people work in isolation.",[12,156,157],{},"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":159,"searchDepth":160,"depth":160,"links":161},"",2,[162,163,169,175],{"id":43,"depth":160,"text":44},{"id":59,"depth":160,"text":60,"children":164},[165,167,168],{"id":67,"depth":166,"text":68},3,{"id":74,"depth":166,"text":75},{"id":81,"depth":166,"text":82},{"id":88,"depth":160,"text":89,"children":170},[171,172,173,174],{"id":108,"depth":166,"text":109},{"id":115,"depth":166,"text":116},{"id":122,"depth":166,"text":123},{"id":129,"depth":166,"text":130},{"id":136,"depth":160,"text":137,"children":176},[177,178],{"id":143,"depth":166,"text":144},{"id":150,"depth":166,"text":151},"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",[186,187,188,189,190],"sprint dependencies","stacked pull requests","chained pull requests","code review","agile delivery","en",{},true,"\u002Fblog\u002Fen\u002Fmanage-sprint-dependencies-with-chained-pull-requests",{"title":6,"description":181},{"loc":194,"images":197,"lastmod":179},[198,199,200],{"loc":20},{"loc":33},{"loc":99},"manage-sprint-dependencies-with-chained-pull-requests","blog\u002Fen\u002Fmanage-sprint-dependencies-with-chained-pull-requests","wvh2xXsMf-_D4su-7k6V7w5M5HeQzIs6vYvyGaF6jn8",{"id":205,"title":206,"author":7,"body":207,"dateModified":179,"datePublished":325,"description":326,"extension":182,"heading":327,"image":328,"imageAlt":213,"keywords":329,"locale":191,"meta":335,"navigation":193,"path":336,"reviewed":193,"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":9,"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],[12,210,211],{},[15,212],{"alt":213,"height":214,"loading":19,"src":215,"width":21,"fetchPriority":22},"A ruler, planning poker cards and a coffee cup on a table",958,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Fcoffee-table-ruler.webp",[12,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?",[41,220,222],{"id":221},"creating-a-competition","Creating a competition",[12,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.",[12,227,228],{},[15,229],{"alt":230,"height":231,"loading":32,"src":232,"width":233,"decoding":34},"Create a competition",487,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun2.png",525,[12,235,236],{},[38,237,230],{},[41,239,241],{"id":240},"the-metrics-for-creating-equal-opportunities","The metrics for creating equal opportunities",[12,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.",[65,246,248],{"id":247},"successful-sprints","Successful sprints",[12,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.",[12,253,254],{},[15,255],{"alt":256,"height":257,"loading":32,"src":258,"width":259,"decoding":34},"Sprint to a goal",680,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun1.png",874,[12,261,262],{},[38,263,256],{},[12,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.",[65,273,275],{"id":274},"velocity-stability-and-the-honest-estimation","Velocity stability and the honest estimation",[12,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.",[12,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.",[12,283,284,285,53],{},"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 ",[49,286,288],{"href":287},"\u002Fblog\u002Fsheepherding-story-points","grounded in evidence",[65,290,292],{"id":291},"capacity-predictability-avoiding-unexpected-work","Capacity predictability (avoiding unexpected work)",[12,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.",[12,297,298,299,53],{},"Complex work can start early, even if only to discover that it needs its own set of stories. That still reduces the ",[49,300,302],{"href":301},"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint","risk of the unknown",[12,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.",[65,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)",[12,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.",[12,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":159,"searchDepth":160,"depth":160,"links":317},[318,319],{"id":221,"depth":160,"text":222},{"id":240,"depth":160,"text":241,"children":320},[321,322,323,324],{"id":247,"depth":166,"text":248},{"id":274,"depth":166,"text":275},{"id":291,"depth":166,"text":292},{"id":308,"depth":166,"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":179},[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":7,"body":349,"dateModified":179,"datePublished":487,"description":488,"extension":182,"heading":489,"image":490,"imageAlt":355,"keywords":491,"locale":191,"meta":496,"navigation":193,"path":497,"reviewed":193,"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":9,"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],[12,352,353],{},[15,354],{"alt":355,"height":18,"loading":19,"src":356,"width":21,"fetchPriority":22},"A flock of sheep and planning poker cards on a coffee table","\u002Fblog\u002Fsheepherding-story-points\u002Fcoffee-table-sheep.webp",[12,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.",[41,361,363],{"id":362},"the-characters-in-voting","The characters in voting",[12,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.",[12,372,373],{},[15,374],{"alt":375,"height":376,"loading":32,"src":377,"width":378,"decoding":34},"The sheep effect",746,"\u002Fblog\u002Fsheepherding-story-points\u002Fsheep-1.png",1779,[12,380,381],{},[38,382,375],{},[65,384,386],{"id":385},"the-overconfident-voter","The overconfident voter",[12,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.",[12,391,392],{},"This person usually votes lower than the honest estimate. Perhaps only they could finish the story that quickly, and only with luck.",[12,394,395],{},[15,396],{"alt":386,"height":397,"loading":32,"src":398,"width":399,"decoding":34},290,"\u002Fblog\u002Fsheepherding-story-points\u002Fimg7.png",600,[12,401,402],{},[38,403,386],{},[12,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.",[65,408,410],{"id":409},"the-quiet-voter","The quiet voter",[12,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.",[12,415,416],{},[15,417],{"alt":410,"height":397,"loading":32,"src":418,"width":399,"decoding":34},"\u002Fblog\u002Fsheepherding-story-points\u002Fimg5.png",[12,420,421],{},[38,422,410],{},[65,424,426],{"id":425},"the-disengaged-voter","The disengaged voter",[12,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.",[12,431,432],{},[15,433],{"alt":426,"height":434,"loading":32,"src":435,"width":436,"decoding":34},353,"\u002Fblog\u002Fsheepherding-story-points\u002Fimg4.png",758,[12,438,439],{},[38,440,426],{},[65,442,444],{"id":443},"the-tired-voter","The tired voter",[12,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.",[12,449,450],{},[15,451],{"alt":444,"height":397,"loading":32,"src":452,"width":399,"decoding":34},"\u002Fblog\u002Fsheepherding-story-points\u002Fimg6.png",[12,454,455],{},[38,456,444],{},[41,458,460],{"id":459},"how-to-keep-the-attention-during-estimation","How to keep the attention during estimation",[12,462,463,464,468,469,471],{},"Estimation matters because only honest story points can ",[49,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.",[12,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\".",[12,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":159,"searchDepth":160,"depth":160,"links":479},[480,486],{"id":362,"depth":160,"text":363,"children":481},[482,483,484,485],{"id":385,"depth":166,"text":386},{"id":409,"depth":166,"text":410},{"id":425,"depth":166,"text":426},{"id":443,"depth":166,"text":444},{"id":459,"depth":160,"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":179},[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":7,"body":513,"dateModified":179,"datePublished":586,"description":587,"extension":182,"heading":588,"image":589,"imageAlt":519,"keywords":590,"locale":191,"meta":595,"navigation":193,"path":596,"reviewed":193,"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":9,"value":514,"toc":581},[515,522,530,534,537,545,549,553,556,560,563,566,574,578],[12,516,517],{},[15,518],{"alt":519,"height":520,"loading":19,"src":521,"width":21,"fetchPriority":22},"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",[12,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 ",[49,526,528],{"href":527},"\u002Fblog\u002Fthe-importance-of-predictable-velocity","capacity calculations"," look so precise?",[41,531,533],{"id":532},"the-rush-to-deliver-more","The rush to deliver more",[12,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.",[12,538,539],{},[15,540],{"alt":541,"height":542,"loading":32,"src":543,"width":544,"decoding":34},"The doomed sprint",349,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fimg1.png",400,[12,546,547],{},[38,548,541],{},[41,550,552],{"id":551},"the-hectic-end-of-a-sprint-during-a-delivery-rush","The hectic end of a sprint during a delivery rush",[12,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.",[41,557,559],{"id":558},"let-the-team-deliver-more-by-its-own-will","Let the team deliver more by its own will",[12,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.",[12,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.",[12,567,568],{},[15,569],{"alt":570,"height":571,"loading":32,"src":572,"width":573,"decoding":34},"Deliver early, deliver extra",320,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fimg3-1.png",296,[12,575,576],{},[38,577,570],{},[12,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":159,"searchDepth":160,"depth":160,"links":582},[583,584,585],{"id":532,"depth":160,"text":533},{"id":551,"depth":160,"text":552},{"id":558,"depth":160,"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":179},[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,"author":7,"body":609,"dateModified":179,"datePublished":787,"description":788,"extension":182,"heading":789,"image":790,"imageAlt":615,"keywords":791,"locale":191,"meta":795,"navigation":193,"path":796,"reviewed":193,"seo":797,"sitemap":798,"slug":806,"stem":807,"translationKey":806,"__hash__":808},"blog\u002Fblog\u002Fen\u002Fcorrectly-estimating-release-deadline.md","How to estimate a release deadline with story points | AELBOX",{"type":9,"value":610,"toc":773},[611,617,620,624,631,635,638,646,650,654,657,660,664,667,675,680,684,687,691,694,698,701,708,713,717,720,724,727,735,739,743,746,751,758,766,770],[12,612,613],{},[15,614],{"alt":615,"height":18,"loading":19,"src":616,"width":21,"fetchPriority":22},"Planning poker cards, a Gantt chart and a coffee cup on a table","\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fcoffee-table-gantt-cards.webp",[12,618,619],{},"An important part of project management is estimating a project's release date. But how do you predict when a large, complex system will be delivered?",[41,621,623],{"id":622},"the-estimation-problems","The estimation problems",[12,625,626,627,630],{},"To deliver on time, you need a reliable estimate of the work. ",[49,628,629],{"href":527},"Estimating tasks is usually difficult",", especially when you must commit to time-based estimates for each task. Psychologically, committing to a completion time is hard, and those commitments often fail.",[65,632,634],{"id":633},"the-problem-with-time","The problem with time",[12,636,637],{},"Estimating time is problematic for a simple reason: the more complex the task, the greater the chance of missing the deadline. It also depends on who picks up the task. Team members work at different speeds and deliver different amounts of work. Because availability changes with vacations and training, a task estimated by the fastest team member may end up with the slowest. The neat Gantt chart turns into a mess: tasks become overdue, and managers constantly worry whether the project will finish in time.",[12,639,640],{},[15,641],{"alt":642,"height":643,"loading":32,"src":644,"width":645,"decoding":34},"Broken Gantt chart",351,"\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fstory1.png",510,[12,647,648],{},[38,649,642],{},[65,651,653],{"id":652},"the-resistance-against-time-estimates","The resistance against time estimates",[12,655,656],{},"When implementers are asked for an estimate, they often resist: if the estimate is missed, who is to blame? And if a task estimated by one person ends up with someone else, who is blamed when the actual time differs?",[12,658,659],{},"The result is reluctance to estimate at all, which makes it difficult for management to estimate delivery dates properly.",[41,661,663],{"id":662},"using-story-points","Using story points",[12,665,666],{},"Story points offer an alternative to time-based estimates. A story point is not a fixed unit of work; it is a relative estimate that grows exponentially. The whole team estimates together during refinement.",[12,668,669],{},[15,670],{"alt":671,"height":672,"loading":32,"src":673,"width":674,"decoding":34},"Example story points",210,"\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fstory2.png",801,[12,676,677],{},[38,678,679],{},"Example estimates",[65,681,683],{"id":682},"sharing-responsibility","Sharing responsibility",[12,685,686],{},"With story points, the whole team estimates each task. The estimate is accepted when everyone agrees on it. That avoids later arguments about who estimated the task and how long it really took. The team agreed up front, so responsibility is shared.",[65,688,690],{"id":689},"estimating-complexity","Estimating complexity",[12,692,693],{},"Story points capture the complexity of a task, including its external dependencies and the risk that something might go wrong. Because they are not a commitment to a physical metric like time, they are easier for the team to give.",[65,695,697],{"id":696},"the-smallest-estimate","The smallest estimate",[12,699,700],{},"Because story points are relative, you need an anchor to start from. The anchor is the smallest unit of work that requires some implementation effort. It is the smallest amount of work the team can estimate.",[12,702,703],{},[15,704],{"alt":697,"height":705,"loading":32,"src":706,"width":707,"decoding":34},206,"\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fstory3.png",141,[12,709,710],{},[38,711,712],{},"The lowest estimate",[65,714,716],{"id":715},"the-biggest-estimate","The biggest estimate",[12,718,719],{},"Story points grow exponentially to show that the more complex a task is, the harder it is to estimate. The scale can extend to infinity (∞), though that estimate is rarely used. The largest estimate should be the most work one person can complete in a sprint on average. The sprint length itself should match the largest amount of work one person can handle without losing control of the task.",[65,721,723],{"id":722},"the-stories-that-are-bigger-than-the-biggest-estimate","The stories that are bigger than the biggest estimate",[12,725,726],{},"Some tasks receive more story points than one person can complete in a sprint. Putting them in a sprint causes carry-over. Carry-over makes the sprint feel incomplete and the work feel unfinished. Tasks estimated above that limit must be split into smaller units and estimated again.",[12,728,729],{},[15,730],{"alt":731,"height":732,"loading":32,"src":733,"width":734,"decoding":34},"Splitting 13 story points",201,"\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fstory4.png",272,[12,736,737],{},[38,738,731],{},[41,740,742],{"id":741},"the-story-points-velocity","The story points velocity",[12,744,745],{},"Velocity is the average number of story points a team completes in a sprint at full availability. Availability is the share of the sprint the team can actually spend on project work after vacations, training and support. Capacity is velocity multiplied by availability.",[12,747,748],{},[38,749,750],{},"capacity = velocity × availability",[12,752,753,754,757],{},"Because capacity is expressed in story points, it can be converted into time using the team's story-point-to-time ratio. When ",[49,755,756],{"href":527},"velocity is predictable",", the release date can be estimated precisely. Based on story points and sprints, the resulting Gantt chart is stable and predictable:",[12,759,760],{},[15,761],{"alt":762,"height":763,"loading":32,"src":764,"width":765,"decoding":34},"Fixed Gantt chart",362,"\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fstory5.png",519,[12,767,768],{},[38,769,762],{},[12,771,772],{},"That is the shift: once velocity is stable, the release date becomes a calculation rather than a guess.",{"title":159,"searchDepth":160,"depth":160,"links":774},[775,779,786],{"id":622,"depth":160,"text":623,"children":776},[777,778],{"id":633,"depth":166,"text":634},{"id":652,"depth":166,"text":653},{"id":662,"depth":160,"text":663,"children":780},[781,782,783,784,785],{"id":682,"depth":166,"text":683},{"id":689,"depth":166,"text":690},{"id":696,"depth":166,"text":697},{"id":715,"depth":166,"text":716},{"id":722,"depth":166,"text":723},{"id":741,"depth":160,"text":742},"2018-04-14","Time estimates fail when complexity and availability shift. Learn how story points, shared estimates and velocity make release dates predictable.","How to estimate a release deadline","\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fcoffee-table-gantt-cards.jpg",[792,492,495,793,794],"release deadline","sprint velocity","capacity planning",{},"\u002Fblog\u002Fen\u002Fcorrectly-estimating-release-deadline",{"title":608,"description":788},{"loc":796,"images":799,"lastmod":179},[800,801,802,803,804,805],{"loc":616},{"loc":644},{"loc":673},{"loc":706},{"loc":733},{"loc":764},"correctly-estimating-release-deadline","blog\u002Fen\u002Fcorrectly-estimating-release-deadline","5hHpuemcBQG8seJxBiCZ8W0L0PEUFBolCkaE0AeBafk",{"id":810,"title":811,"author":7,"body":812,"dateModified":179,"datePublished":787,"description":958,"extension":182,"heading":959,"image":960,"imageAlt":818,"keywords":961,"locale":191,"meta":964,"navigation":193,"path":965,"reviewed":193,"seo":966,"sitemap":967,"slug":973,"stem":974,"translationKey":973,"__hash__":975},"blog\u002Fblog\u002Fen\u002Fthe-importance-of-predictable-velocity.md","Predictable velocity: make sprint commitments reliable | AELBOX",{"type":9,"value":813,"toc":948},[814,820,823,827,830,833,836,844,848,852,855,859,862,865,872,879,883,887,890,893,896,899,903,906,909,916,920,924,932,935,939,945],[12,815,816],{},[15,817],{"alt":818,"height":18,"loading":19,"src":819,"width":21,"fetchPriority":22},"Planning poker cards and a stopwatch on a coffee table","\u002Fblog\u002Fthe-importance-of-predictable-velocity\u002Fcoffee-table-chronometer.webp",[12,821,822],{},"Predictable velocity is the ability to know, in advance, how much work a team will complete in a given period, based on its availability.",[41,824,826],{"id":825},"the-problem-of-varying-velocity","The problem of varying velocity",[12,828,829],{},"When velocity varies between sprints, planning a release becomes difficult. No one knows when the work will be delivered, and the whole Scrum process breaks down. Chaos takes over, which does little for team morale.",[12,831,832],{},"Varying velocity usually happens because team members try to do their best and commit to more than they can deliver. In a collaborative environment with a well-set-up development process, there is more to a task than straightforward implementation. Some team members get lucky and land on tasks that are relatively simple to implement, while others run into a problem nobody anticipated. In one sprint, velocity looks high because the team is finishing carry-overs; in the next, it drops because new carry-overs appear.",[12,834,835],{},"Carry-overs create the impression that the team is underperforming: it could do more, but something unpredictable always gets in the way. Management notices the problem, sees the missed deadlines and tension builds among team members.",[12,837,838],{},[15,839],{"alt":840,"height":841,"loading":32,"src":842,"width":843,"decoding":34},"Regular sprint with carry-overs",198,"\u002Fblog\u002Fthe-importance-of-predictable-velocity\u002Fstory6.png",461,[12,845,846],{},[38,847,840],{},[41,849,851],{"id":850},"the-common-problems-in-maintaining-predictability","The common problems in maintaining predictability",[12,853,854],{},"The problems vary by project, but many are common to all types of projects. Here are the usual ones, with practical fixes.",[65,856,858],{"id":857},"expect-the-unexpected","Expect the unexpected",[12,860,861],{},"Some tasks need research before they can start. Imagine a feature that depends on a third-party company that may not respond when you need it. Or a feature that cannot be implemented as planned because the team misunderstood the underlying technology when creating the task.",[12,863,864],{},"If such a task is added to a sprint without the necessary research, it is likely to take longer than expected, and the estimate will be blamed. Some would argue that you need a spike to research the subject first. But how do you know which tasks need one?",[12,866,867,868,871],{},"The only way is to start ",[49,869,870],{"href":301},"working on a task in advance",". Starting before a task is planned makes it possible to find issues before they occur. With that approach, a task enters a sprint only when it is clear and some of the work is already done.",[12,873,874],{},[15,875],{"alt":876,"height":841,"loading":32,"src":877,"width":878,"decoding":34},"Sprints with tasks started in advance","\u002Fblog\u002Fthe-importance-of-predictable-velocity\u002Fstory7.png",721,[12,880,881],{},[38,882,876],{},[65,884,886],{"id":885},"avoid-fuzzy-task-definitions","Avoid fuzzy task definitions",[12,888,889],{},"Some tasks look acceptable to their creator but omit important details. Some implementation details can seriously affect delivery.",[12,891,892],{},"Business stakeholders may argue that task definitions should contain no technical detail, yet implementers often find the business requirements too vague to act on.",[12,894,895],{},"The solution is a technical design document that the implementation task references. That makes it clear what exactly needs to be built.",[12,897,898],{},"It also helps to include technical details in the task description, so implementers know what needs to be done and can spot potential issues early.",[65,900,902],{"id":901},"reduce-capacity-using-the-fibonacci-sequence","Reduce capacity using the Fibonacci sequence",[12,904,905],{},"Sometimes team members take vacation, or a public holiday falls within the sprint. Training and internal events also reduce availability: the time the team can spend on project work. In that case, capacity must be reduced to reflect the missing people.",[12,907,908],{},"Velocity is assumed to be constant, but it is calculated from the average velocity of everyone in the team. For simplicity, assume one person completes one story point per day. If one person is missing for one day, reduce the sprint's capacity by one story point. If two people are missing for two days (four story points), reduce capacity by five story points (the next Fibonacci number) rather than four. If two people are missing for three days, reduce capacity by eight points rather than six, to account for dependency risk.",[12,910,911],{},[15,912],{"alt":913,"height":841,"loading":32,"src":914,"width":915,"decoding":34},"Committing less capacity than calculated","\u002Fblog\u002Fthe-importance-of-predictable-velocity\u002Fstory8.png",392,[12,917,918],{},[38,919,913],{},[65,921,923],{"id":922},"avoid-dependent-tasks","Avoid dependent tasks",[12,925,926,927,931],{},"Often, one person completes a task that another team member's task depends on. This creates ",[49,928,930],{"href":929},"\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests","in-team or inter-team dependencies",". If the first task is late, every dependent task slips. Team members idle, then rush once the dependency clears, wasting valuable time.",[12,933,934],{},"Dependent tasks can start earlier, so that by the next sprint the critical upstream tasks are almost complete. That reduces the dependency's impact on velocity in the current sprint.",[65,936,938],{"id":937},"estimate-honestly","Estimate honestly",[12,940,941,944],{},[49,942,943],{"href":287},"Estimating tasks honestly"," is difficult and requires the whole team's attention. Everyone should estimate without being influenced by other members' estimates. Only honest estimates show how long an epic will really take and keep release dates realistic.",[12,946,947],{},"Predictable velocity is not a tool or a metric you impose on a team; it is the result of removing surprises one by one. Start with the five fixes above, and the release date stops being a guess.",{"title":159,"searchDepth":160,"depth":160,"links":949},[950,951],{"id":825,"depth":160,"text":826},{"id":850,"depth":160,"text":851,"children":952},[953,954,955,956,957],{"id":857,"depth":166,"text":858},{"id":885,"depth":166,"text":886},{"id":901,"depth":166,"text":902},{"id":922,"depth":166,"text":923},{"id":937,"depth":166,"text":938},"Why velocity swings between sprints and how to make commitments predictable: five practical fixes for planning, capacity and dependencies.","The importance of predictable velocity","\u002Fblog\u002Fthe-importance-of-predictable-velocity\u002Fcoffee-table-chronometer.jpg",[962,793,495,492,963],"predictable velocity","release planning",{},"\u002Fblog\u002Fen\u002Fthe-importance-of-predictable-velocity",{"title":811,"description":958},{"loc":965,"images":968,"lastmod":179},[969,970,971,972],{"loc":819},{"loc":842},{"loc":877},{"loc":914},"the-importance-of-predictable-velocity","blog\u002Fen\u002Fthe-importance-of-predictable-velocity","ZjgnIGZ65QKzZVrMoDnfWPmmD_dvSKmf4Yz1OZPKd0c",1795345544741]