[{"data":1,"prerenderedAt":274},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fwhy-better-than-scrum":3},{"id":4,"title":5,"body":6,"description":266,"extension":267,"meta":268,"navigation":269,"path":270,"seo":271,"stem":272,"__hash__":273},"docs\u002Fdocs\u002Fwhy-better-than-scrum.md","Why this beats Scrum",{"type":7,"value":8,"toc":256},"minimark",[9,14,18,21,25,85,93,97,100,103,109,113,116,119,126,130,233,237,240,253],[10,11,13],"h2",{"id":12},"the-honest-comparison","The honest comparison",[15,16,17],"p",{},"Scrum is a well-intentioned framework that solved real problems in early-2000s software teams: lack of structure, invisible progress, scope creep, no delivery cadence. Those problems were real and Scrum addressed them.",[15,19,20],{},"The problem is that Scrum was designed for human teams where coordination overhead is the dominant bottleneck. When you replace most of the team with AI agents, coordination overhead collapses - and Scrum's ceremony, which existed to manage that coordination, becomes pure waste.",[10,22,24],{"id":23},"zero-ceremony","Zero ceremony",[26,27,28,41],"table",{},[29,30,31],"thead",{},[32,33,34,38],"tr",{},[35,36,37],"th",{},"Scrum",[35,39,40],{},"FFF",[42,43,44,53,61,69,77],"tbody",{},[32,45,46,50],{},[47,48,49],"td",{},"Sprint planning (2-4 hrs every 2 weeks)",[47,51,52],{},"Backlog refinement runs continuously and asynchronously",[32,54,55,58],{},[47,56,57],{},"Daily standup (15 min × 5 days × 52 weeks = 65 hrs\u002Fyear)",[47,59,60],{},"Interruptions only (typically 0-2 per ticket, \u003C5 min each)",[32,62,63,66],{},[47,64,65],{},"Sprint review (1-2 hrs every 2 weeks)",[47,67,68],{},"Validation Package review (\u003C15 min per ticket)",[32,70,71,74],{},[47,72,73],{},"Retrospective (1-2 hrs every 2 weeks)",[47,75,76],{},"Prompt refinement when needed (10-30 min, rarely)",[32,78,79,82],{},[47,80,81],{},"Backlog refinement (1+ hr per week)",[47,83,84],{},"Automatic",[15,86,87,88,92],{},"A typical Scrum team spends roughly ",[89,90,91],"strong",{},"15-20% of working hours in ceremony",". That percentage is higher for senior engineers and managers whose time is most expensive. FFF reduces this to near zero.",[10,94,96],{"id":95},"instant-feedback","Instant feedback",[15,98,99],{},"In Scrum, you discover whether work is complete and correct at the Sprint Review - up to two weeks after the work was done. By then, the developer has context-switched to other tickets. The cost of re-engagement is high.",[15,101,102],{},"In FFF, a Validation Package arrives within hours of triggering a ticket. The code is fresh. The context is clear. Issues are identified and returned to the Forge loop immediately, before cognitive context is lost.",[104,105,106],"blockquote",{},[15,107,108],{},"The feedback loop in FFF is measured in hours. In Scrum it is measured in weeks.",[10,110,112],{"id":111},"reduced-cognitive-load","Reduced cognitive load",[15,114,115],{},"Managing a Scrum team requires managing people - their motivation, their blockers, their velocity, their communication. This is cognitively expensive and emotionally demanding work that compounds at scale.",[15,117,118],{},"In FFF, you manage a process. When something goes wrong, the question is never \"why did the developer do that?\" - it is \"what was missing from the spec?\" The fix is an edit to a text file, not a difficult conversation.",[15,120,121,122,125],{},"This is not dehumanising. It is a recognition that the highest-value human skill in a software team is ",[89,123,124],{},"judgment"," - deciding what to build and confirming that it is correct. FFF concentrates human effort on judgment and removes the coordination overhead that dilutes it.",[10,127,129],{"id":128},"direct-comparison","Direct comparison",[26,131,132,143],{},[29,133,134],{},[32,135,136,139,141],{},[35,137,138],{},"Dimension",[35,140,37],{},[35,142,40],{},[42,144,145,156,167,178,189,200,211,222],{},[32,146,147,150,153],{},[47,148,149],{},"Delivery cadence",[47,151,152],{},"Fixed sprint (1-4 weeks)",[47,154,155],{},"Continuous (hours to days)",[32,157,158,161,164],{},[47,159,160],{},"Planning overhead",[47,162,163],{},"High",[47,165,166],{},"Near zero",[32,168,169,172,175],{},[47,170,171],{},"Progress visibility",[47,173,174],{},"Sprint burndown",[47,176,177],{},"Ticket state machine",[32,179,180,183,186],{},[47,181,182],{},"Feedback latency",[47,184,185],{},"End of sprint",[47,187,188],{},"Hours after trigger",[32,190,191,194,197],{},[47,192,193],{},"Quality gate",[47,195,196],{},"Code review + manual QA",[47,198,199],{},"Automated review + tester in loop",[32,201,202,205,208],{},[47,203,204],{},"Metric",[47,206,207],{},"Velocity (story points\u002Fsprint)",[47,209,210],{},"Cycle Time (hours)",[32,212,213,216,219],{},[47,214,215],{},"Human bottleneck",[47,217,218],{},"Sprint planning, standups, reviews",[47,220,221],{},"Validation Package audit",[32,223,224,227,230],{},[47,225,226],{},"Scalability",[47,228,229],{},"Degrades with team size",[47,231,232],{},"Scales by adding parallel agents",[10,234,236],{"id":235},"when-scrum-still-wins","When Scrum still wins",[15,238,239],{},"FFF is not universally superior. Scrum remains a better choice when:",[241,242,243,247,250],"ul",{},[244,245,246],"li",{},"Your team is primarily human and the social coordination function of ceremonies has real value",[244,248,249],{},"You are in early product discovery where requirements are genuinely unknowable and frequent human pivots are expected",[244,251,252],{},"Your organisation's culture and compliance requirements mandate sprint-based reporting to stakeholders",[15,254,255],{},"FFF works best when the requirement space is reasonably well understood, the technical domain is familiar to the agents, and the goal is efficient, reliable delivery - not creative exploration.",{"title":257,"searchDepth":258,"depth":258,"links":259},"",2,[260,261,262,263,264,265],{"id":12,"depth":258,"text":13},{"id":23,"depth":258,"text":24},{"id":95,"depth":258,"text":96},{"id":111,"depth":258,"text":112},{"id":128,"depth":258,"text":129},{"id":235,"depth":258,"text":236},"A direct comparison of FFF and Scrum across the dimensions that matter for software delivery.","md",{},true,"\u002Fdocs\u002Fwhy-better-than-scrum",{"title":5,"description":266},"docs\u002Fwhy-better-than-scrum","yAOSJkVX343TuESUnf-tCxwNpXc0IxKNtZUGJTbcAsw",1778559261708]