Are you investing enough to build cross-functional development team?

I do see people come to attend CSM (Certified Scrum Master) or CSPO (Certified Scrum Product Owner) training or many organizations ask us to facilitate in-house CSM and CSPO workshops. These 2 workshops are for Scrum Master and Product Owner and really needed in order to start practicing Scrum within organization. But what kind of workshop you are organizing for development team or what workshop you development team members are attending to gain knowledge related to development team's practices?

How you are helping to build a better cross-functional and self-organizing team? Hope you are not ignoring but are you having right workshops for them? What do you do for people working on Salesforce, Oracle ERP, Java Development, UX design, Database, .Net Development, Open Source Platform, Mainframe or Embedded Technologies either as Developer, Testers or Business Analyst?

I am raising this questions based on my interaction with development team while facilitating CSD ( Certified Scrum Developer) workshop for developers, testers and business analyst. What I usually hear that organization facilitates only Scrum Framework workshop and nothing specific to development team role. Some organizations also organize workshops on TDD, CI etc. but mainly tools training and not much focus on practices.

Since Scrum become a widely used framework for software development and majority of organizations already practicing Scrum or Scrum + Something so it has become vital to have your development team members go through role specific workshop to learn practices that can help them to be more efficient and effective.

Workshops should focus more on practices and importance of these practices rather than just tools. If they just go for junit, dbunit, jenkins or cucumber training then most likely teams will misuse these tools. Being a developer I understand one things that until I am not sure how these practices and tools useful for me, I will not use it. Maybe this is one the biggest reason that team ignore engineering practices and technical debts keeps increasing sprint by sprint.