Bus factor

Accident with a bus on a highway, an example of the scenario used for the bus factor

The bus factor (aka lottery factor,[1][2] truck factor,[3] or circus factor[4]) is a measurement of the risk resulting from information and capabilities not being shared among team members, derived from the phrase "in case they get hit by a bus".

The concept is similar to the much older idea of key person risk, but considers the consequences of losing key technical experts, versus financial or managerial executives (who are theoretically replaceable at an insurable cost). Personnel must be both key and irreplaceable to contribute to the bus factor; losing a replaceable or non-key person would not result in a bus-factor effect.

The term was first applied to software development, where a team member might create critical components by crafting code that performs well, but which also is unavailable to other team members, such as work that was undocumented, never shared, encrypted, obfuscated or not published. Thus a key component would be effectively lost as a direct consequence of the absence of that team member, making the member key. If this component was key to the project's advancement, the project would stall.

  1. ^ Adler, Adler (April 4, 2023). "Reducing the Lottery Factor, for Data Teams". Locally Optimistic. Archived from the original on April 4, 2023. Retrieved December 10, 2024.
  2. ^ Marques, Joao (July 15, 2024). "How to Avoid the Lottery Factor". DEV Community. Archived from the original on December 10, 2024. Retrieved December 10, 2024.
  3. ^ Bowler, Michael (May 15, 2005). "Truck Factor". Agile Advice. Archived from the original on April 29, 2021. Retrieved April 9, 2014.
  4. ^ Bernard, Mercedes. "RubyConf 2021 - Minimize Your Circus Factor: Building resilient teams by Mercedes Bernard". devconf.net. Retrieved 8 October 2024.

© MMXXIII Rich X Search. We shall prevail. All rights reserved. Rich X Search