There is a trend on the IT market to be software developer who has expertise in one specific technology (vertical line in “T”) and knows others at levels that don’t stop him from understanding a full code (horizontal line in “T”). This whole idea seems to help building cross-functional team, one of core thing in Agile world.
Currently the team that I’m working with has decided to try to become T-Shape one. There have been a few discussions how to tackle it, what should be assumptions and how we can manage dependencies. We have used brainstorming session to create a plan that all of us would support. Here is our approach:
- Create skill matrix to get knowledge what kind of expertise team has.
- Identify skills that should be strengthened.
- Verify in which directions team member would like to develop.
- Each team member proposes plan of skill’s development with clearly stated goals.
- Scrum Master facilitates and challenges progress on skills’ learning plan on monthly basis.
On top of this, the whole team has agreed that during transformation into T-Shape developer we still need to follow principles mentioned as below:
- Each team member has main focus on core skill/-s.
- We will plan how to grow individual horizontal skills during sprint planning so we could forecast more accurate sprint deliverable.
- Each team member is responsible for his/her skill’s development.
- Each team member seeks actively new ways of skills’ learning.
As you can see the team has decided to move closer to be cross-functional team in structured way, doing it step by step. Such approach gives them a chance to adjust it if needed and to validate their progress (see points 4. & 5.). Additionally it should help minimizing an influence on sprint deliverables. Keep finger crossed!
If you have any experience in creating T-Shape team let me know. I’m curious to find out how you have transitioned to it and I’m open for your advice!