| Title: |
The Modernization Roadmap |
| Author: |
David Sprott |
| Publication Date: |
26 February 2010 |
| Report Type: |
Journal |
| Report Class: |
Best Practice |
| Abstract: |
Modern applications must be business driven, agile, service oriented and componentized. To deliver on these objectives requires coordination of many disciplines across the enterprise and its ecosystem of suppliers, customers and partners to implement new practices and skills. This level of change will not happen overnight; it will be introduced as part of business facing projects on a progressive basis over time. What’s needed is a structured approach to manage and govern that change to ensure the broader organizational objectives are not compromised by specific project constraints. We call this approach the Modernization Roadmap. |
| Backgrounder: |
The typical organization today is somewhat chaotic. We all thrive on continuous change and at any point in time there will always be projects introducing new tools, new products and technologies. However some types of change are different; they are bigger than any new tool or technology. They affect the way the organization does business in a very profound manner and have all sorts of impacts right across the organization. For these changes we need a roadmap that can coordinate change. Without it, the level of chaos represents a very significant business risk.
If you are reengineering a single application from a legacy language like COBOL to Java, you probably don’t need a roadmap; you need a project plan. If however you have broader, business based objectives you need to plan for practice and process improvement. |
| Report Size: |
9 pages |
| Report Access Type: |
 | Silver/Gold (Premium) |
|
| Available for separate purchase |
Single copies of recent CBDI Journals may be purchased |
| Login |
|
Home