A question I've gotten a fair amount over the past year or so has been:Where are [Value Streams | Epics | Teams] in the TBM Taxonomy?If you're not familiar with Value Streams or Epics (or Agile Teams), I suggest reading their definitions here: https://www.scaledagileframework.com/glossary/ A deeper dive into Value Streams can be found here: https://www.scaledagileframework.com/value-streams/In our Standards process in 2020, the Standards Committee discussed including these elements in the TBM Taxonomy v4.0. In the end, the committee concluded that value streams, epics, projects, etc., are the "how" of developing apps, products or services (what we call Solutions) and therefore they were not included in the Taxonomy itself.Of course, these objects are used in TBM cost models and reporting. But there have always been TBM data sources with objects that are not shown in the Taxonomy. For example, we've never had "Projects" in the Taxonomy, but we know that Project data is used in many (if not most) TBM models and that TBM models are often used to cost projects themselves. Project costs are comprised of Tower/Subtower resources (e.g., Application Development, Servers, Online Storage, Database, Middleware, etc.). But Projects are usually a development bucket, basically; projects are not the Application, Service or Product that ultimately delivers value to the business.SAFe seems to take a similar tack with their definition of Value Streams:"Value Streams represent the series of steps that an organization uses to implement Solutions that provide a continuous flow of value to a customer." © Scaled Agile, Inc.So, the committee's consensus was that Value Streams, Epics, Projects, etc., did not meet the criteria we've used to define what appears in the taxonomy.With 4.0, we refined the Products & Services layer to "Solutions", which includes Applications, Products and Services. Solutions is the term Scaled Agile uses to refer to these things more generally, with the primary object in Agile being Products (the whole "Projects to Products" shift), and we felt this was a good term to use to allow flexibility for what appears in that layer. And we also introduced the Solution Classes to call out Applications, Products, and Services.I'd like to know what you think. How do you use Value Streams, etc. in your TBM reporting? Are you funding (budgeting) by Value Streams, etc.? Do you think we should have included Value Streams or Epics or Projects or Teams in the standard taxonomy and why?
About Us11100 NE 8th St. Suite 600Bellevue, WA98004info@tbmcouncil.org
Join CommunityWhat is TBM?Community Newsletters