Archive for the 'Application Lifecycle Management' Category

Peter HelfensteinPeter Helfenstein HP BTO Software Centers – Overview

07/24/2008 by Peter Helfenstein

HP offers a number of BTO Centers. These software packages support in the context of a BTO strategy specific phases of the application lifecycle. The following overview is meant to shed light on the HP BTO jungle.

Read the rest of this post...

Comments Off on HP BTO Software Centers – Overview

Klaus OttoKlaus Otto Business Technology Optimization (BTO)

07/22/2008 by Klaus Otto

The New Role of IT
For many years, all IT departments seem to have taken up the cause of cost reducing. This has changed. Business managers more and more consider IT a lever for boosting growth. Particularly, this means for IT departments to implement new business models and concepts as fast as possible.

Read the rest of this post...

Comments Off on Business Technology Optimization (BTO)

Marco GerussiMarco Gerussi Project Roadmap: Quick Wins with Iterations

07/17/2008 by Marco Gerussi

My blog Scoping – A Guarantee for Success through Harmonized Expectations describes how to identify factors that are most relevant to the success of the project:

Read the rest of this post...

1 Comment »

Peter HelfensteinPeter Helfenstein Forrester: HP is Number 1 for Functional Testing

07/14/2008 by Peter Helfenstein

According to then most recent Forrester Wave Report dating July 8, 2008 on Functional Testing solutions HP clearly keeps on leading this market.

Read the rest of this post...

3 Comments »

Michael LoebbertMichael Loebbert A Strategy is a Story

07/02/2008 by Michael Loebbert

As a reminder of what a strategy is and what it should provide:

Read the rest of this post...

Comments Off on A Strategy is a Story

Marco GerussiMarco Gerussi Project Scoping – Aligning Expectations

07/01/2008 by Marco Gerussi

Projects often fail to be successful due to diverging, badly aligned expectations
Dozens of statistics seem to suggest that there are dozens of reasons why projects fail to be successful. However, a great deal of them are attributable to vaguely defined objectives, problems related to technical architecture and a lack of management support. These causes, in turn, are in most cases due to either too optimistic or diverging expectations of the parties involved. Very often, projects are initiated without having identified and documented expectations as well as requirements on the part of all expert and management key roles.

Read the rest of this post...

2 Comments »

Fritz MosonyiFritz Mosonyi Software Archeology – how to Successfully Change SAP Releases

06/30/2008 by Fritz Mosonyi

16th century. The eyes of an archeologist are scanning a field. He is asking himself where he should start digging. In his life, he still has a few years left. Which area would, from his experience, hold a chance for him to make a discovery? Then he notices a tree. For growing, it would need nutrients, so underneath there might be something. This is what he knows from experience.

Read the rest of this post...

1 Comment »

Marco GerussiMarco Gerussi SAP Change Impact Management – PHW Business School and beteo study

06/30/2008 by Marco Gerussi

In collaboration with the PHW Business School, Zurich, Switzerland we are conducting  a study in the IT Change Impact Management area.

Read the rest of this post...

Comments Off on SAP Change Impact Management – PHW Business School and beteo study

Dieter SteigerDieter Steiger Configuration Management for SAP Customizing?

06/27/2008 by Dieter Steiger

A comprehensive configuration management is the most important basis of SAP Change and Transport Management. For ABAP code, this is accepted as general practice and supported by suitable tools. But how about configuration management for SAP customizing?

Read the rest of this post...

2 Comments »

Marco GerussiMarco Gerussi Proof of Concept – Less Risk for System Implementations

06/26/2008 by Marco Gerussi

Scoping for defined requirements and harmonized expectations
The scoping approach allows you to define requirements, expectations and project scopes when systems, methods and processes are implemented. This results in aligned expectations, a well-designed system architecture, defined requirements as well as a structured implementation roadmap. If the roadmap is implemented in several iterations, quick wins are achieved in addition to a direct benefit to the project client and the users.

Read the rest of this post...

1 Comment »