- Alignment
- Agility
- Value for money
- Vendor independence
- Complexity
- Quality
Alignment is by far the most difficult and most important challenge. The problem with alignment is that it is only after SW/IT systems has been designed, developed, deployed and considerably used , it can be known whether it really meets customer needs. It is difficult to measure or quantify alignment, specially before the actual usage of SW.
Any SW development process should be a process of dialogue between SW development team and customers. This process of engagement has to be driven by SW development team. Although, both business and IT side are responsible for alignment, IT side who should take the prime responsibility for alignment. They must drive and engage the customers in a process of continuous dialogue for understanding business current and future needs and pain points. The continuation of dialogue through out IT life cycle is key to alignment. In fact IT service provider should become the part of the customer organizations.
Cognizant technologies is a US based company with development centers at Bangalore and other places. . It has a innovative customer engagement process which it calls -Two-in-a-Box™ (TiB
"Using a proprietary client engagement model called Two-in-a-Box™ (TiB), we embed personnel with demonstrated domain experience within the client organization to help drive IT strategy and ensure alignment with business objectives"
Here world embed is the key. If an IT service provider has to really understand customer business and IT requirements, its personnel should become the part of the customer organization. It should take both inside-out and out side -in view of the customers business and IT environment.
In order to understand customers business and IT environment , it is important to look into customers business and IT systems from different perspective. There are two IT framework which can used for this purpose - IEEE 1471 and John Zackman framework for EA . According to IEEE 1471, a systems has multiple stakeholders who look at the systems from different point of view. Each stakeholders has different concerns, needs and expectations from the systems. In order to understand the system, we need to create a view of the system from each stakeholders point of view. It is easier to define a systems into multiple views instead trying to describe a system in one large complex view. Once different views of the systems has been created, conflicts among them can be resolved. Views can also be created for different concerns - security, compliance, performance etc.
Another framework which can be used to define an enterprise/IT systems is good old framework for EA from John Zackman . This framework simply ask 6 W questions - What, Why, Who, When, Where and HoW from perspective of different stakeholders . The present state of Zackman framework is shown in the following figure -
Each row in Zackman framework describe in an enterprise/system in totality from the perspective of a single stakeholders. Zackman framework can also be used for enterprise agility. As we move across a column- from top to bottom, the artifacts in each cell should be based upon the artifact in the upper cell. This ensure traceability from business needs to code level. It is this traceability which provides agility.We will have a detailed looked into agility challenge in next post.
