TECHNOLOGY

MANAGEMENT
ROAD MAPPING
CHAPTER 10
 Group 1
Safeera Azhar 20010856-002
Kainat 20010856-011
Farzeen Walayat 20010856-009
Zunaira Tariq 20010856-007
 Technology Road
Mapping (TRM)
•A technology roadmap is a display, document, or diagram
that illustrates the technology adoption plan at a given
organization. Technology roadmaps are created to help
business leaders plan and strategize which, when, and
why certain technologies will be on boarded while
avoiding expensive mistakes and even planning for
technologies becoming obsolete.
•An effective technology roadmap should also outline a
strategy to reach short- and long-term digital
transformation goals, if applicable.
 Technology Road Mapping (TRM)

•There are many methods and models for technology road mapping. However,
this type of visual usually falls into two categories:

 IT Systems Roadmaps
 Technology Roadmaps
 IT Systems Roadmap
• An IT systems roadmap is a diagram or model designed to set the parameters that
enable key functioning across the business or organization. An effective IT roadmap
will lay out current IT capabilities, projected IT needs, and any improvements you
plan to make to execute against your business strategy. Generally, IT roadmaps are
meant to communicate plans about the major systems that keep your business
running.
• These systems include, but are not limited to, customer relationship management
systems (CRM), enterprise resource planning systems ( ERP), data analytics systems,
identity management systems, cyber security systems, and more.
 Technology Roadmap
• A technology roadmap illustrates the technology presently
available and emphasizes scheduled improvements. A technology
roadmap should also consider which technologies will become
obsolete or are scheduled for end of life. For example, a work
management software system will show when the previous system
will sunset and when the new one will be implemented.
• As organizations lay out their strategy and implementation to help
execute on their vision, a technology roadmap will help them
determine which technologies to invest in and now to implement
them. Technology roadmaps should enable technological
infrastructure improvements to meet both long-term and short-
term targets of the business or organization in mind.
 Why do you need a Technology Roadmap?

•The overall function of a technology roadmap is to align

your target stakeholders, like IT, software engineering,
operations executives, and even sales teams, by creating a
course of action to onboard new technology solutions or
maintain existing ones.
•This method helps teams visualize, prepare for, and
execute the desired outcomes for the organization.
Creating a thorough technology roadmap gives you the
ability to:
 Why do you need a Technology Roadmap?

Have a clear picture of your company's IT infrastructure abilities and

how they align with business outcomes.
Address any current it issues.
Cut costs by removing any unnecessary technologies and applications.
Increase productivity by implementing technology that serves your
immediate needs.
Improve it and cyber security.
Avoid or mitigate against system failures by learning any weaknesses
in your it infrastructure.
Resolve any conflicts around business priorities.
Prepare for digital transformation.
Key components of a technology roadmap

Goals: New system Release

capabilities: plans:
Your technology or IT These are the new Release plans highlight
roadmap should capabilities provided the requirements to
include both long-term by the implementation enhance the systems
and short-term goals of the technology to support new
that the business or enhancement. As an capabilities provided
organization wishes to example, adding a by the new technology.
achieve through the chatbot to a customer- They are generally
technology facing platform like a predictable and may
implementation. website or mobile app be scheduled months
will provide scalability in advance. Release
and enhance both plans should be shared
inbound and outbound throughout the
marketing strategies. business or
organization.
 Key components of a technology
roadmap
Resources: Training:
Milestones:
• Resources exhibit the Whenever rolling out
Milestones are the key time, capital, energy, a new technology
benchmarks achieved and personnel needed system, a training
in the technology to onboard new period must take place
onboarding process. technol --goes and to ensure that
When stakeholders maintain existing personnel is adopting
track milestones, they technology systems. the new system
can assess and For example, IT teams efficiently. In fact, your
understand the must plan how to technology/IT
progress toward their simultaneously roll out roadmap should
long-term goals, plus a new operating always account for
evaluate the success of system while updating training time, as
the new technology in existing systems as training includes the
achieving those goals. needed. guidance needed for
internal teams to
adopt and support a
new system.
 Key components of a technology
roadmap
Risk factors: Status reports:

• Risk factors describe the • Status reports are necessary

potential internal or external to keep all relevant
threats that may prevent stakeholders abreast and
successful implementation of informed of the progress of
new technologies. Risk the new technology adoption.
factors may include
limitations in the technology
itself, difficulty adopting the
new technology such as a
substandard user interface,
or market disruptions that
affect the needs and goals of
the business or organization.
PROCESS
Developmen
Preliminary t phase
phase

Follow-up
activities
 PRELIMINARY PHASE

IN THIS PHASE THE KEY DECISION MAKERS MUST IDENTIFY THAT THEY HAVE A
PROBLEM AND THAT TECHNOLOGY ROAD MAPPING CAN HELP THEM IN SOLVING
THE PROBLEM
Satisfy
essential
conditions

Preliminar
y phase

Provide Scope and

leader-ship boundaries
 PRELIMINARY PHASE
o SATISFY ESSENTIAL CONDITIONS Click icon to add picture
IN THIS STEP IT MUST BECOME CLEAR WHAT THE
CONDITIONS ARE (THEY MUST BE IDENTIFIED) Identify essential conditions
AND IF THEY ARE NOT MET, WHO TAKES ACTIONS
TO MEET THEM. THESE CONDITIONS INCLUDE,
FOR EXAMPLE:
 A NEED FOR THE TECHNOLOGY ROADMAP else
 INPUT AND PARTICIPATION FROM DIFFERENT Needs
PARTS OF THE ORGANIZATION (E.G., All conditions
satisfied Take actions to satisfy Participation
MARKETING, R&D, THE STRATEGIC BUSINESS conditions

UNITS) WITH DIFFERENT PLANNING HORIZONS Planning horizons

AND PERSPECTIVES.
ALL CONDITIONS SHOULD BE SATISFIED (OR AN
AGREED-ON PARTY TAKES NECESSARY ACTIONS) Move to next step
TO CONTINUE TO THE NEXT STEP IEEI.
 Click icon to add picture
PRELIMINARY PHASE
o PROVIDE LEADERSHIP
provides
COMMITTED LEADERSHIP IS NEEDED BECAUSE OF THE
TIME AND EFFORT INVOLVED IN CREATING A All essential
Leadership/sponsorship
TECHNOLOGY ROADMAP. ADDITIONALLY THE conditions,
LEADERSHIP SHOULD COME FROM ONE OF THE
PARTICIPANTS, ONE OF THEM PROVIDES LEADERSHIP
AND SPONSORSHIP. THIS MEANS THAT THE LINE
ORGANIZATION MUST DRIVE THE PROCESS AND USE THE
ROADMAP TO MAKE RESOURCE ALLOCATION DECISIONS. Move to next step
 DEFINE THE SCOPE AND BOUNDARIES FOR THE
TECHNOLOGY ROADMAP

CHECK IF VISION EXISTS IN THIS STEP THE CONTEXT FOR THE

ROADMAP IS SPECIFIED. IN THE COMPANY A
VISION SHOULD EXIST AND IT MUST BE
Vision else CLEAR THAT THE ROADMAP CAN SUPPORT
exists THAT VISION. IF THE VISION DOES NOT EXIST
ONE SHOULD BE DEVELOPED AND CLEARLY
Clearly state STATED.
vision
Develop and state
vision
• WHEN THAT IS DONE THE BOUNDARIES
AND THE SCOPE OF THE ROADMAP vision
SHOULD BE SPECIFIED. FURTHERMORE.
No
THE PLANNING HORIZON AND THE
LEVEL OF DETAILS SHOULD BE SET yes Scope
define scope

Technology Participatio
boundaries define boundaries
scope n scope
 THE SECOND PHASE, THE DEVELOPMENT OF
THE TECHNOLOGY ROADMAP PHASE
Specify the major technology CONSISTS OF 7 STEPS:
areas

Specify the technology drivers and

their targets,

Identify technology alternatives and their

timelines

Recommend the technology alternatives that

Development phase should be pursued

Create the technology roadmap report

 Click icon to add picture

Development phase

 SPECIFY THE MAJOR TECHNOLOGY AREAS Transform requirements into

These are the areas that help achieve critical system technology oriented drivers
requirements. For each technology area several
technologies can be found. Example technology
areas are:
Market assessment, crosscutting technology, Move to next step
component development, and system development.
 Click icon to add picture

Development phase

 SPECIFY THE TECHNOLOGY DRIVERS AND Select technology

THEIR TARGETS alternatives

In this step the critical system requirements from the second

step are transformed into technology drivers (with targets) for
the specific technology area. These drivers are the critical Move to next step
variables that select the technology alternatives.
 Click icon to add picture

Development phase
 IDENTIFY TECHNOLOGY ALTERNATIVES AND THEIR Identify alternatives and
TIMELINES their Timeline

At this point the technology drivers and their targets are

specified and the technology alternatives that can satisfy
those targets should be specified. For each of the
alternatives a timeline should be estimated for how it
Move to next step
will mature with respect to the technology driver targets
 Click icon to add picture

Development phase
Select subset of technology
 RECOMMEND THE TECHNOLOGY ALTERNATIVES THAT alternatives that should be
SHOULD BE PURSUED pursued

Because the alternatives may differ in costs, timeline, etc., A selection

must be made of the alternatives. These are the alternatives to pursue.
In this step a lot of trade-offs must be made between different Move to next step
alternatives for different targets: for example, performance over -osts
and even target over target ieei
 Follow-UP activity phase
This is the moment when the roadmap must be critiqued, validated and hopefully
accepted by the group involved in any implementation. This requires a plan developed
using the technology roadmap. Next, there must be a periodical review and update point,
because needs from the participants and the technologies evolve.
 Technology Roadmapping Application Areas
Technology road mapping term is very flexible and the terms "product" or busniess roadmapping may be
more appropriate for many of its potential users

PRODUCT Service /
Strategic Long-range Programme
PLANNING capability
planning planning planning
planning
This is far the most Similar to Type 1 Includes a
common type of (product strategic Implementatio
technology planning), but dimension, in Extends the n of strategy
roadmap, relating to more suited to terms of planning time and more
insertion of
service-based supporting the horizon, and is directly relates
technology into often performed to project
manufactured
enterprises, evaluation of
focusing on how different at the sector or planning (for
products, often
technology opportunities or national level example,
including more than
one generation of supports threats, typically ('foresight' ) . R&D
product organizational at the business programmes).
capabilities. level.