Cross Functionality in feature teams and component teams

If a component team was "cross-functional", wouldn't that mean they have all of the capabilities needed to deliver "feature-complete" work?

Hi Ian, you are exactly right. But I try to understand the necessity of the component teams. Do we have to support component teams also, or support feature teams? So many organizations use component team in agile environment. I think we have to focus on " complete feature" that scrum team provides.

Cross-Functionality just means you have all the skills required on a team to build a product increment. It doesn't matter at all what that product is, be it feature, component, or otherwise. 

So many organizations use component team in agile environment. I think we have to focus on " complete feature" that scrum team provides.

Does a scrum team provide a complete feature though? That is fully dependent upon the product. Personally, I don't see a problem in having Component and Feature teams, if you move to have a single team do both; that can make the team too large or cause a lack of focus. Scrum itself does not prescribe the use of component or feature teams, it just says have a cross-functional team build a product increment. Find what works best for the customers, company, product, and team and as long as you're living within the boundaries of the framework; you're doing it right.