Lately I've been seeing the classic skill matrix used more and more in companies in order to create teams and identify knowledge gaps. The tool is excellent for that, but recently I've come across a few modifications of the technique that make it so much more powerful, and to my surprise it was hard to find detailed information about these modifications online. Hence this blogpost.

The classic skill matrix and forming a team

The classic skill matrix works like this: 

The issue: knowledge sharing & alignment

It is frequently seen that even though people are working on the same delivery there still is misalignment on the way of working, with what degree of finish (D.O.D. interpretations), etc. 
This especially happens with different skills and contexts that imply different perspectives on how to look at software.
Either way you place it: knowledge sharing is lacking. 

Stage

Backlog Refinement session. 

Purpose 

Our Product Owner came up with new stories to be estimated. 14 to be precise. 
It required some preparation however.  We have 2 teams, and they do the Backlog Refinement together. 
Around 20 people in one room, partly offshore, estimating together is quite a challenge!