Dependencies

DependenciesAlignmentStrategyStream TeamContinuous DesignContinuous DevelopmentProduct Teams
DependenciesDependencies
+1+1
The 4 Types of Team Dependencies That Kill Performance (and How to Spot Them)

The 4 Types of Team Dependencies That Kill Performance (and How to Spot Them)

Dependencies remove autonomy, which kills accountability. Once you have handoffs you allow people the wiggle room to throw up their hands and say "I did my job". We need to remove dependencies if we want teams to be accountable for outcomes - and that start with identifying the different types of dependencies that can exist.

Rory Madden
Rory Madden
DependenciesDependencies
+1+1
Why We Need a Brook's Law for Teams

Why We Need a Brook's Law for Teams

In 1975, Fred Brooks published "The Mythical Man-Month," introducing what became known as Brooks' Law: "Adding manpower to a late software project makes it later." Brooks observed that communication overhead grows much faster than productive capacity when you add people to complex projects.The same is true for adding more projects into a portfolio.

Rory Madden
Rory Madden
DependenciesDependencies
+1+1
Slow Product Development? Dependencies are the Cause

Slow Product Development? Dependencies are the Cause

Brooks' Law highlights the problem of the exponential increase in communication between team members as team size grows. We need a similar concept for dependencies between projects as the number of parallel projects grows.

Rory Madden
Rory Madden