Identifying Dependencies

There are different ways to approach Dependency Poker, and in this article, we will explore three different options.

Option 1: Turn the cards one by one and discuss them

In this option, all cards with the information hidden are put on the backlog item. The team then randomly selects one card and turns it over. The team then discusses the card and tries to identify any dependencies that may exist. The team members can ask questions and share their insights, based on their knowledge and experience. The discussion can be open-ended or guided by a facilitator.

This option is useful because it allows the team to focus on one card at a time, and ensures that each card is thoroughly discussed. However, it can be time-consuming if the team has a lot of cards to go through.

Option 2: Identify dependencies to remove

In this option, all cards are put on the backlog item and the team is asked to identify which cards/dependencies can be removed. If all team members agree, the card is removed from the backlog item.

This option is useful because it helps the team to focus on the most critical dependencies and remove any unnecessary ones. However, it may not be effective if the team members have different opinions about which dependencies are critical and which are not.

Option 3: Dependency Storming

In this option, the team members throw identified dependencies on the backlog item. Each member shares their insights and experience to identify potential dependencies, and the team discusses each one. This option works best with mature teams who are familiar with the project and have experience with dependency identification.

Option 4: The Delphi Method

This option is a variation of the Dependency Poker game that adds an element of secrecy and individual decision-making. In this approach, each team member is given a set of cards, but instead of discussing them openly with the team, they choose their preferred cards in secret.

The team then sets a timebox, after which each team member reveals the dependencies they have chosen. The team then compares the chosen dependencies, and any duplicates or dependencies that are commonly chosen are discussed further.