How to transition from Component Team to Feature Team?
When a Development Team decides to transform itself from a component-based team to a feature-based team, it is generally not an easy journey. Depending on the context of the organization, it can be quite painful in some cases to fully transition to feature-based teams.
In this piece, I take inspiration from the Scrum Values to describe 5 things to keep in mind while transitioning from being a Component Team to becoming a Feature Team.
1. Courage
It surely takes courage to embark upon, and sustain this journey — for Development Team members as well as for the organization. Example, if a team has always worked on back-end components using Java, they will need some degree of courage to learn ReactJS from scratch and start making changes to front-end components. From being a superstar in one technology, to becoming a beginner writing “Hello World” in another technology, is definitely not easy.
The fear of breaking the code in a new component, and the inertia to work away from the comfort-zone, can limit the team’s ability to learn new things and expanding the skill-sets. The team needs courage to overcome this fear and inertia. Of course, they have to act responsibly while doing so.
