Need for matured developers in Agile Teams – A Myth
The Agile Zone is brought to you in partnership with JetBrains. Learn how Agile Boards in YouTrack are designed to help teams plan, visualize and manage their work in an efficient manner, with support for both Scrum and Kanban processes.
I have heard many times from in-experienced scrum coaches saying Agile projects need matured team members.
The Big myth
The above statement is as big a myth as the one which says Agile projects follow no documentation
The answers I got…
I had asked one of those in-experienced scrum coaches the following questions,
What do you mean by Matured team members ?
Why do you think Agile projects need more matured team members ?
The answers surprised me a lot, the answers were
Matured team means, a team with more experienced people
The reason we need matured teams is because, concepts like self organizing teams and self managing teams are easily understood and implemented by experienced developers as compared to juniors.
They also say that the junior developers mis-use the freedom and trust shown in Agile projects and so, they are not suitable !!
Does maturity comes with Age ?
My view is, maturity to a person does not come with age or more experience at work. Secondly, concepts like self organizing and self managing teams need the fundamental value, trust to succeed than any software development skill or experience.
I strongly believe that, individual team members shouldn’t be blamed. This is because, the culture followed within the team is strongly influenced by the person leading the team.
According to the greatest thinker, Peter Senge,
We must look beyond individual mistakes or bad luck to understand important problems. We must look at the underlying structures which shape individual actions and create the conditions where types of events become likely
So, if a junior team member is not doing his/her assigned job, instead of blaming him/her, we should look at the system which is driving this character within them.
Success of Agile projects does not depend on the experiences of the team members but on the fundamental value driving the system.