{"id":4673,"date":"2024-05-04T17:17:47","date_gmt":"2024-05-04T15:17:47","guid":{"rendered":"https:\/\/p4dev.hardscrum.com\/?p=4673"},"modified":"2025-07-06T14:00:51","modified_gmt":"2025-07-06T12:00:51","slug":"tapir-decision-guideline","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/tapir-decision-guideline\/","title":{"rendered":"TAPIR Decision Guideline"},"content":{"rendered":"

The “TAPIR Decision Guideline” is an effective approach to find and make decisions in a group and to agree on them. The steps described here should be carried out by a moderator (e.g. a Servant Manager or Scrum Master) in the order described.<\/p>\n

T<\/span>riage & Time<\/strong>: A quick assessment about criticality and decision time. Questions: Regarding the time, how deep should the analysis be? Who, what and how much time is needed?<\/p>\n

A<\/span>nalysis<\/strong>: Depending on the available time for the analysis, the assigned “TAPIR Driver” should do an Analysis, resulting in a Problem Statement. Questiones: What is the problem? What are the needs of the different stakeholders? For example, the A3 method from Lean\/TQM\/Six Sigma can be used for this purpose. It is also important to consider who will be affected by the decision and who should work on it<\/p>\n

P<\/span>roposed Options<\/strong>: A list of options with an analysis of their pros & cons, cost & benefits or effort & business value. The presentation of the options can be done in different ways:<\/p>\n

    \n
  1. A simple list, for example with Effort & Business Value: The Effort can be discussed and estimeated by the Working Team<\/a> using Planning Poker<\/a>. The Business Value can be estimated by the Product Owner<\/a> (or the TPO Group<\/a>). The resulting priority can be visualized by the Upswing-Gravity-Field<\/a>.<\/li>\n
  2. A list with important attributes as a decision matrix (Pugh matrix)<\/a>. By first agreeing on the weighing factors of the different attributes, it is possible to split and slice the discussion.<\/li>\n
  3. Different options can be prepared using the NABC<\/a> method.<\/li>\n
  4. A Consent Decision Making process<\/a> where the TAPIR Driver introduces a proposal and the group discusses & resolves objections and lists concerns to be reviewed in the TAPIR Review step.<\/li>\n<\/ol>\n

    Decision<\/strong>: This is the formal step, where the deciding group agrees on one<\/span> Proposed Option as the solution. The group also agrees that everyone supports and sticks to the solution, at least until the TAPIR Review step. (aka Disagree & commit)<\/p>\n

    I<\/span>mplementation<\/strong>: In this step, the Proposed Option\/solution is implemented and used. It is crutial that everyone is disciplined to stick the the agreed solution. Every deviation should be made transparent.<\/p>\n

    R<\/span>eview<\/strong>: After a predefined period of time (usually an Iteration or Cycle) the group verifies and reviews the solution’s results, effectiveness, efficiency and how people behave and feel about it. Then, the group can make changes or agrees to make the solution permanent.<\/p>\n

    \n

    TAPIR is based on TDODAR<\/a> with extensions. One method for agreeing responsibilities between manager and team uses Delegation Poker<\/a> with a Delegation Matrix for visualisation. Team Collaboration Poker<\/a> is suitable for deciding responsibilities between two teams.<\/p>\n

    Anothe decising framework is the OODA loop<\/a> from John Boyd.<\/p>\n

    See also: Attributes of successful teams<\/a>. Home<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"The “TAPIR Decision Guideline” is an effective approach to find and make decisions in a group and to agree on them. The steps described here should be carried out by a moderator (e.g. a Servant Manager or Scrum Master) in the order described. Triage & Time: A quick assessment about criticality and decision time. Questions:…","protected":false},"author":3,"featured_media":4676,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[558],"tags":[],"translation":{"provider":"WPGlobus","version":"2.10.10","language":"en","enabled_languages":["de","en"],"languages":{"de":{"title":true,"content":true,"excerpt":false},"en":{"title":true,"content":true,"excerpt":false}}},"_links":{"self":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/4673"}],"collection":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/comments?post=4673"}],"version-history":[{"count":24,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/4673\/revisions"}],"predecessor-version":[{"id":4675,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/4673\/revisions\/4675"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/4676"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=4673"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=4673"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=4673"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}