Effect Managing ITCopenhagen Business School Press DK, 2007 - 104 pagina's Information Technology (IT) products in themselves do not create any effects - these arise when the products are used. In order to obtain the intended effects from their investments, all purchasers should actively manage their projects towards these effects. This sounds obvious but is unusual in practice. This book demonstrates clear working methods and techniques for managing IT projects so that the anticipated effects arise. It also contains many inspiring real-world examples. Many IT projects focus very weakly on benefit and effect once the development project has commenced. Thus, it is not particularly strange that many of the IT solutions produced are unnecessarily difficult to use and don't create the operational benefit that is anticipated, not to mention the unforeseen costs of the various measures that are required in order to put right what has gone wrong. There is an easy way to procure, conduct, and follow up IT projects with the aim of achieving real benefit for both the operation and the user. This book demonstrates a concrete method, which puts its finger on the point where the benefit arises on every occasion of use. Effect Managing IT is aimed at people who make decisions about, who implement, and who are responsible for IT investments, such as purchasers, line managers, executives, IT managers, business developers, buyers, and project managers. |
Veelvoorkomende woorden en zinsdelen
able actions AstraZeneca booking system car pool Car-Sharing carbon footprint carried Check point commercial concept conducted contribute costs create the desired create the expected decision-makers degree of usage describe desired effects detailed DSDM effect management effect map effect targets effects arise ensure entails environment envisaged evaluated expected benefit expected effects focus following supportive data formulated functions Göteborgs-Posten high level implemented important interaction design investment knowledge level of ambition measurement points ment methods needs and expectations Ny Teknik operational benefit Order recipients organisation perspective possible prioritized problems procurement product architect product design product quality productivity paradox project manager project members proposed public transport purchaser requirements regarding responsible role SAP R/3 Smartcards solutions specific steering group meeting supplier Sweden Swedish system architect system development target group analysis tasks technical quality tion usage goals usage quality usage situation usage test User Interface Engineering