[Like any asset IT is a resource to be managed. The resource has a cost and must deliver an adequate return/ROI. Projects must also be delivered on time and within reasonable budgets variances. Please develop a guideline that ensures:
(1) IT spending and investment will be alighned with corporate objectives
(2) The risk of bad IT implementation outcomes are mitigated]
Ideas/suggestions: Please discuss in general the appropriate metrics that one may need to track. Also discuss how investing in IT with an eyes towards the replacement/automation of another project/issue or task may work (e.g., if Company Z invests in technolgies, A-C it may be able to shut down more antiquated systems and realize the higest ROI amongst the existing projects in the portfolio.
Treat and analyze the list of IT projects as a portfolio whereby different ROIs and payback periods may differ for projects based on a segmentation of: (1) Strategic Importance (e.g., High - Low) by (2) Ability to Execute
or Strategic Importance today (High-Low) vs. Strategic Importance Tomorrow (High-Low). This framework can describe IT projects that fall into the following categories:
Legacy (Low - Today, Low - Tomorrow)
Falling Stars (High - Today, Low - Tomorrow)
Stars (high - Today, High - Tomorrow)
Rising Stars (Low - Today, High - Tomorrow)
Tomorrow represents the near/long term.
Thanks!© BrainMass Inc. brainmass.com March 4, 2021, 6:15 pm ad1c9bdddf
Four IT projects are discussed as a portfolio, the various pitfalls are discussed that need to be avoided and the investment and returns on investment are tabulated for the four projects in alignment with the required timing of the returns. From the payback analysis one can decide when one would like to have its investment back so that the investment can be used in future projects.
The LEGACY works with British Aerospace operating companies to advance the technology of high integrity aerospace computing systems. The Newcastle group concentrates on the accurate representation, analysis and tracing of system requirements. Techniques have been developed to represent safety requirements, including timing properties, to a high level of rigor, leading on to systematic representation of design strategies, with the ability to prove the strategies against the safety requirements. Work on formal methods support includes development of accessible notations for the representation of timing, functionality and system structure. Traceability work aims to provide a systematic linkage between requirements and the parts of the system design that purport to satisfy them. All developments are regularly tested against case studies supplied by the operating companies of BAe. The strategic importance is of this project is not very high now nor is it likely to be high in future and the financial returns will reflect the strategic importance.
The strategic importance of this project is that it is targeted at a reliable segment and is likely to get work in future. Even though the returns are the lowest in this project, now and in the long run, the strategic importance of this project is that further projects can be expected from BA in future. This project is important for cultivating a relationship.
The overall objective of FALLING STARS is the creation of a methodology and supporting open tool platform for the cost effective rigorous development of dependable complex software systems and services.
The project focuses on tackling complexity (i) caused by the environment in which the software is to operate; (ii) which comes from poorly conceived architectural structure.
Mastering complexity requires design techniques that support clear thinking and rigorous validation and verification. Formal design methods do so. Coping with complexity also requires architectures that are tolerant of faults and unpredictable changes in environment. This is addressed by fault tolerance design techniques dealing with faults in the system environment, faults of the individual component, component mismatches, as well as errors affecting interacting components.
The project will develop a unified methodology combining formal methods with fault tolerance design principles by using a systems approach, where both software and environment are modeled together. We will tackle complex architectures: the systems approach will support the construction of appropriate abstractions and provide ...
Four IT projects are discussed as a portfolio.