Dependencies: Can your agile teams handle them? and if not.. how
summary
Dependencies often hide as accepted facts and cost weeks: one case shows outsourced testing increases lead time by three weeks and another three-week sprint produces only a new DB table because the Definition of Done mandates external code review. Practical moves that work are concrete: measure waiting time with timestamps or Jira CFD, require SOAP UI proof of backend interfaces before frontend work, allocate a scarce expert for several sprints, adopt CI/TDD and shared code, or reorganize teams (parallel spin-out) to eliminate the dependency.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 3:30Is having a dependency a problem
- 9:25Examples of dependencies
- 12:40External dependencies
- 14:50Process dependencies
- 17:07Shared environment dependencies
- 18:26Impact of dependency
- 26:54Is it a problem
- 28:37How to treat dependencies
- 29:58Two extremes of dependency management
- 30:39Gatekeeper technique
- 33:37Scrum
- 35:11Measure and visualize
- 36:24Dynamic extended team
- 37:36Exclude legacy processes
- 39:07Common planning
- 40:13Shared code
- 41:13Elimination
- 42:37Redesign
- 44:23Code dependency
related talks
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
44mDependencies; Devil or Darling?
40mAgile Software Development: Practice and Analytics
01h 26mChaos Development: Removing Software as the Inhibitor of Agile
51mDon't Kill Agility with Agile Processes
36mYou Can't Be Agile If Your Testing Practices Suck
40mRegain Benefits from Agile Software Development
27mDependency hell - Or, Developers' perception of software dependencies