Context Switching - so you think this is a good thing?

Last post we talked about Agile Clowns multi-tasking and that research has shown that we can't actually multi-task except for repetitive, memorized types of activities. You can't truly multi-task (do 2 or more things at one time) for cognitive activities. Since we can't multi-task, the real issue is context switching. How many projects are you working concurrently? Are you dedicated to one project? Great. Keep it up. Do you have 2 or more projects? 3 or more? Then you're not going to be very efficient.

Agile Clowns or "How to be a great multi-tasker"

What phrase did I see on your resume? Oh yeah: "great multi-tasker." That's awesome! You pride yourself on delivering more in less time by juggling several projects at the same time. It's a badge of honor and you wear it proudly.

Sorry to break it to you, but a clown is better at multi-tasking than you are. If a clown can do it, you must be able to do it just as good, even better.  The question is, are you sure about that?

Multi-tasking - is it really this bad everywhere?

Multitasking is killing many of the projects I'm currently coaching. Team members literally have 3, 4 or even as many as 5 projects going at once. Teams are formed with multiple members, each on multiple projects. In almost every case, where there's heavy multi-tasking the teams choose to have their daily standup two times per week. Catch that - daily standup, only twice per week...