Please help me understand the dependencies in Agile-cross functional Team.
This is a reference to the LinkedIn learning course by Chris Croft and Doug Rose, where both of them are discussing waterfall vs Agile.
One particular aspect of the video that's driving me crazy is that if a true Agile cross-functional team has people with generalised knowledge in different areas, all built together in one team, then there would be no internal dependencies within the team because each team focuses on the same sprint, technically evolving products with the help of their knowledge in their respective domains.
While Mr. Rose argues that Agile teams have problems with dependencies. I can come to think of him referring to non-structural, external dependencies, but then he goes on to say that organisational dependencies are a huge problem. I mean, how is that possible in a small true agile team in theory (in theory because I would like to understand the concept without any practical aspect to it first, and later adjust to the practical ways of the world).
(New student)