Agile Team Structure

In the past, we’ve used component teams in development: teams of people that with generally the same skills. These teams are typically assigned a part of a project to work on.

Bringing these different teams together to create the final product can be a hassle and can result in unnecessary dependency management, overwhelming overhead, and a longer process.
Learn how to build Agile teams that are cross-functional and are optimized for outcome as opposed to output.

Follow Agile Velocity around the internet:

[bencoupland]

This was extremely helpful and explains the concept of agile in very clear and concise way. Thank you!

[markux]

@David Hawks Okay, so you manage to set up a cross-functional team that can cover UI + frontend + backend work.

Now, about the shopping database story example, should it be implemented by each one of the three team members? I think that's the case you are representing here (unless I misunderstood), however you will inevitably face a high degree of interdependency between the three of them, and eventually this will end up requiring a lot of daily micro management. What would your idea be to tackle this scenario?

Thanks for your time and congrats for your excellent videos!

[sandroinzerilli]

Hello. Interesting Video! Can I ask you Which instruments do you use to Paint while talking?(ex: a specific tablet connected to PC with USB port?)