Jump to content

Business case

From Wikipedia, the free encyclopedia

A business case captures the reasoning for initiating a project or task.[1] Many projects, but not all, are initiated by using a business case.[2] It is often presented in a well-structured written document,[3] but may also come in the form of a short verbal agreement or presentation. The logic of the business case is that, whenever resources such as money or effort are consumed, they should be in support of a specific business need.[2] An example could be that a software upgrade might improve system performance, but the "business case" is that better performance would improve customer satisfaction, require less task processing time, or reduce system maintenance costs. A compelling business case adequately captures both the quantifiable and non-quantifiable characteristics of a proposed project. According to the Project Management Institute, a business case is a "value proposition for a proposed project that may include financial and nonfinancial benefit."[4]

Business cases can range from comprehensive and highly structured, as required by formal project management methodologies, to informal and brief. Information included in a formal business case could be the background of the project, the expected business benefits,[5] the options considered (with reasons for rejecting or carrying forward each option), the expected costs of the project, a gap analysis and the expected risks. Consideration should also be given to the option of doing nothing including the costs and risks of inactivity. From this information, the justification for the project is derived.

Reasons for creating a business case

[edit]

Business cases are created to help decision-makers ensure that:

  • the proposed initiative will have value[6] and relative priority compared to alternative initiatives based on the objectives and expected benefits laid out in the business case.

Development and approval process

[edit]

Business process

[edit]
A business process, business method, or business function is a collection of related, structured activities or tasks performed by people or equipment in which a specific sequence produces a service or product (that serves a particular business goal) for a particular customer or customers. Business processes occur at all organizational levels and may or may not be visible to the customers.[7][8][9] A business process may often be visualized (modeled) as a flowchart of a sequence of activities with interleaving decision points or as a process matrix of a sequence of activities with relevance rules based on data in the process.[8][9][10][11] The benefits of using business processes include improved customer satisfaction and improved agility for reacting to rapid market change.[7][8] Process-oriented organizations break down the barriers of structural departments and try to avoid functional silos.[12]

Business process design

[edit]

The business case process should be designed to be:

  • adaptable – tailored to the size and risk[2] of the proposal
  • consistent – the same basic business issues are addressed by every project
  • business oriented – concerned with the business capabilities and impact, rather than having a technical focus
  • comprehensive – includes all factors relevant[13] to a complete evaluation
  • understandable – the contents are clearly relevant, logical and, although demanding, are simple to complete and evaluate
  • measurable – all key aspects can be quantified so their achievement can be tracked and measured
  • transparent – key elements can be justified directly
  • accountable – accountability and commitments for the delivery of benefits and management of costs are clear.

Components of a business case report

[edit]

A good business case report brings confidence and accountability into the field of making investment decisions. It is a compilation of all information collected during enterprise analysis and the business case process. The key objective is to provide evidence and justification for continuing with the investment proposition.

A business case can include details such as strategic alignment, return on investments, risk exposure assessment, feasibility study, expected Key Performance Indicators, evaluations and alternative measures.[14][15]

Strategic alignment

[edit]
Strategic alignment is a process that ensures an organization's structure, use of resources (and culture) support its strategy. "In its simplest form, organizational strategic alignment is lining up a business' strategy with its culture."[16] Successful outcomes also require an awareness of the wider environment, regulatory issues and technological change.[17] Strategic alignment contributes to improved performance by optimizing the operation of processes/systems, and the activities of teams and departments. Goal-setting theory supports the relevance of clear, measurable operational objectives that can be linked to superordinate goals. This helps ensure resources are used effectively.

Feasibility study

[edit]
A feasibility study is an assessment of the practicality of a project or system. A feasibility study aims to objectively and rationally uncover the strengths and weaknesses of an existing business or proposed venture, opportunities and threats present in the natural environment, the resources required to carry through, and ultimately the prospects for success.[18][19][20] In its simplest terms, the two criteria to judge feasibility are cost required and value to be attained.[21]

Key performance indicators

[edit]
A performance indicator or key performance indicator (KPI) is a type of performance measurement.[22] KPIs evaluate the success of an organization or of a particular activity (such as projects, programs, products and other initiatives) in which it engages.[23] KPIs provide a focus for strategic and operational improvement, create an analytical basis for decision making and help focus attention on what matters most.[24]

Example of a business case report structure

[edit]

Here is an example of a report structure for a business case:[25][26]

Review and approval

[edit]

At various stages in the project, the business case should be reviewed to ensure that:

  • The justification is still valid,
  • The project will deliver the solution to the business need.

The result of a review may be the termination or amendment of the project.[27] The business case may also be subject to amendment if the review concludes that the business need has abated or changed,[2] this will have a knock on effect[28] on the project.

Public sector projects

[edit]

Many public sector projects are now required to justify their need through a business case. In the public sector, the business case is argued in terms of cost–benefit analysis, which may include both financial and non-financial cost and benefits.[29] This allows the public body concerned to take social and environmental benefits into account, allowing a more comprehensive understanding of economic impacts.

See also

[edit]

Notes

[edit]
  1. ^ Project Management Institute 2021, §Appendix X3.2 The PMO Value Proposition - Why have one?.
  2. ^ a b c d Project Management Institute 2021, §3.4 Focus on Value.
  3. ^ Project Management Institute 2021, §2.6.1 Delivery of Value.
  4. ^ Project Management Institute 2021, §Glossary Section 3. Definitions.
  5. ^ Project Management Institute 2021, §4.6.1 Strategy Artifacts.
  6. ^ Project Management Institute 2021, Section 3.4 Focus on Value.
  7. ^ a b Weske, M. (2012). "Chapter 1: Introduction". Business Process Management: Concepts, Languages, Architectures. Springer Science & Business Media. pp. 1–24. ISBN 9783642286162.
  8. ^ a b c Kirchmer, M. (2017). "Chapter 1: Business Process Management: What Is It and Why Do You Need It?". High Performance Through Business Process Management: Strategy Execution in a Digital World. Springer. pp. 1–28. ISBN 9783319512594.
  9. ^ a b von Scheel, H.; von Rosing, M.; Fonseca, M.; et al. (2014). "Phase 1: Process Concept Evolution". In von Rosing, M.; Scheer, A.-W.; von Scheel, H. (eds.). The Complete Business Process Handbook: Body of Knowledge from Process Modeling to BPM. Vol. 1. Morgan Kaufmann. pp. 1–10. ISBN 9780128004722.
  10. ^ Chen, M. (2012). "Chapter 8: BPR Methodologies: Methods and Tools". In Elzinga, D.J.; Gulledge, T.R.; Lee, C.-Y. (eds.). Business Process Engineering: Advancing the State of the Art. Springer Science & Business Media. pp. 187–212. ISBN 9781461550914.
  11. ^ Chand, D.R.; Chircu, A.M. (2012). "Chapter 3: Business Process Modeling". In Elzinga, D.J.; Gulledge, T.R.; Lee, C.-Y. (eds.). Business Enterprise, Process, and Technology Management: Models and Applications. Springer Science & Business Media. pp. 187–212. ISBN 9781466602502.
  12. ^ von Rosing, M.; Kemp, N.; Hove, M.; Ross, J.W. (2014). "Process Tagging - A Process Classification and Categorization Concept". In von Rosing, M.; Scheer, A.-W.; von Scheel, H. (eds.). The Complete Business Process Handbook: Body of Knowledge from Process Modeling to BPM. Vol. 1. Morgan Kaufmann. pp. 123–172. ISBN 9780128004722.
  13. ^ Project Management Institute 2021, §2.7.1.2 Effective Metrics.
  14. ^ Project Management Institute 2021, §3.4 Strategy Artifacts.
  15. ^ Tamang, Suman. "Business Case Study of Yahoo: The Rise and Fall". Money Sifu. Retrieved December 2, 2023.
  16. ^ "Approaches to Organizational Strategic Alignment". Small Business - Chron.com. Retrieved 2021-07-14.
  17. ^ Faucheux, Sylvie; Nicolaı̈, Isabelle (1998). "Environmental technological change and governance in sustainable development policy". Ecological Economics. 27 (3): 243–256. doi:10.1016/s0921-8009(97)00176-6. ISSN 0921-8009. S2CID 154733072.
  18. ^ Justis, R. T. & Kreigsmann, B. (1979). The feasibility study as a tool for venture analysis. Business Journal of Small Business Management 17 (1) 35-42.
  19. ^ Georgakellos, D. A. & Marcis, A. M. (2009). Application of the semantic learning approach in the feasibility studies preparation training process. Information Systems Management 26 (3) 231-240.
  20. ^ McLeod, Sam (2021-12-01). "Feasibility studies for novel and complex projects: Principles synthesised through an integrative review". Project Leadership and Society. 2: 100022. doi:10.1016/j.plas.2021.100022.
  21. ^ Young, G. I. M. (1970). Feasibility studies. Appraisal Journal 38 (3) 376-383.
  22. ^ Carol Fitz-Gibbon (1990), "Performance indicators", BERA Dialogues (2), ISBN 978-1-85359-092-4
  23. ^ Weilkiens, Tim; Weiss, Christian; Grass, Andrea; Duggen, Kim Nena (2016). "Frameworks". OCEB 2 Certification Guide. Elsevier. pp. 149–169. doi:10.1016/b978-0-12-805352-2.00007-8. ISBN 9780128053522. KPI is a business metric that measures the degree of fulfillment of a goal or a Critical Success Factor (CSF). The CSF is an organization-internal or organization-external property that is necessary to achieve a specific goal. A CSF can involve multiple KPIs.
  24. ^ "What is a Key Performance Indicator (KPI)". KPI.org. Retrieved 1 January 2022.
  25. ^ Source: Messner, W.: More on Making the Compelling Business Case Archived 2017-04-06 at the Wayback Machine GloBus Research, accessed: 5 May 2013 and Messner, W. (2013): Making the Compelling Business Case. Houndmills: Palgrave Macmillan.
  26. ^ Vardrup, Kasper; Stigzelius, Mats. "How to write a solid Business Case". Slideworks.io. Retrieved 18 June 2024.
  27. ^ Project Management Institute 2021, §3.4 The Tailoring Process.
  28. ^ Project Management Institute 2021, §2.8.3 Complexity.
  29. ^ Project Management Institute 2021, §4.4.1 Data Gathering and Analysis.

References

[edit]
  • Messner, W.: Making the Compelling Business Case. Decision-Making Techniques for Successful Business Growth. Houndmills: Palgrave Macmillan, 2013 (book companion website)
  • Project Management Institute (2021). A guide to the project management body of knowledge (PMBOK guide). Project Management Institute (7th ed.). Newtown Square, PA. ISBN 978-1-62825-664-2.{{cite book}}: CS1 maint: location missing publisher (link)
  • Schaltegger, S. & Wagner, M. (Eds.): Managing the Business Case for Sustainability. The Integration of Social things, and Economic Performance. Sheffield: Greenleaf, 2006
[edit]