[#ALM] Do you really need roles in a team? (usually not)

Hello!

Today I’m going to avoid the intro and some context and I’ll go directly to the question:

Are necessary roles in an Agile team ?

The answer is simple: Yes. But they are not roles that usually people know, there are only 2 roles in a single Agile Team

Some people with a problem
An Agile Team with the ability to provide a solution to this problem

And that’s all. The 1st role is usually known as a client or customer, and is defining the problems or needs that will work the 2nd team. The 2nd team is where lives the usual roles, best-known as front end developer, backend roles developer, analyst, etc.

The important thing in an agile team is that members should be flexible enough to cover any position. Since the ZERO day, the team should be able to to add value. This does not remove the need for some specialist, in example: a tuning of a databases. This should be be dictated by the evolution of the solution, and if the architecture is emerging from the team, there will not be a problem. (remember discarded classical architects! ))

And I’ll close with a tip: The next time that you start an agile team, don’t consider the specific capacities of the people in relation to what they can do, but rather keep in mind the capacity that they have to adapt to what comes up. Remember that the only constant in a team change and:

Agile customers knows that a product can always improve, and also knows that they are responsible for the changes introduced in the product

Analysts knows that a solution is never complete, the context and the problems tend to change and they must adapt the analysis models as these changes are discovered

The developers know that we will never write perfect code, so that we refactor the code, we base our code on tests and change the code again and again to improve it

Happy Teaming Open-mouthed smile !!!