Sign for Notice Everyday    Sign Up| Sign In| Link| English|

Our Sponsors

    Receive Latest News

    Feedburner
    Share Us


    Building an Information Technology Roadmap - Webinar By EITAGlobal

    View: 435

    Website http://bit.ly/Vbhmvz | Want to Edit it Edit Freely

    Category Information Technology; TOGAF; Enterprise Architecture (EA); Online IT training;

    Deadline: September 22, 2014 | Date: September 23, 2014

    Venue/Country: ONLINE, U.S.A

    Updated: 2014-08-11 16:24:21 (GMT+9)

    Call For Papers - CFP

    Overview: All enterprises, except the smallest ones, need to define, control and execute a series of actions or projects to support the business with appropriate information technology and systems.

    A good IT roadmap needs to meet several demanding requirements:

    It must be sufficiently high-level to be discussed with business stakeholders

    Each action/project must have a clear justification

    It needs to be realistic - you cannot do everything at once

    It needs to be clear and detailed enough for IT people so they can clearly understand what to do to fulfill it

    It must evolve as conditions change, and it must be kept up-to-date through these changes

    It needs to incorporate the capabilities offered by new technologies without seeming to be "technology for technology's sake"

    A roadmap driven by an understanding of Enterprise Architecture (EA) allows IT to describe and maintain the connection between the various levels of concern: business capabilities and business processes, business systems/applications, and the technical infrastructure. Therefore, it allows the organization to justify and prioritize each IT project. The development of the actual roadmap is a serious and intense exercise - something that may take at minimum a couple of person-months, and much more if there is little prior information about the existing portfolio and the business requirements. In this webinar, we describe a systematic approach that allows the development of the roadmap.

    Depending on the existing level of knowledge, a systematic education effort may need to be provided on the concepts and frameworks for Enterprise Architecture, including Zachman and TOGAF. In particular, the TOGAF Architecture Development Method (ADM) is usually relevant to most organizations. At the same time, TOGAF is a very complex framework, and it is not necessary to master it in its entirety to correctly define an IT roadmap.

    Next, the entire IT organization, as well as its business partners, and in particular the people who will be tasked with developing the roadmap, need to understand, tailor if necessary, and document the various levels of the enterprise architecture, starting with the business strategy and the value streams at the top, and going all the way to the infrastructure layers. There will be IT roadmap elements at almost every level, except the top-most ones which are the responsibility of the executive management, but everything else needs to be well positioned and well aligned in the roadmap.

    The outcome of the process should be (a) a living document, easy to communicate and review, that both the business and IT can use to prioritize and monitor their actions, (2) a list of "follow-on" projects that will need to be performed in order to place the entire range of IT efforts on a solid basis; these projects may include the institution of a Product/Project Portfolio Management system, the creation of a business process center of excellence, the convergence of multiple redundant systems, the retirement of legacy systems, the externalization of certain capabilities (outsourcing, cloud, or BPO), the creation of an Enterprise Architecture Program, a Master Data Management program, a technology watch program, and more.

    Why should you attend: All enterprises, except the smallest ones, need to define, control and execute a series of actions or projects to support the business with appropriate information technology and systems. Several difficulties immediately appear when the CIO or IT Manager attempts to define such a roadmap:

    How do you take the business strategy, as defined by C-level executives, and derive from it a set of actions?

    How do you engage with business people to review and agree on that roadmap, given that business managers often do not understand the technology, IT people do not speak in business terms?

    How do you deal with the ever-increasing complexity of IT?

    How do you handle legacy systems, especially after mergers and acquisitions?

    A good IT roadmap needs to meet several demanding requirements:

    It must be sufficiently high-level to be discussed with business stakeholders

    Each action/project must have a clear justification

    It needs to be realistic - you cannot do everything at once

    It needs to be clear and detailed enough for IT people so they can clearly understand what to do to fulfill it

    It must evolve as conditions change, and it must be kept up-to-date through these changes

    It needs to incorporate the capabilities offered by new technologies without seeming to be "technology for technology's sake"

    Many organizations conduct projects in isolation from each other, without having a clear view of where they are going. With this approach, you can run in circles or hit a wall. Other organizations dive down immediately to the level of detailed project plans, which are useless beyond a short-term horizon. Yet others have an IT roadmap or plan that is disconnected from the business strategy and requirements, so that it is hard to justify the cost of the projects to the business. Clearly, a more systematic and well-grounded approach is required.

    Areas Covered in the Session:

    Introduction

    Challenge and Objective of a Roadmap

    Key Enterprise Architecture concepts

    Obtaining business inputs

    Value streams or end-to-end processes

    Business capabilities

    Business system evolution and convergence

    Technical Architecture elements of the roadmap

    Creating the Roadmap: practical advice

    Execution and governance

    Follow-on projects

    Who Will Benefit:

    CIO

    IT Manager (reports to CIO)

    Business Architect

    Enterprise Architect

    Senior IT Consultants

    IT Project Managers

    Project Management Office (PMO)

    Speaker Profile:

    Claude Baudoin has 39 years of experience in IT Management, Software Engineering Management, and Knowledge Management (KM) in an international context, including the semiconductor, Oil & Gas, and IT services sectors. He is a recognized innovator and educator who has authored two books and two patents, and written many articles and papers on IT and KM subjects.

    For further information about the event, cost and registration please contact to +1 800 447 9407 to have your seats confirmed.

    Contact Information:

    Event Coordinator

    James Richard

    Toll free: 1800 447 9407

    Fax: 302 288 6884

    Email: webinarsateitaglobal.com

    Website: https://www.eitaglobal.com/

    EITAGlobal

    NetZealous LLC,

    161| Mission Falls Lane| Suite 216, Fremont| CA 94539


    Keywords: Accepted papers list. Acceptance Rate. EI Compendex. Engineering Index. ISTP index. ISI index. Impact Factor.
    Disclaimer: ourGlocal is an open academical resource system, which anyone can edit or update. Usually, journal information updated by us, journal managers or others. So the information is old or wrong now. Specially, impact factor is changing every year. Even it was correct when updated, it may have been changed now. So please go to Thomson Reuters to confirm latest value about Journal impact factor.