Flux Teams

The One Rule (1R) Team

The 1R team is responsible for the execution of a single item at a time until it is done adhering to the 1R rule. As a minimum, a 1R team should have these 2 core specialised roles –

  1. Delivery Expert
  2. Technical Expert

1R team cannot choose a specific Product team to work with. The roles are recommended to be attached to a dedicated individual at all times to focus on what they do best.

Delivery expert is a problem solver and guardian of the One Rule, who has low or no technical knowledge. If they are from a technical background they must `unlearn` to play this role. This role is a “process” expert who exist to keep the communication around product delivery as transparent as possible within the bubble and outside the bubble. This role should not be shared and is strictly focused on bubble’s goal and delivery plan. This individual is the glue which holds the Product team and 1R team together, while they are in a bubble.

Technical expert, as the name suggest they can be a developer, a tester or the UX persona for example. There are no restrictions on how many Technical experts can be on a 1R team.

Flux demands respect for the specialised skills; not to “force” them to become cross skilled because the One Rule makes sure it is not a dependency.

Technical experts are expected to share knowledge of newly learned techniques to other 1R teams. They can have a T-skill like an Architecture expert or DevOps expert to help the 1R team to stay in the context, explore & experiment new technologies while working around a specific work item.

A typical workflow in a 1R team looks like – Open > Blocked > In Progress > Done – as the members will only work on one item at a time and don’t have the choice to commit to another item on the backlog.

The Product Team

Product team decides which 1R team is suitable for their backlog and hence decides who they form the bubble with. As the name suggests the role is purely focused on business needs and goes all in from market research to inception to consumer delivery as well as consumer acceptance by product success analysis.

Product Team is a permanent team which is not bound by the 1R rule and can work in multiple items at one time.

As a minimum, a Product team should have these 2 core specialised roles –

  1. Product Expert
  2. Analysis Expert

The roles are recommended to be attached to a dedicated individual at all times to focus on what they do best. Product Expert is a typical business representative who is responsible to drive the success of a product from it’s inception.

Product team cannot have multiple Product Experts and only this role is allowed to add items in the backlog. While in a bubble the Product Expert is the glue between the 1R and Product team, just like the Delivery Expert in 1R team. Delivery Expert and Product Expert will drive a common goal – successful product delivery. A Product Expert can own multiple MVPs but can only use one bubble per MVP for implementation. Hence they can be shared between different bubbles at the same time.

Analysis expert will be responsible to provide valuable analytics data to the Product Expert even if they are not part of the bubble. Product team can have multiple Analysis experts and they responsible to capture, analyse and support the 1R teams for design decisions while development which affects consumer satisfaction.

Analysis expert can influence the addition/removal of backlog items by providing research outcomes but cannot add/remove items themselves. They can work on multiple MVPs on multiple bubbles. Hence they can be shared between different bubbles at the same time.