Who Is Chapter Lead
Who Is Chapter Lead
The Chapter is your small family of people having similar skills and working within the same general
competency area, within the same tribe. Chapter Lead, it is a role rather than a position. The chapter
lead is the line manager for the chapter members, responsible for developing people and the things
happening in the chapter but still is a member of the squad and does day-to-day work.
— Peter Drucker
Well, in agile you don’t have traditional teams headed up by a manager. Teams consist of various roles
working together on projects. Squads. They define their own goals independently and decide how to
reach them. A number of squads make up a tribe. As for a Chapter Lead, one must support people
within a tribe but in different squads, who are in the same role.
Because the chapters are responsible for hiring they must deploy talented people to the appropriate
squads, based on their expertise and demonstrated competence, but once the talent joins the squad,
chapters can not tell them how to set priorities, what to do within the squads, how to assign a task or
how to spend a day.
Each chapter is responsible for: developing talent — guiding along their career paths; evaluating and
promoting people; and building common tools shared by squads, standardize developer culture and
ways of working. Chapter synchronization meetings take place once a week or bi-weekly.
With me so far?
8. Agile Is Chaos.
Not at all! Agile means a lot less hierarchy than in the past, which means you can change tack faster
and work more effectively. That is much better. I don’t understand how some companies are still able
to work in the traditional way. After the switch, it does take a while for it to really become a way of life.
The role of a Chapter Lead is very important in making that transition.
Besides being a member of the squad which includes standups, meetings, and tasks, here are some
other responsibilities as a chapter lead.
Communication — You are going to spend a good part of your working day in meetings. One-on-
one meetings with chapter members, retrospective (retros), POCLACs(Product Owner +Chapter
Lead + Agile Coach), chapter sync meetings, sync with other chapter leads and everyone who
needs the help of competent opinion from your field.
Growth — You should care for everyone and their career growth. Not only salary or growth in the
field but assign them to the appropriate squad where they can find the balance and display the
strength.
Activation — You will be the one who leads chapter members to their desired growth step; you
will be the one who activates their skills, helps them to perform better, learn and reach new
heights.
Hiring — You are going to need developers, lots of them. You should convince them to work for
squads and for your organization. It means you should be joining conferences, attending meetups
(in a non-covid world), and other activities to get to know the community and blend in.
Sometimes you can attract talents who know you and want to work with you.
Less Testing — You will significantly Test less, because of all the other responsibilities you will
have. The main objective becomes to find several consecutive hours to focus solely on the tasks
because of an overwhelming amount of context switching you will have during the day. And I
think it’s ok because you contribute to the project and organization in a different way. But also it
means you should study hard to keep your tech skills sharp because as a chapter lead you have to
stay sharp and know the field very well.
Is it worth it?
It depends on the person. I see people growing, happy and dedicated. You have a different measure to
scale the success, you help others to do their job better, you contribute to the organization to build
better products. Being the chapter lead is a great place to hone your soft skills.