TFS is not a Framework

TFS is NOT a framework, and this is why it does not have prescribed roles and methods.

• TFS is not a framework or a methodology or a prescriptive one size fits all approach. We are elucidating the issues in complex problems (not Scrum pretend complexity) and that the key differentiator is the focus on human factors through team science (teamwork).

It is a system of learning and understanding that provides guidance and knowledge that enables you to operate in any context. It elaborates the interconnected nature of the areas of science that we believe is necessary to be successful, the Triple Helix. It does not abandon 8 decades of lean thinking, but recognizes lean is not enough.

Team types are contextual and just like the word Kanban have been distorted to mean what the purveyor of hope wants them to mean. I know your frustration and in the context you work in it is fine to make that distinction and to talk about the challenges with component teams. Focusing on Flow enables you to design organizations that enable the flow of value, and to avoid naming team types (I wrote about this recently on LinkedIn) and instead focus on creating optimal value streams.