Often, business want to start more projects than they can handle. It can be hard in those environments to explain to business people, that by multi tasking, the output of the development organisation, will be reduced.

@michelgrootjans did a great job explaining this effect through simulation:

https://youtu.be/bhpQKA9XYcE

#Flow
#WIP
#LittlesLaw

Explaining team flow

YouTube

@djswagerman @michelgrootjans Good one.

Yet still a vast oversimplification, that may lead to false conclusions.

Like this: Making every teammember 'fullstack' actually means, illiminating all dependencies. This is hardly possible in reality.

Also, mental capacity is somewhat limited. Going broad in skills may lead to a lack of depth.

Additional variability is likely to be introduced into the process, which has to be coped with and violate Little's Laws assumptions.

@bbak @michelgrootjans yes, would be interesting to further model this trade of. There is a limit to reducing handover time. There’s a limit to reducing waiting time. There is also a limit to the speed in which a person can learn another domain or skill

Modelling the time to learn new skills follows similar math as thermodynamics substituting knowledge for heat.

The limit for handover time may also be guided by these laws

What would be your approach for a better model?

@djswagerman @michelgrootjans Model different sizes of work items, uncertainty about their size, and changing priorities. 😁