|
|
| Line 1: |
Line 1: |
| {{Refimprove|date=December 2008}}
| | The writer's name is Christy Brookins. To play lacross is the factor I adore most of all. He is an information officer. Ohio is exactly where his house is and his family members enjoys it.<br><br>my site - phone psychic ([http://www.octionx.sinfauganda.co.ug/node/22469 visit link]) |
| | |
| '''Assumption-based planning'' in [[project management]] is a post-planning method that helps companies to deal with uncertainty. It is used to identify the most important assumptions in a company’s [[business plan]]s, to test these assumptions, and to accommodate unexpected outcomes. | |
| | |
| == Overview ==
| |
| Conventional business planning works on the expectation that managers can extrapolate future results from past experience, but for new businesses and projects this way of planning is often not possible. Experience may be lacking or extrapolating from past experience may be misleading.<ref>Christensen, C., Kaufman, S., & Shih, W. 2008. Innovation killers: how financial tools destroy your capacity to do new things. Harvard Business Review, 86(1): 98-105, 137.</ref>
| |
| | |
| A solution to this problem is to make assumptions and attempt to predict future outcomes. Some of the assumptions made during the planning process are very likely to come true; the outcome of others is very much uncertain, though not unimportant. Assumption-based planning identifies and tests the assumptions made in a business plan, the formulation of “hedging actions” and the construction of “what-if” scenarios.
| |
| | |
| Uncertainties are identified and plans can be prepared for what to do if original predictions prove to be false. Assumption-based planning does not demand accuracy for all assumptions made in a business plan, but builds a reasonable model to assess the assumptions involved.
| |
| | |
| Assumption-based planning methods include:
| |
| * [[Critical assumption planning]] (CAP) by D. Dunham & Co.
| |
| * Assumption-based planning by [[RAND]] : raises the visibility of make-or-break uncertainties common to new ventures by forcing managers to admit what they don’t know.
| |
| * Discovery-Driven Planning by [[Rita Gunther McGrath]] and Ian C. MacMillan.<ref>McGrath, R. G. & MacMillan, I. C. 1995. Discovery Driven Planning. Harvard Business Review, 73(4): 44-54.</ref><ref>McGrath, R. G. & MacMillan, I. C. 2009. Discovery Driven Growth: A Breakthrough Process to Reduce Risk and Seize Opportunity. Boston: Harvard Business Publishing</ref>
| |
| | |
| Assumption-based planning methodologies provided the foundation for other planning frameworks and tools such as [[Robust decision making]].
| |
| | |
| == Position in business planning process ==
| |
| Most business planning methods or books about “how to write a business plan” indicate that you should write down your financial assumptions at the end of your plan, but assumption-based planning encourages managers to actively plan and monitor the validation of these assumptions.
| |
| | |
| The identification of assumptions may lead to a change in the business plan, so advocates of assumption-based planning argue that it should be at the core of business planning.
| |
| | |
| ==Types of assumption==
| |
| [[RAND]] defines an assumption as “an assertion about some characteristic of the future that underlies the current operations or plans of an organization.” There are several types of assumption. Include implicit and explicit assumptions, and primary and secondary assumptions, an important aspect of [[Critical assumption planning]]. The two classifications are not mutually exclusive; an assumption can be both explicit and primary.
| |
| | |
| === Implicit and explicit assumptions ===
| |
| Explicit assumptions are assumptions of which the intention that is fully revealed or expressed without vagueness, implication or ambiguity. However, explicit statements in a plan often have hidden implicit assumptions. Implicit assumptions are assumptions that are not expressed and may go undetected. If implicit assumptions prove to be wrong, this can damage projects.
| |
| | |
| {|
| |
| |+ Examples of implicit assumptions:<ref>McGrath, R. G. and I. C. MacMillan (1995). ''Discovery-Driven Planning''. Harvard Business Review.</ref>
| |
| |-
| |
| | style="background-color: #CCC; border: 2px solid black" |
| |
| # Customers will buy our product because we think it’s a good product
| |
| # Customers will buy our product because it’s technically superior
| |
| # Customers will agree with our perception that the product is “great”
| |
| # The product will sell itself
| |
| # Distributors are desperate to stock and service the product
| |
| # We can develop the product on time and on budget
| |
| # Competitors will respond rationally
| |
| # We will be able to hold down prices while gaining share rapidly
| |
| # We will have no trouble attracting the right staff
| |
| # Customers will run no risk in buying from us instead of continuing to buy from their past suppliers
| |
| |-
| |
| |}
| |
| | |
| == Process of assumption-based planning==
| |
| [[File:ABP process.gif|thumb|320px|Assumption-based planning. The blue part of the figure depicts the process steps of a general assumption based planning method, the white part identifies the separate deliverables. Every step is described in the assumption based planning process list displayed below the picture.<ref>The modelling method in general is a result from a method engineering approach as proposed by the [[University of Utrecht]] in its "Method Engineering Encyclopedia"</ref>]]
| |
| | |
| The steps of assumption-based planning are:
| |
| * Identify assumptions: Collect all assumptions implicit, explicit, primary and derivative, out of the (business) plan.
| |
| * Determine criticality: Try to quantify the assumptions as much as possible in order to determine which assumptions have the greatest (financial) impact.
| |
| * Design tests: Design a test for every critical assumption. In a test design you state how to test the assumption and what proves the assumption wrong or right.
| |
| * Schedule tests: Every critical assumption needs to be tested, but not all assumptions can be tested in the present. So future assumptions tests are scheduled in a test schedule. Some possible reasons to schedule a test in the future are a lack of information in the present or a dependency on the test outcomes of other tests.
| |
| * Test assumptions: Then an assumption is tested this results in a test outcome, which proves the assumption right or wrong.
| |
| * Reassess plan: Based on the test outcomes and the test schedule one might decide to reassess the venture plan and update the business plan with the new insights gathered in the ABP process.
| |
| * Plan re-testing: The assumptions need to be re-tested regularly if not constantly. There should be a retest schedule of every critical assumption.
| |
| * Create or update the assumption plan: The assumption plan holds all data gathered during the ABP process.
| |
| | |
| ==Critical assumption planning==
| |
| | |
| ''Critical assumption planning'' (CAP) is a service mark of D. Dunham & Co. It helps managers and entrepreneurs maximize business development learning at least cost. The continuous process consists of six steps: Knowledge Base Assessment, Critical Assumption Planning, Test Program Design, Funding Request, Test Implementation and Venture Reassessment.<ref>Sykes, H. B. and D. Dunham (1995). "Critical assumption planning: A practical tool for managing business development risk." ''Journal of Business Venturing'' 10(6): 413-424.</ref><ref>Block, Zenas and Ian C. Macmillan (1985). [http://hbr.org/1985/09/milestones-for-successful-venture-planning/ar/1 "Milestones for Successful Venture Planning."] "Harvard Business Review" September 1985.</ref>
| |
| | |
| CAP is built on the foundation of the work of Block (1989) who showed that assumptions can stand in the way of perceiving current business realities. The identification and assessment of assumptions solves this problem and forms the foundation for managing new business ventures.
| |
| | |
| CAP involves six steps, combined in a "Learning Loop". Once all six steps are completed, a milestone is reached and the loop starts over again. The loop is constantly repeated as the business is developing.
| |
| [[image:cap-process.gif|frame|none|The Critical Assumption Planning Process]]
| |
| | |
| ===Knowledge-base assessment===
| |
| This step takes "a comprehensive analysis of what is known and unknown about the competition, market and technology" (Sykes 1995). In this step the entrepreneur oversees his plans and the first assumptions are exposed. Important parts of the [[business plan]] to check are the definition of the business concept and an assessment of the competition.
| |
| | |
| ===Critical assumption identification===
| |
| During this step the assumptions are identified and there is a determination of criticality. The hardest part of CAP is to identify the assumptions that are not written down.
| |
| | |
| In order to determine the criticality of the assumptions, they need to be quantified; it is then possible to put the financial results in a [[spreadsheet]] and link them together. These financial impacts will change for the various assumptions.
| |
| | |
| CAP measures the criticality of an assumption as a change in the [[net present value]] of a venture (NPV). To determine criticality each assumption is assigned a range of uncertainty: base case, best and worst case. Then, assumption for assumption, while keeping the other assumptions at [[ceteris paribus|base case]], the NPV changes for each assumption in the worst and best case scenarios are checked.
| |
| | |
| The NPV analysis proves the company with information about the criticality of an assumption. Two signals strongly indicate a critical assumption: a big difference in NPV between the best and worst-case scenarios, or a huge loss of NPV in the worst-case scenario
| |
| | |
| ===Test program design===
| |
| The assumptions need to be tested. Sometimes good market research is enough,
| |
| other times a working prototype needs to be developed. The order in which the assumptions are tested is critical in terms of the money spent on testing. One
| |
| of the major focuses of the CAP method is to maximize the learning per unit expenditure on testing.
| |
| | |
| In order to determine the best testing option the test Effectiveness ratio (e)
| |
| is calculated for one or more assumptions based on the estimated Costs (C), Time spend on testing (T) and the estimated reduction (R) between the NPV values of the assumptions (P as a percentage of the NPV range). Using these parameters, the effectiveness ratio (e) is calculated:
| |
| | |
| <math> | |
| e = \frac{\sum (PR)}{CT}
| |
| </math> | |
| | |
| <!--
| |
| e = SUM(PR) / (CT)
| |
| -->
| |
| | |
| Once the best testing option is chosen from the different test effectiveness values, the organisation can finish the planning of the test.
| |
| | |
| ===Funding request===
| |
| When the test program design is ready and the costs are clear, resources have to be allocated to the test program. In most companies or start-ups clearance from senior managers or [[venture capitalists]] is needed to conduct the tests.
| |
| | |
| ===Test implementation===
| |
| In this step the actual testing of the assumptions takes place.
| |
| | |
| ===Venture Reassessment===
| |
| When the results of one or more tests are known, it might be that resources need to be re-allocated and business plans have to be updated.
| |
| | |
| == References ==
| |
| {{reflist}}
| |
| | |
| ==External links==
| |
| *[http://www.andrewgrill.com/cap Australian CAP Case Study]
| |
| | |
| [[Category:Project management]]
| |