Back to Basics
summary
Only about 30% of teams have a working agreement, and many lack a definition of ready or a definition of done. A team repeatedly drags a ticket through three sprints because required inputs aren’t defined, and QA marks “meets acceptance criteria” without reading them. The team convenes, writes concrete DoR/DoD and a social contract, stops pulling unready stories into sprints, and starts closing tickets that actually meet documented acceptance rather than guessing.
AI-written summary · about
related talks
33mThe Holy Grail in Scrum: The Done Increment
41mProduct Owner & Developer: An Unexpected Journey
32mBuild Teams as an Engineer
44mEnhancing the Performance of Engineering Teams
32mDefinition of Done
40mAgile Software Development: Practice and Analytics
17mRisks with Ticket Driven Software Testing
36mDEVELOPER ORIENTED PROJECT MANAGEMENT