https://eight2late.wordpress.com/2010/03/11/bayes-theorem-for-project-managers/ Eight to Late Sensemaking and Analytics for Organizations Bayes Theorem for project managers with 10 comments Introduction Projects are fraught with uncertainty, so it is no surprise that the language and tools of probability are making their way into project management practice. A good example of this is the use of Monte Carlo methods to estimate project variables. Such tools enable the project manager to present estimates in terms of probabilities (e.g. there's a 90% chance that a project will finish on time) rather than illusory certainties. Now, it often happens that we want to find the probability of an event occurring given that another event has occurred. For example, one might want to find the probability that a project will finish on time given that a major scope change has already occurred. Such conditional probabilities, as they are referred to in statistics, can be evaluated using Bayes Theorem. This post is a discussion of Bayes Theorem using an example from project management. Bayes theorem by example All project managers want to know whether the projects they're working on will finish on time. So, as our example, we'll assume that a project manager asks the question: what's the probability that my project will finish on time? There are only two possibilties here: either the project finishes on (or before) time or it doesn't. Let's express this formally. Denoting the event the project finishes on (or before) time by T, the event the project does not finish on (or before) time by \tilde T and the probabilities of the two by P(T) and P(\tilde T) respectively, we have: P(T)+P(\tilde T) = 1......(1), Equation (1) is simply a statement of the fact that the sum of the probabilities of all possible outcomes must equal 1. Fig 1. is a pictorial representation of the two events and how they relate to the entire universe of projects done by the organisation our project manager works in. The rectangular areas A and B represent the on time and not on time projects, and the sum of the two areas, A+B, represents all projects that have been carried out by the organisation. [bayes-fig-] Fig 1: On Time and Not on Time projects In terms of areas, the probabilities quoted above can be expressed as: P(T) = \displaystyle \frac{A}{A+B} ......(2), and P(\tilde T) = \displaystyle \frac{B}{A+B} ......(3). This also makes explicit the fact that the sum of the two probabilities must add up to one. Now, there are several variables that can affect project completion time. Let's look at just one of them: scope change. Let's denote the event "there is a major change of scope" by C and the complementary event (that there is no major change of scope) by \tilde C. Again, since the two possibilities cover the entire spectrum of outcomes, we have: P(C)+P(\tilde C) = 1 ......(4). Fig 2. is a pictorial representation of by C and \tilde C. [bayes-fig-] Fig 2: "Major Change" and "No Major Change" projects The rectangular areas D and E represent the projects that have undergone major scope changes and those that haven't respectively. P(C) = \displaystyle \frac{D}{D+E} ......(5), and P(\tilde C) = \displaystyle \frac{E}{D+E} ......(6). Clearly we also have A+B=D+E since the number of projects completed is a fixed number, regardless of how it is arrived at. Now things get interesting. One could ask the question: What is the probability of finishing on time given that there has been a major scope change? This is a conditional probability because it represents the likelihood that something will happen (on-time completion) on the condition that something else has already happened (scope change). As a first step to answering the question posed in the previous paragraph, let's combine the two events graphically. Fig 3 is a combination of Figs 1 and 2. It shows four possible events: 1. On Time with Major Change (T, C) - denoted by the rectangular area AD in Fig 3. 2. On Time with No Major Change (T, \tilde C) - denoted by the rectangular area AE in Fig 3. 3. Not On Time with Major Change (\tilde T, C) - denoted by the rectangular area BD in Fig 3. 4. Not On Time with No Major Change (\tilde T, $\tilde latex C$) - denoted by the rectangular area BE in Fig 3. [bayes-fig-] Fig 3: Combination of events shown in Figs 1 and 2 We're interested in the probability that the project finishes on time given that it has suffered a major change in scope. In the notation of conditional probability, this is denoted by P(T|C). In terms of areas, this can be expressed as P(T|C) = \displaystyle \frac{AD}{AD+BD} = \frac{AD}{D}......(7) , since D (or equivalently AD+BD) represent all projects that have undergone a major scope change. Similarly, the conditional probability that a project has undergone a major change given that it has come in on time, P(C|T), can be written as: P(C|T) =\displaystyle \frac{AD}{AD+AE} = \frac{AD}{A}......(8) , since AD+AE=A. Now, what I'm about to do next may seem like pointless algebraic jugglery, but bear with me... Consider the ratio of the area AD to the big outer rectangle (whose area is A+B) . This ratio can be expressed as follows: \displaystyle\frac{AD}{A+B}=\frac{AD}{D}\times\frac{D}{A+B}=\frac{AD} {A}\times\frac{A}{A+B}......(9). This is simply multiplying and dividing by the same factor (D in the second expression and A in the third. Written in the notation of conditional probabilities, the second and third expressions in (9) are: P(T|C)*P(C)=P(C|T)*P(T)......(10), which is Bayes theorem. From the above discussion, it should be clear that Bayes theorem follows from the definition of conditional probability. We can rewrite Bayes theorem in several equivalent ways: P(T|C)=\displaystyle\frac{P(C|T)*P(T)}{P(C)}......(11), or P(T|C)=\displaystyle\frac{P(C|T)P(T)}{ P(C|T)P(T)+P(C|\tilde T)P(\ tilde T)}......(12), where the denominator in (12) follows from the fact that a project that undergoes a major change will either be on time or will not be on time (there is no other possibility). A numerical example To complete the discussion, let's look at a numerical example. Assume our project manager has historical data on projects that have been carried out within the organisation. On analyzing the data, the PM finds that 60% of all projects finished on time. This implies: P(T) = 0.6......(13), and P(T) = 0.4......(13), Let us assume that our organisation also tracks major changes made to projects in progress. Say 50% of all historical projects are found to have major changes. This implies: P(C) = 0.5......(15). Finally, let us assume that our project manager has access to detailed data on successful projects, and that an analysis of this data shows that 30% on time projects have undergone at least one major scope change. This gives: P(C|T) = 0.3......(16). Equations (13) through (16) give us the numbers we need to calculated P(T|C) using Bayes Theorem. Plugging the numbers in equation (11), we get: P(T|C)=\displaystyle\frac{0.3*0.6}{0.5}=0 .36 ......(16) So, in this organisation, if a project undergoes a major change then there's a 36% probability that it will finish on time. Compare this to the 60% (unconditional) probability of finishing on time. Bayes theorem enables the project manager to quantify the impact of change in scope on project completion time, providing the relevant historical data is available. The italicised bit in the previous sentence is important; I'll have more to say about it in the concluding section. In closing this section I should emphasise that although my discussion of Bayes theorem is couched in terms of project completion times and scope changes, the arguments used are general. Bayes theorem holds for any pair of events. Concluding remarks It should be clear that the probability calculated in the previous section is an extrapolation based on past experience. In this sense, Bayes Theorem is a formal statement of the belief that one can predict the future based on past events. This goes beyond probability theory; it is an assumption that underlies much of science. It is important to emphasise that the prediction is based on enumeration, not analysis: it is solely based on ratios of the number of projects in one category versus the other; there is no attempt at finding a causal connection between the events of interest. In other words, Bayes theorem suggests there is a correlation between major changes in scope and delays, but it does not tell us why. The latter question can be answered only via a detailed study which might culminate in a theory that explains the causal connection between changes in scope and completion times. It is also important to emphasise that data used in calculations should be based on events that akin to the one at hand. In the case of the example, I have assumed that historical data is for projects that resemble the one the project manager is working on. This assumption must be validated because there could be situations in which a major change in scope actually reduces completion time (when the project is "scoped-down", for instance). In such cases, one would need to ensure that the numbers that go into Bayes theorem are based on historical data for "scoped-down" projects only. To sum up: Bayes theorem expresses a fundamental relationship between conditional probabilities of two events. Its main utility is that it enables us to make probabilistic predictions based on past events; something that a project manager needs to do quite often. In this post I've attempted to provide a straightforward explanation of Bayes theorem - how it comes about and what its good for. I hope I've succeeded in doing so. But if you've found my explanation confusing, I can do no better than to direct you to a couple of excellent references. Recommended Reading 1. An Intuitive (and short) explanation of Bayes Theorem - this is an excellent and concise explanation by Kalid Azad of Better Explained. 2. An intuitive explanation of Bayes Theorem - this article by Eliezer Yudkowsky is the best explanation of Bayes theorem I've come across. However, it is very long, even by my verbose standards! Rate this: Share this: * Share * * Print * Like this: Like Loading... Related Written by K March 11, 2010 at 10:17 pm Posted in Estimation, Probability, Project Management, Risk analysis, Statistics << Conflicts over identity: on the relationship between software developers and project managers Trumped by conditionality: why many posts on this blog are not interesting >> 10 Responses Subscribe to comments with RSS. 1. Bayes can only be applied if you have references to the past rigth? In my organisation the required data is not collected But never the less: this is a good artikel. Marc LikeLike [a25] MarcS March 14, 2010 at 6:30 pm Reply 2. Marc, Thanks for the feedback. You are absolutely right...and you're not alone in not having the required data Regards, Kailash. LikeLike [fc3] K March 14, 2010 at 6:36 pm Reply 3. [...] probability and Bayes Theorem. Those unfamiliar with these may want to have a look at my post on Bayes theorem before proceeding [...] LikeLike Trumped by conditionality - why many posts on this blog are not interesting << Eight to Late March 17, 2010 at 10:43 pm Reply 4. Hi K, I was reading about Event Chain Methodology. Is it similar to Bayes Theorem ? LikeLike [d9c] Nikhil April 26, 2010 at 8:21 pm Reply + Nikhil, The Event Chain Methodology (ECM) uses Bayes theorem to evaluate the conditional probabilty of an event occuring. The two are very different: ECM is a scheduling technique whereas Bayes theorem is a fundamental principle of probability. Regards, Kailash. LikeLike [fc3] K April 27, 2010 at 9:18 pm Reply 5. [...] and objective Bayesian interpretations because knowledge about these events can be refined using Bayes Theorem, providing one has relevant data regarding the occurrence of [...] LikeLike On the interpretation of probabilities in project management << Eight to Late July 1, 2010 at 10:09 pm Reply 6. [...] can be figured out using Bayes' Theorem, which in the context of the question can be stated as [...] LikeLike On the accuracy of group estimates << Eight to Late December 1, 2011 at 5:16 am Reply 7. I liked. LikeLike [a49] Felix May 13, 2014 at 6:37 am Reply 8. [...] Bayes theorem, which I've explained at length in this post, this can be recast [...] LikeLike A gentle introduction to Naive Bayes classification using R | Eight to Late November 6, 2015 at 7:34 am Reply 9. [...] I'll save the heavy statistics on this post, however if you are interested in further reading on this algorithm you can find it here https://eight2late.wordpress.com/2010/03/11/ bayes-theorem-for-project-managers/. [...] LikeLike A Naive Approach To Football | Karl's Blog April 1, 2016 at 9:49 am Reply Leave a Reply Cancel reply Enter your comment here... [ ] Fill in your details below or click an icon to log in: * * * * Gravatar Email (required) (Address never made public) [ ] Name (required) [ ] Website [ ] WordPress.com Logo You are commenting using your WordPress.com account. ( Log Out / Change ) Twitter picture You are commenting using your Twitter account. ( Log Out / Change ) Facebook photo You are commenting using your Facebook account. ( Log Out / Change ) Cancel Connecting to %s [ ] Notify me of new comments via email. [ ] Notify me of new posts via email. [Post Comment] [ ] [ ] [ ] [ ] [ ] [ ] [ ] D[ ] This site uses Akismet to reduce spam. Learn how your comment data is processed. Subscribe Enter your email address and click "Follow" to receive notifications of new posts. Your address will not be used for any other purpose. Email Address: [ ] Follow Search Search for: [ ] [Search] Author * About * Sensanalytics Consulting * Datanitio Copyright * Copyright Notice [top_mgmt_resource_2012] My book Check out reviews of my book on Amazon * The Heretic's Guide to Best Practices Top Posts & Pages * Bayes Theorem for project managers * A gentle introduction to logistic regression and lasso regularisation using R * An introduction to Monte Carlo simulation of project tasks * Metaphors we argue by * A gentle introduction to text mining using R * Motivation in project management * From the coalface: an essay on the early history of sociotechnical systems * A gentle introduction to topic modeling using R * The system and the lifeworld: a note on the gap between work and life * Cox's risk matrix theorem and its implications for project risk management Recent Posts * Perceptions of change * Making sense of entrepreneurship - a conversation with Craig Brown * The ethical dimension of complex decision making - a metalogue * From ambiguity to action - a paper preview * Monte Carlo Simulation of Projects - an (even simpler) explainer Categories * AI Fiction * Argumentation * Best Practice * Bias * Book Review * Business Fables * Business Intelligence * Causality * Communication * Consulting * Corporate IT * Data Analytics * Data Science * Data Visualization * Decision Making * Design Rationale * Dialogue Mapping * Emergent Design * Enterprise Architecture * Estimation * General Management * Issue Based Information System * Issue Mapping * IT Management * Knowledge Management * Leadership * Limericks * Management * Metalogues * mismanagement * Monte Carlo Simulation * Organizational Culture * Organizational Paradoxes * Organizations * Paper Review * People Management * Personal * portfolio management * Power Laws * Predictive Analytics * Probability * Project Management * R * Risk analysis * Sensanalytics * Sensemakers * sensemaking * Statistics * Systems Thinking * Tacit Knowledge * Text Analytics * Text Mining * Verse * Wicked Problems * Writing Archives * January 2023 * November 2022 * October 2022 * May 2022 * January 2022 * October 2021 * September 2021 * June 2021 * May 2021 * March 2021 * December 2020 * May 2020 * February 2020 * January 2020 * October 2019 * September 2019 * May 2019 * February 2019 * January 2019 * December 2018 * July 2018 * June 2018 * March 2018 * February 2018 * December 2017 * November 2017 * October 2017 * September 2017 * July 2017 * April 2017 * March 2017 * February 2017 * January 2017 * December 2016 * October 2016 * September 2016 * July 2016 * June 2016 * May 2016 * March 2016 * February 2016 * January 2016 * December 2015 * November 2015 * October 2015 * September 2015 * August 2015 * July 2015 * June 2015 * May 2015 * April 2015 * March 2015 * February 2015 * January 2015 * December 2014 * November 2014 * October 2014 * September 2014 * August 2014 * July 2014 * June 2014 * May 2014 * April 2014 * March 2014 * February 2014 * January 2014 * December 2013 * November 2013 * October 2013 * September 2013 * August 2013 * July 2013 * June 2013 * May 2013 * April 2013 * March 2013 * February 2013 * January 2013 * December 2012 * November 2012 * October 2012 * September 2012 * August 2012 * July 2012 * June 2012 * May 2012 * April 2012 * March 2012 * February 2012 * January 2012 * December 2011 * November 2011 * October 2011 * September 2011 * August 2011 * July 2011 * June 2011 * May 2011 * April 2011 * March 2011 * February 2011 * January 2011 * December 2010 * November 2010 * October 2010 * September 2010 * August 2010 * July 2010 * June 2010 * May 2010 * April 2010 * March 2010 * February 2010 * January 2010 * December 2009 * November 2009 * October 2009 * September 2009 * August 2009 * July 2009 * June 2009 * May 2009 * April 2009 * March 2009 * February 2009 * January 2009 * December 2008 * November 2008 * October 2008 * September 2008 * August 2008 * July 2008 * June 2008 * May 2008 * April 2008 * March 2008 * February 2008 * January 2008 * December 2007 * November 2007 * October 2007 * September 2007 Blogroll * Craig Brown * Glen Alleman * Nicholas Carr * Paul Culmsee * Ricardo Guido Lavalle * Scott McCrickard * Tim van Gelder * Toby Elwin Other links * Australian Financial Review article on "The Heretic's Guide to Management" * Book Excerpt - Platitudes in Organizations * DataCamp course on support vector machines * Eight to Late featured in oDesk's Top 25 PM Blogs * Eight to Late in Capterra's list of 58 Most "Insanely Useful" Project Management Blogs * Interview - Smart Company (w/ Paul Culmsee) * Uncertainty in The Workplace - ABC Radio interview /w Richard Aedy Blog at WordPress.com. * Follow Following + [wpcom-] Eight to Late Join 933 other followers [ ] Sign me up + Already have a WordPress.com account? Log in now. * + [wpcom-] Eight to Late + Customize + Follow Following + Sign up + Log in + Copy shortlink + Report this content + View post in Reader + Manage subscriptions + Collapse this bar Loading Comments... Write a Comment... [ ] Email (Required) [ ] Name (Required) [ ] Website [ ] [Post Comment] %d bloggers like this: [b]