Bus factor
The bus factor 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". It is also known as the bus problem, truck factor,[1] or bus/truck number.[citation needed]
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.
Definition
The "bus factor" is the minimum number of team members that have to suddenly disappear from a project before the project stalls due to lack of knowledgeable or competent personnel.
The expression "hit by a bus" describes a person either dying or more generally disappearing suddenly from the project. It is used to describe hypothetical future disappearances in a darkly humorous way. Team members do not literally have to get "hit by a bus" for the "bus factor" to apply—any number of events could occur in which a team member could be suddenly and substantially prevented from working on the project. This could include a person taking a new job, going on parental leave, or changing lifestyle or life status.
For instance, say a team of 30 people produces bread in three necessary steps: mixing ingredients, kneading the dough, and baking. Ten people know how to mix ingredients, all 30 people know how to knead the dough, and 5 people know how to bake. If all 5 people who know how to bake disappear, then the team cannot produce bread, so the team's bus factor is 5.
There is a rare alternative definition for the bus factor, namely: the number of people who are indispensable for the project.[2] In other words, it is the minimum number of people who are a single point of failure. If using this definition, then a high bus factor is considered a bad thing (since the loss of any person included destroys the project), and zero is considered the ideal bus factor.
History
An early instance of this sort of query was when Michael McLay publicly asked, in 1994, what would happen to the Python language if Guido van Rossum were to be hit by a bus.[3]
"Truck number" was already a recurring concept in the Organizational Patterns book published in 2004,[4] itself an evolution of the work published in the first book of the Pattern Languages of Program Design series in 1995,[5] which was the publication record of the first Pattern Languages of Programs conference in August 1994, where it was referenced in patterns including Solo Virtuoso.[6] The term was used[clarification needed] in mental health in 1998.[7] It was seen in engineering by 2003,[8] and the Debian project in 2005.[9]
Studies conducted in 2015 and 2016 calculated the bus/truck factor of 133 popular GitHub projects. The results show that most of the systems have a small bus factor (65% have bus factor ≤ 2) and the value is greater than 10 for less than 10% of the systems.[10][11]
The term is mostly used in business management, and especially in the field of software development.[citation needed]
Improving the bus factor
In many software development projects, one goal is to share information in order to improve the bus factor, potentially to the size of the entire team. A good bus factor means many individuals know enough to carry on and the project could still succeed even in very adverse events.[12]
Several ways to improve the bus factor have been proposed:
- Reduce complexity,[13]
- Document all processes and keep that documentation up-to-date,[13]
- Encourage cross-training.[13]
See also
References
- ↑ Bowler, Michael (May 15, 2005). "Truck Factor". Agile Advice. http://www.agileadvice.com/2005/05/15/agilemanagement/truck-factor/.
- ↑ Coplien, James; Harrison, Neil (2004-07-26). Organizational patterns of agile software development. Wiley.
- ↑ McLay, Michael (June 29, 1994). "If Guido was hit by a bus?" (Mailing list).
- ↑ Coplien, James; Harrison, Neil (July 26, 2004). Organizational patterns of agile software development. Wiley.
- ↑ Coplien, James; Schmidt, Douglas (May 12, 1995). "Chapter 13, A Generative Development-Process Pattern Language". Pattern Languages of Program Design. Addison Wesley. Bibcode: 1995plpd.book.....V.
- ↑ Coplien, James (August 4, 1994), "A Generative Development-Process Pattern Language", Internal proceedings of PLoP 1994, Allerton Park, Illinois: unpublished., https://sites.google.com/a/gertrudandcope.com/info/Publications/Patterns/Process/PLoPD1/section4, retrieved September 12, 2014
- ↑ Simon, Robert (May 17, 1998). The Mental Health Practitioner and the Law: A Comprehensive Handbook. Harvard University Press. p. 69. ISBN 0-674-69721-9.
- ↑ Redmond, Matthew C.; Newton, Paul (2003). "Integrating GIS in the Engineering, Planning and Design Processes". http://proceedings.esri.com/library/userconf/proc03/p0559.pdf.
- ↑ Reinholdtsen, Petter (November 11, 2005). "Re: Resignation and uploads" (Mailing list).
- ↑ Avelino, Guilherme; Valente, Marco Tulio; Hora, Andre (September 10, 2015). "What is the Truck Factor of popular GitHub applications? A first assessment.". PeerJ Preprints. doi:10.7287/peerj.preprints.1233v3. https://peerj.com/preprints/1233/. Retrieved December 4, 2015.
- ↑ Avelino, Guilherme; Passos, Leonardo; Hora, Andre; Valente, Marco Tulio (2016). "A novel approach for estimating Truck Factors". 2016 IEEE 24th International Conference on Program Comprehension (ICPC). pp. 1–10. doi:10.1109/ICPC.2016.7503718. ISBN 978-1-5090-1428-6. Bibcode: 2016arXiv160406766A.
- ↑ James Coplien, Pair Programming Illuminated. Quote: "How many or few would have to be hit by a truck (or quit) before the project is incapacitated?"
- ↑ 13.0 13.1 13.2 "Increasing your team's bus factor". 2008-09-03. https://eight2late.wordpress.com/2008/09/03/increasing-your-teams-bus-factor/.
Further reading
- Michele Marchesi, Giancarlo Succi, Don Wells, James Donovan Wells, Laurie Williams (2003). Extreme Programming Perspectives. Boston u. a.: Addison-Wesley. ISBN 0-201-77005-9.
- Laurie Williams, Robert Kessler (2002). Pair Programming Illuminated. Boston u. a.: Addison-Wesley. ISBN 0-201-74576-3. https://archive.org/details/pairprogrammingi0000will.
- Kent Beck (2000) (in de). Extreme Programming. Das Manifest. s. l.: Addison-Wesley. ISBN 3-8273-2139-5.
External links
- Poisonous People, a talk that includes (among other topics) discussion of bus factor and how to increase it
- "What If Linus Torvalds Gets Hit by a Bus?" - An Empirical Study, a humour piece
 |  |
