How to Manage Dependencies on Agile Projects: Agile Mentors Podcast 85

On Episode 85 of the Agile Mentors Podcast, host Brian Milner welcomes Ken Rubin to talk about how to manage dependencies on agile projects. Inside this video, you'll discover:

00:00 Who is Ken Rubin?
02:07 What are project dependencies?
03:45 Two types of dependencies on agile projects.
05:25 Where most agile teams go wrong with managing dependencies.
08:01 Why dependencies aren't the same as blockers.
10:45 Why do agile teams care about the concept of flow?
14:15 How to balance system-level work in process with capacity.
16:30 Options to solve dependency problems (hint: Feature teams don't solve everything)
28:15 Debunking the myths surrounding dependencies

[scottf]

your sticky note example really points to the importance of incremental development as much as the value of feature teams and reducing dependencies. If, with 3 component teams, one team can't get their work done there's no chance a feature team, with only a fraction of the component team, would be able to get that same work done within the sprint. For example, if 3 individuals on the component team can't complete the work there's no chance a single individual, now on a Feature team, can complete it. Thus, breaking that functionality down so that we can incrementally complete a portion of what's required, in order to get feedback, is just as important as removing the dependency. If you move to Feature teams, and continue to insist on doing huge implementations it will still take you just as long.