Context-Driven Practices
summary
Claims that rigid “best practices” cause harm and that 90% of sprints miss goals under enforced scrum rules, backed by a project example where allowing cross-sprint work and team-owned priorities produces higher quality. Specific shifts: give teams permission to move stories, choose tools that fit current constraints, and deliberately ship multiple MVPs delivered periodically while keeping small iterative changes. Concrete outcome: creativity returns, team morale rises and the project consistently ships value rather than features, a practical context-driven practices recipe.
AI-written summary · about
related talks
33mEffective Agile Processes: It’s All About People
45mPeople, Process, & Patterns
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
59mFrom Ok-ish to Outstanding: How any team can become a high-performing one
57mFocus. Deliver. Learn. Repeat
36mContext-driven Agile Tester
01h 10mAgile Cross Team Collaboration How Tos
46mWhat is Context-Driven Testing?