IT Business Cases in Local Government: An Action Research Study

Nielsen, Peter Axel; Persson, John Stouby

doi:10.1109/hicss.2012.393

Cited by 3 publications

(3 citation statements)

References 34 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Benaroch, Lichtenstein, and Robinson (2006, p. 835) defines it as "a comprehensive document that includes the project description, resources required, benefits and financial plans, and a risk management plan." A recent definition was provided by (Nielsen & Persson, 2012), who define a business case as "an artifact in the form of a document specifying the main rationale behind the expected value and cost of an IT investment for the adopting organisation." In practitioner literature, a business case is defined as "documentation of the rationale for making a business investment, used to support a business decision on whether to proceed or not with the investment" (ITGI, 2008).…”

Section: A Formal Document To Justify An Investmentmentioning

confidence: 99%

Investigating a Process Approach on Business Cases

Maes

Haes

Grembergen

2013

International Journal of IT/Business Alignment and Governance

View full text Add to dashboard Cite

Strategic information technology (IT) enabled investments are among other types of IT investments, characterised by the highest level of uncertainty and the highest potential for value creation. They are often associated with product/service innovation, new business models or an enterprise-wide transformation (e.g. Enterprise Resource Planning (ERP) investment). Although these may deliver operational excellence and a competitive advantage, it is a risky endeavour with high failure rates. One of the critical factors to achieve a successful outcome is to develop a sound business case. Many organisations perceive a business case as a valuable instrument for investment justification and decision-making, yet other organisations still do not develop a business case due to insufficient knowledge. In response to this knowledge gap, Ward, Daniel, and Peppard (2008) designed a business case development process that ends on investment approval. Others scholars however call for a continuous usage of business cases throughout the entire investment life cycle. The present research responds to this call with an exploratory case study in order to identify multiple business case tasks that complement the process of Ward et al. (2008). The paper starts with a description of background literature on what constitutes a business case whereof the authors derive a new definition. The authors then set the context and structure for an initial business case process based on the contribution by (Ward et al., 2008). The findings of the exploratory case study and the initial business case process are discussed.

show abstract

Section: A Formal Document To Justify An Investmentmentioning

confidence: 99%

Investigating a Process Approach on Business Cases

Maes

Haes

Grembergen

2013

International Journal of IT/Business Alignment and Governance

View full text Add to dashboard Cite

show abstract

“…For example, Nielsen and Persson (2012) describe that, in some of the municipalities they investigated, business cases were developed after an investment decision was made already, to justify and promote the IT investment decision internally. In contrast with the ideas of HBSP (2010) about business cases (i.e.…”

Section: Business Case: What It Is Notmentioning

confidence: 99%

“…Nielsen and Persson (2012) define business cases as artefacts in the form of a document specifying the main rationale behind the expected value and cost of an IT investment for the adopting organization. Also Ward et al (2008) relate business cases with IT projects in terms of a method, amongst others, to get funding for the investment.…”

Section: Business Case: What It Ismentioning

confidence: 99%

Relating business modelling and enterprise architecture

Meertens¹

View full text Add to dashboard Cite

English SummaryThis thesis proposes a methodology for creating business models, evaluating them, and relating them to enterprise architecture. The methodology consists of several steps, leading from an organization's current situation to a target situation, via business models and enterprise architecture. The problems with Business-IT AlignmentCurrently, increasing amounts of businesses rely on IT systems to do their business. However, success rates of IT implementations projects are low. Difficulties exist in aligning existing IT systems with business objectives. A consensus exists among researchers and practitioners alike that business-IT alignment (BITA) is necessary to improve business performance. Typical symptoms of lack of BITA include:• People cannot use the systems effectively.• Changes in systems often do not consider the financial impacts.• Systems cannot be changed easily and quickly to adapt to new situations.Difficulties also exist with technological innovations. Most difficulties are not caused by technical issues. Lack of consideration for financial and organisational aspects is a cause for projects not surviving after the pilot phase. A lack of attention is paid to financial aspects of innovations. Projects are often more expensive than planned due to changing requirements. Projects are often more expensive than planned because demands are not well known. Therefore, we have a problem to build and adapt IT systems to changing business needs. This thesis attempts to combine two partial solutions to this problem, Enterprise Architecture (EA) and Business Modelling (BM). A partial solution: Enterprise ArchitectureEnterprise Architecture comprises a collection of simplified representations of the organisation, from different viewpoints and according to the needs of different stakeholders. A coherent description of enterprise architecture provides insight, enables communication among stakeholders, and guides complicated change processes. ArchiMate provides a language to create such descriptions in a precise and formal way. While Enterprise Architecture helps to manage change, it includes insufficient business strategy, and use of ArchiMate is limited to expert users. Another partial solution: Business ModellingIn the basis, business models are used to describe businesses and explore possibilities for future development. Business modelling is intuitive to use by managers, consultants, VI and entrepreneurs alike. The business model concept is a young and emerging field of research. The state in which this field finds itself is one of "prescientific chaos": several competing schools of thought exist, and progress is limited because of a lack of cumulative progress. Links to other research domains are vital to establish the business model as a distinct area of investigation. This lack of cohesion in the field clearly diminishes the added value of business models for organizations and makes business modelling an art, rather than a science. A combined solution: Relating Enterprise Architecture and Business ...

show abstract

Benefits management in software development: A systematic review of empirical studies

et al. 2021

View full text Add to dashboard Cite

Considerable resources are wasted on software projects delivering less than the planned benefits. Herein, the objective is to synthesize empirical evidence of the adoption and impact of benefits management (BM) in software development, and to suggest directions for future research. A systematic review of the literature is performed and identified 4836 scientific papers of which the authors found 47 to include relevant research. While most organizations identify and structure benefits at the outset of a project, fewer organizations report implementing BM as a continuous process throughout the project lifecycle. Empirical evidence gives support for positive impact on project outcome from the following BM practices: identifying and structuring benefits, planning benefits realization, BM during project execution, benefits evaluation and the practice of having people responsible for benefits realization. The authors suggest four research directions to understand (1) why BM practices sometimes not are adopted, (2) BM in relation to other management practices, (3) BM in agile software development and (4) BM in the context of organizations' value creation logics.

show abstract

IT Business Cases in Local Government: An Action Research Study

Cited by 3 publications

References 34 publications

Investigating a Process Approach on Business Cases

Investigating a Process Approach on Business Cases

Relating business modelling and enterprise architecture

Benefits management in software development: A systematic review of empirical studies

Contact Info

Product

Resources

About