SlideShare a Scribd company logo
1 of 12
Implementation roadmap
The implementation roadmap is presented in this section in table. The tables contain the initiatives according to their implementation priority. There are
four level of priorities. At each level and for each initiative, key activities that should be taken are shown in the tables.
Table 1: priority level1
Critical Success Factor: Priority level1
This initiative is a Critical Success Factor (CSF) to implement the rest of the initiatives successfully. This is the first initiative that should be implemented. This
initiative should be started and implemented in 1 month.
Initiative Sub-Initiative Time of
achievement
Key activities Responsibility
Create
a
Project
Management
Office
(PMO)
None 3 - 6 weeks 1. Appoint relevant staff to the Project Management Office and ensure that an IT
representative is part of the PMO.
2. Develop a Project Management Policy and its underlying procedures
3. Develop a library of Project Management Materials
-Project Plan templates
-Business case templates
-Project Management tools
4. Select Technology to facilitate the Project Management policy and procedures as
well as the tracking and benefits realization of projects.
5. Utilize the PMO to manage the implementation of the initiatives highlighted in the
remainder of the roadmap.
1. Business
2. IT Department
STRATEGIC OBJECTIVE : Creation of PMO
Table 2: Priority level2
Priority level2
This initiative is crucial to improving the state of IT. Initiatives marked red should be started within 1 – 3 months of the IT strategy approval and
implementation.
Initiative Sub-Initiative Time of
achievement
Key activities Responsibility
1. Establish an
ICT steering
committee
None 1 - 6 weeks 1.1. Appoint staff to the ICT steering committee, including representatives from
both business and IT at the executive, senior and operational levels.
2. Business
3. ITDepartment
2.
Implement
an
IT
Governance
Framework
2.1 Implement
Governance
frameworks and
procedures for IT
decision making
3 – 6 Months 2.1.1. Review and update the current governance framework and ensure it is aligned
to the overall Corporate Governance Framework.
2.1.2. Implement the IT Governance framework:
a) Communicate the implementation of the IT Governance Framework
b) Enforce compliance with the procedures defined in the IT
Governance framework
c) Monitor compliance and take corrective action as defined in the IT
Governance framework
2.1.3. Define and Implement data governance policies and procedures
a) Assign ownership of data and information within the organisation
b) Classify the data of organisation
c) Define system specific access levels for each data category
d) Review current access rights on the system
e) Implement and align access rights to data classifications
f) Implement periodic review procedures for user access on the
organisation systems
2.1.4. Appoint an ICT Steering Committee
2.1.5. Define and implement an IT Department organisational structure
a) Clearly define and document roles and responsibilities of members of the
IT department
b) Appoint an IT Operations Manager to oversee operations and report to the
CIO
c) Structure performance management around documented roles and
responsibilities.
2.1.6. Define and implement risk management policies and procedures that are
integral to the existing business and decision making processes.
 Business
 ITDepartment
 PMO
Priority level2
This initiative is crucial to improving the state of IT. Initiatives marked red should be started within 1 – 3 months of the IT strategy approval and
implementation.
Initiative Sub-Initiative Time of
achievement
Key activities Responsibility
2.2. Implement
Governance
frameworks and
procedures for IT
Operations
6 – 48 Months 2.2.1. Implement Service Level Management
a) Define and implement Service Level Agreements between business and IT.
b) Define and implement standard operating procedures for the processes within
the IT department.
c) Define and implement OLAs between the units within the IT department.
d) Monitor performance against the agreements and make improvements and
amendments where necessary.
2.2.2. Implement IT financial management with specific focus on costs vs. performance.
2.2.3. Implement Capacity Management
a) Review and document the current capacity of IT and what it is able to deliver.
Address both infrastructure and people capacity and capability.
b) Define and implement a capacity management process, including the capacity
aspects that will be monitored. (e.g. bandwidth usage, server storage and
processing).
c) Implement training programmes for IT personnel to build skills where
necessary.
STRATEGIC OBJECTIVE 1: IT Governance
Table 3: priority level3
Priority level3
This initiative is important to improving the state of IT. Initiatives marked orange should be started within 3 – 6 months of the IT strategy
approval and implementation.
Initiative Sub-Initiative Time of
achievement
Key activities Responsibility
Implementation
of
IT
governance
framework
2.2. Implement
Governance
frameworks and
procedures for IT
Operations
6-48 Months 2.2.4. Implement IT Service Continuity Management
a) Implement and adhere to a defined backup procedure which specifically
outlines the backup frequency.
b) Test the restore functionality of the backups on a regular basis.
c) Define and implement an IT Disaster Recovery plan in conjunction with
the business continuity plan. The focus should be on the mission-critical
systems and data with well-defined RPO’s and RTO’s.
2.2.5. Implement Availability Management
a) Agree on availability percentages and system downtime thresholds with
business.
b) Define and implement an availability management procedure taking into
account the availability percentages agreed upon. This is closely related
to service continuity and service level management.
2.2.6. Implement Service Desk Management
a) Define incident categories and resolution timeframes for each category.
b) Monitor and report on call resolution statistics. Have discrepancy
reports for incidents that are open out of their resolution timeframe.
c) Provide users with feedback on the status of calls logged throughout the
resolution process.
 Business
 IT Department
 ICT Steering
Committee
 PMO
STRATEGIC OBJECTIVE : IT Governance
Priority level3
This initiative is important to improving the state of IT. Initiatives marked orange should be started within 3 – 6 months of the IT strategy
approval and implementation.
Initiative Sub-Initiative Time of
achievement
Key activities Responsibility
1. Business
process
Integration
None 6 – 12 months 1.1 Define and document business processes, their integration requirements and
how IT can facilitate the integration processes
1.2 Assess the current legacy applications and systems in place and their ability to
meet the defined business requirements.
a) If legacy applications meet the business requirements, implement
adequate system integration them as per business requirements.
b) If the legacy application can no longer fully meet the business
requirements or integration requirements, investigate procuring a system
that meets the business and integration requirements.
 Business
 IT Department
 ICT Steering
Committee
 PMO
8. Information
security
3 – 18 months 8.1.1. Review all existing information security policies at the G3 CONSULTING and
consolidate policies where necessary.
8.1.2. Gain top management buy-in to security practices becoming part of daily
routine and raise awareness around security practices.
8.1.3. Define and implement security awareness training programmes for the end
users within the organisation in order to ensure that security awareness is
instilled in their daily job routines.
8.1.4. Ensure adequate physical access, logical access and environmental controls
are in place to mitigate risks to the organisation network and information
assets.
8.1.5. Define and implement network monitoring procedures in order to detect
potential vulnerabilities and threats, as well as compliance to the information
security standards and procedures.
8.1.6. Define and implement formalised antivirus and patch update methodologies.
Conduct regular internal and specialist external security reviews.
 Business
 IT Department
 ICT Steering
Committee
 PMO
Priority level3
This initiative is important to improving the state of IT. Initiatives marked orange should be started within 3 – 6 months of the IT strategy
approval and implementation.
Initiative Sub-Initiative Time of
achievement
Key activities Responsibility
STRATEGIC OBJECTIVE 3: Convergence
9. Harnessing Big
data
None 3-6 months 1.3 Show value in the data that the organisation currently has. Develop different
ways to present this data in meaningful and valuable ways in order to garner buy-
in for the business intelligence initiative.
1.4 Clean, restructure and consolidate existing data
1.5 Identify which data will be the most valuable for reporting and evaluation and
implement the reporting and evaluation processes and dashboards.
1.6 Use the data and dashboards to make strategic decisions and to evaluate the
effectiveness and popularity of different products and services offered by the
organisation.
 Business
 IT Department
 ICT Steering
Committee
 PMO
11. Empower
Business personnel
with IT knowledge
and IT trend
awareness
None 3-6 months 11.1 Provide awareness to key personnel around the latest technological
innovations in the IT industry and how these are applicable to the organisation
from a strategic perspective.
11.2 Empower end users with the knowledge, skills and understanding to
fully harness the potential of their IT equipment, systems and applications to
make their daily job functions more efficient and effective.
 Business
 IT Department
 ICT Steering
Committee
 PMO
12. Empower IT
personnel with
Business Knowledge
None 3-6 months Provide awareness to the IT personnel of the business processes they are
supporting and the criticality of the IT operations and support in enabling
these processes to occur.

STRATEGIC OBJECTIVE 4: Innovation and Technology Enablement
Table 4: Priority level 4
Priority level4
This initiative is important to improving the state of IT, but can afford to be started at a later stage. Initiatives marked yellow should be started within 6 – 12
months of the IT strategy approval and implementation
Initiative Sub-Initiative Time of
achievement
Key activities Responsibility
Implement
an
IT
Governance
Framework
2.2 Implement
Governance
frameworks and
procedures for IT
Operations
3 - 6 weeks 2.2.7. Implement Configuration Management
a) Document the current configuration details of all hardware and software
components utilised at the organisation and store this as the start of the
Configuration Management Database.
b) Document interdependencies between Configuration Items.
c) Compare these configuration settings to industry best-practice and
ensure that the CI’s are aligned where applicable.
2.2.8. Define and implement Change Management Procedures
a) Define and document the types of changes that could occur (Standard,
normal or emergency)
b) Define and document the change management procedures and approval
process for each of these changes
c) Establish a Change Committee responsible for approving changes
d) Define and standardise a change request template that incorporates
impact and risk assessments of the proposed change.
2.2.9. Implement Release Management Procedures
a) Define and implement processes to take inventory of software installed
on all devices within the organisation. All subsequent changes and
updates to this software should be recorded.
b) Define and implement processes to adequately test software changes
prior to their deployment.
Priority level4
This initiative is important to improving the state of IT, but can afford to be started at a later stage. Initiatives marked yellow should be started within 6 – 12
months of the IT strategy approval and implementation
Initiative Sub-Initiative Time of
achievement
Key activities Responsibility
6-48 Months 2.2.10. Implement Release Management Procedures
a. Define and implement processes to take inventory of software installed on all
devices within the organisation. All subsequent changes and updates to this
software should be recorded.
b. Define and implement processes to adequately test software changes prior to
their deployment.
c. Implement procedures to ensure documentation of software testing and
deployment is kept and lessons learned are noted.
STRATEGIC OBJECTIVE : Creation of PMO
3. IT Sourcing
Strategies
1-6 months 3.1. Define the business requirements and IT requirements.
3.2. Identify IT functions that are not core operations that could be outsourced to
a vendor which includes vendor support.
3.3. Define and implement vendor management processes which entail managing
and monitoring the performance of the vendor as per agreed upon KPIs.
3.4. Select appropriate vendors for the functions to be outsourced and define KPIs
in line with business and IT requirements to monitor the vendor against.
Monitor, review and report on vendor performance and amend where necessary.
 Business
 IT Department
 ICT Steering
Committee
 PMO
Priority level4
This initiative is important to improving the state of IT, but can afford to be started at a later stage. Initiatives marked yellow should be started within 6 – 12
months of the IT strategy approval and implementation
Initiative Sub-Initiative Time of
achievement
Key activities Responsibility
4.Cloud
computing
none 1-3
months
4.1. Investigate the potential cost reduction benefits of implementing a SaaS cloud
computing model to host certain applications such as CRM and SharePoint.
4.2. If feasible, select an appropriate external service provider as per the external
vendor management process.
 IT Department
 ICT Steering
Committee
 PMO
5. IT Asset
Management
none 1-3
Months
5.1. Investigate the number of devices that are operating on different hardware
and software platforms.
5.2. Evaluate and select the most feasible hardware and software platforms from
a risk and cost perspective.
5.3. Develop a platform migration plan to get all devices operating on the selected
standard hardware and software platforms.
Define and implement a BYOD policy which allows only approved and secured
devices to connect to the organisation network.
STRATEGIC OBJECTIVE 2: Cost Effectiveness
6. Platform
Standardization
none 1-12
months
6.1. Investigate the number of devices that are operating on different hardware and
software platforms.
6.2. Evaluate and select the most feasible hardware and software platforms from a risk
and cost perspective.
6.3. Develop a platform migration plan to get all devices operating on the selected
standard hardware and software platforms.
Define and implement a BYOD policy which allows only approved and secured
devices to connect to the organisation network.
Priority level4
This initiative is important to improving the state of IT, but can afford to be started at a later stage. Initiatives marked yellow should be started within 6 – 12
months of the IT strategy approval and implementation
Initiative Sub-Initiative Time of
achievement
Key activities Responsibility
STRATEGIC OBJECTIVE 3: Convergence
10. Innovation
Initiatives
Mobile
technologies,
eLearning,
Corporate
Partnerships
3-6
months
1.7 Investigate the market need for and benefits of investing in
mobile technologies and applications for service and content
delivery.
1.8 Investigate the market need for and benefits of investing in
eLearning technologies and partnerships for service and content
delivery.
Investigate partnering with various government departments and other organisations
in order to leverage new technologies and provision thereof.
STRATEGIC OBJECTIVE 4: Innovation and Technology Enablement

More Related Content

Similar to Implementation roadmap.docx

Clint Britt _ Six Sigma Project _ MFP_ June2016
Clint Britt _ Six Sigma Project _ MFP_ June2016Clint Britt _ Six Sigma Project _ MFP_ June2016
Clint Britt _ Six Sigma Project _ MFP_ June2016Clint Britt
 
mis ch2.pptx
mis ch2.pptxmis ch2.pptx
mis ch2.pptxTeshome48
 
mis ch2.pptx
mis ch2.pptxmis ch2.pptx
mis ch2.pptxhabte11
 
How Monitoring the Development of Digital Transformation Programs.pdf
How Monitoring the Development of Digital Transformation Programs.pdfHow Monitoring the Development of Digital Transformation Programs.pdf
How Monitoring the Development of Digital Transformation Programs.pdfJose thomas
 
Telehealth capacity assessment tool introduction
Telehealth capacity assessment tool introductionTelehealth capacity assessment tool introduction
Telehealth capacity assessment tool introductionMike Wilhelm
 
Pmbok 5th executing process group
Pmbok 5th executing process groupPmbok 5th executing process group
Pmbok 5th executing process groupHossam Maghrabi
 
Development of information system chap 2
Development of information system chap 2Development of information system chap 2
Development of information system chap 2amanuelayde1
 
Asset Management Proposal
Asset Management ProposalAsset Management Proposal
Asset Management ProposalLyle Villarta
 
250250902-141-ISACA-NACACS-Auditing-IT-Projects-Audit-Program.pdf
250250902-141-ISACA-NACACS-Auditing-IT-Projects-Audit-Program.pdf250250902-141-ISACA-NACACS-Auditing-IT-Projects-Audit-Program.pdf
250250902-141-ISACA-NACACS-Auditing-IT-Projects-Audit-Program.pdfAddisu15
 
Chap3 2007 Cisa Review Course
Chap3 2007 Cisa Review CourseChap3 2007 Cisa Review Course
Chap3 2007 Cisa Review CourseDesmond Devendran
 
InfoTech - IT Governance.pptx
InfoTech - IT Governance.pptxInfoTech - IT Governance.pptx
InfoTech - IT Governance.pptxAjay Gangakhedkar
 
Jurnal an example of using key performance indicators for software development
Jurnal   an example of using key performance indicators for software developmentJurnal   an example of using key performance indicators for software development
Jurnal an example of using key performance indicators for software developmentRatzman III
 
02. cobit 41 dan iso 17799
02. cobit 41 dan iso 1779902. cobit 41 dan iso 17799
02. cobit 41 dan iso 17799Mulyadi Yusuf
 
Project Management for IT-related Projects (Logitrain)
Project Management for IT-related Projects (Logitrain)Project Management for IT-related Projects (Logitrain)
Project Management for IT-related Projects (Logitrain)Logitrain: New Zealand
 

Similar to Implementation roadmap.docx (20)

Clint Britt _ Six Sigma Project _ MFP_ June2016
Clint Britt _ Six Sigma Project _ MFP_ June2016Clint Britt _ Six Sigma Project _ MFP_ June2016
Clint Britt _ Six Sigma Project _ MFP_ June2016
 
Sdlc1
Sdlc1Sdlc1
Sdlc1
 
mis ch2.pptx
mis ch2.pptxmis ch2.pptx
mis ch2.pptx
 
CHAPTER FOUR.pptx
CHAPTER FOUR.pptxCHAPTER FOUR.pptx
CHAPTER FOUR.pptx
 
mis ch2.pptx
mis ch2.pptxmis ch2.pptx
mis ch2.pptx
 
How Monitoring the Development of Digital Transformation Programs.pdf
How Monitoring the Development of Digital Transformation Programs.pdfHow Monitoring the Development of Digital Transformation Programs.pdf
How Monitoring the Development of Digital Transformation Programs.pdf
 
Telehealth capacity assessment tool introduction
Telehealth capacity assessment tool introductionTelehealth capacity assessment tool introduction
Telehealth capacity assessment tool introduction
 
Pmbok 5th executing process group
Pmbok 5th executing process groupPmbok 5th executing process group
Pmbok 5th executing process group
 
It Audit
It AuditIt Audit
It Audit
 
Development of information system chap 2
Development of information system chap 2Development of information system chap 2
Development of information system chap 2
 
Asset Management Proposal
Asset Management ProposalAsset Management Proposal
Asset Management Proposal
 
250250902-141-ISACA-NACACS-Auditing-IT-Projects-Audit-Program.pdf
250250902-141-ISACA-NACACS-Auditing-IT-Projects-Audit-Program.pdf250250902-141-ISACA-NACACS-Auditing-IT-Projects-Audit-Program.pdf
250250902-141-ISACA-NACACS-Auditing-IT-Projects-Audit-Program.pdf
 
Chap3 2007 Cisa Review Course
Chap3 2007 Cisa Review CourseChap3 2007 Cisa Review Course
Chap3 2007 Cisa Review Course
 
IT Governance.pptx
IT Governance.pptxIT Governance.pptx
IT Governance.pptx
 
InfoTech - IT Governance.pptx
InfoTech - IT Governance.pptxInfoTech - IT Governance.pptx
InfoTech - IT Governance.pptx
 
Chap03
Chap03Chap03
Chap03
 
Jurnal an example of using key performance indicators for software development
Jurnal   an example of using key performance indicators for software developmentJurnal   an example of using key performance indicators for software development
Jurnal an example of using key performance indicators for software development
 
02. cobit 41 dan iso 17799
02. cobit 41 dan iso 1779902. cobit 41 dan iso 17799
02. cobit 41 dan iso 17799
 
PACMTN Portfolio1
PACMTN Portfolio1PACMTN Portfolio1
PACMTN Portfolio1
 
Project Management for IT-related Projects (Logitrain)
Project Management for IT-related Projects (Logitrain)Project Management for IT-related Projects (Logitrain)
Project Management for IT-related Projects (Logitrain)
 

Recently uploaded

Story boards and shot lists for my a level piece
Story boards and shot lists for my a level pieceStory boards and shot lists for my a level piece
Story boards and shot lists for my a level piececharlottematthew16
 
Gen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdfGen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdfAddepto
 
Install Stable Diffusion in windows machine
Install Stable Diffusion in windows machineInstall Stable Diffusion in windows machine
Install Stable Diffusion in windows machinePadma Pradeep
 
APIForce Zurich 5 April Automation LPDG
APIForce Zurich 5 April  Automation LPDGAPIForce Zurich 5 April  Automation LPDG
APIForce Zurich 5 April Automation LPDGMarianaLemus7
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024Lorenzo Miniero
 
DevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsDevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsSergiu Bodiu
 
Understanding the Laravel MVC Architecture
Understanding the Laravel MVC ArchitectureUnderstanding the Laravel MVC Architecture
Understanding the Laravel MVC ArchitecturePixlogix Infotech
 
Beyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry InnovationBeyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry InnovationSafe Software
 
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
"Federated learning: out of reach no matter how close",Oleksandr LapshynFwdays
 
Integration and Automation in Practice: CI/CD in Mule Integration and Automat...
Integration and Automation in Practice: CI/CD in Mule Integration and Automat...Integration and Automation in Practice: CI/CD in Mule Integration and Automat...
Integration and Automation in Practice: CI/CD in Mule Integration and Automat...Patryk Bandurski
 
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Commit University
 
Bun (KitWorks Team Study 노별마루 발표 2024.4.22)
Bun (KitWorks Team Study 노별마루 발표 2024.4.22)Bun (KitWorks Team Study 노별마루 발표 2024.4.22)
Bun (KitWorks Team Study 노별마루 발표 2024.4.22)Wonjun Hwang
 
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks..."LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...Fwdays
 
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...shyamraj55
 
costume and set research powerpoint presentation
costume and set research powerpoint presentationcostume and set research powerpoint presentation
costume and set research powerpoint presentationphoebematthew05
 
Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)
Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)
Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)Mark Simos
 
Unleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubUnleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubKalema Edgar
 
My INSURER PTE LTD - Insurtech Innovation Award 2024
My INSURER PTE LTD - Insurtech Innovation Award 2024My INSURER PTE LTD - Insurtech Innovation Award 2024
My INSURER PTE LTD - Insurtech Innovation Award 2024The Digital Insurer
 
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024BookNet Canada
 

Recently uploaded (20)

Story boards and shot lists for my a level piece
Story boards and shot lists for my a level pieceStory boards and shot lists for my a level piece
Story boards and shot lists for my a level piece
 
Gen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdfGen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdf
 
Install Stable Diffusion in windows machine
Install Stable Diffusion in windows machineInstall Stable Diffusion in windows machine
Install Stable Diffusion in windows machine
 
APIForce Zurich 5 April Automation LPDG
APIForce Zurich 5 April  Automation LPDGAPIForce Zurich 5 April  Automation LPDG
APIForce Zurich 5 April Automation LPDG
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024
 
DevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsDevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platforms
 
Understanding the Laravel MVC Architecture
Understanding the Laravel MVC ArchitectureUnderstanding the Laravel MVC Architecture
Understanding the Laravel MVC Architecture
 
Beyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry InnovationBeyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
 
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
 
E-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptx
E-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptxE-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptx
E-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptx
 
Integration and Automation in Practice: CI/CD in Mule Integration and Automat...
Integration and Automation in Practice: CI/CD in Mule Integration and Automat...Integration and Automation in Practice: CI/CD in Mule Integration and Automat...
Integration and Automation in Practice: CI/CD in Mule Integration and Automat...
 
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!
 
Bun (KitWorks Team Study 노별마루 발표 2024.4.22)
Bun (KitWorks Team Study 노별마루 발표 2024.4.22)Bun (KitWorks Team Study 노별마루 발표 2024.4.22)
Bun (KitWorks Team Study 노별마루 발표 2024.4.22)
 
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks..."LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
 
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
 
costume and set research powerpoint presentation
costume and set research powerpoint presentationcostume and set research powerpoint presentation
costume and set research powerpoint presentation
 
Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)
Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)
Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)
 
Unleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubUnleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding Club
 
My INSURER PTE LTD - Insurtech Innovation Award 2024
My INSURER PTE LTD - Insurtech Innovation Award 2024My INSURER PTE LTD - Insurtech Innovation Award 2024
My INSURER PTE LTD - Insurtech Innovation Award 2024
 
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
 

Implementation roadmap.docx

  • 1. Implementation roadmap The implementation roadmap is presented in this section in table. The tables contain the initiatives according to their implementation priority. There are four level of priorities. At each level and for each initiative, key activities that should be taken are shown in the tables. Table 1: priority level1 Critical Success Factor: Priority level1 This initiative is a Critical Success Factor (CSF) to implement the rest of the initiatives successfully. This is the first initiative that should be implemented. This initiative should be started and implemented in 1 month. Initiative Sub-Initiative Time of achievement Key activities Responsibility Create a Project Management Office (PMO) None 3 - 6 weeks 1. Appoint relevant staff to the Project Management Office and ensure that an IT representative is part of the PMO. 2. Develop a Project Management Policy and its underlying procedures 3. Develop a library of Project Management Materials -Project Plan templates -Business case templates -Project Management tools 4. Select Technology to facilitate the Project Management policy and procedures as well as the tracking and benefits realization of projects. 5. Utilize the PMO to manage the implementation of the initiatives highlighted in the remainder of the roadmap. 1. Business 2. IT Department STRATEGIC OBJECTIVE : Creation of PMO
  • 2. Table 2: Priority level2 Priority level2 This initiative is crucial to improving the state of IT. Initiatives marked red should be started within 1 – 3 months of the IT strategy approval and implementation. Initiative Sub-Initiative Time of achievement Key activities Responsibility 1. Establish an ICT steering committee None 1 - 6 weeks 1.1. Appoint staff to the ICT steering committee, including representatives from both business and IT at the executive, senior and operational levels. 2. Business 3. ITDepartment
  • 3. 2. Implement an IT Governance Framework 2.1 Implement Governance frameworks and procedures for IT decision making 3 – 6 Months 2.1.1. Review and update the current governance framework and ensure it is aligned to the overall Corporate Governance Framework. 2.1.2. Implement the IT Governance framework: a) Communicate the implementation of the IT Governance Framework b) Enforce compliance with the procedures defined in the IT Governance framework c) Monitor compliance and take corrective action as defined in the IT Governance framework 2.1.3. Define and Implement data governance policies and procedures a) Assign ownership of data and information within the organisation b) Classify the data of organisation c) Define system specific access levels for each data category d) Review current access rights on the system e) Implement and align access rights to data classifications f) Implement periodic review procedures for user access on the organisation systems 2.1.4. Appoint an ICT Steering Committee 2.1.5. Define and implement an IT Department organisational structure a) Clearly define and document roles and responsibilities of members of the IT department b) Appoint an IT Operations Manager to oversee operations and report to the CIO c) Structure performance management around documented roles and responsibilities. 2.1.6. Define and implement risk management policies and procedures that are integral to the existing business and decision making processes.  Business  ITDepartment  PMO
  • 4. Priority level2 This initiative is crucial to improving the state of IT. Initiatives marked red should be started within 1 – 3 months of the IT strategy approval and implementation. Initiative Sub-Initiative Time of achievement Key activities Responsibility 2.2. Implement Governance frameworks and procedures for IT Operations 6 – 48 Months 2.2.1. Implement Service Level Management a) Define and implement Service Level Agreements between business and IT. b) Define and implement standard operating procedures for the processes within the IT department. c) Define and implement OLAs between the units within the IT department. d) Monitor performance against the agreements and make improvements and amendments where necessary. 2.2.2. Implement IT financial management with specific focus on costs vs. performance. 2.2.3. Implement Capacity Management a) Review and document the current capacity of IT and what it is able to deliver. Address both infrastructure and people capacity and capability. b) Define and implement a capacity management process, including the capacity aspects that will be monitored. (e.g. bandwidth usage, server storage and processing). c) Implement training programmes for IT personnel to build skills where necessary. STRATEGIC OBJECTIVE 1: IT Governance
  • 5. Table 3: priority level3 Priority level3 This initiative is important to improving the state of IT. Initiatives marked orange should be started within 3 – 6 months of the IT strategy approval and implementation. Initiative Sub-Initiative Time of achievement Key activities Responsibility Implementation of IT governance framework 2.2. Implement Governance frameworks and procedures for IT Operations 6-48 Months 2.2.4. Implement IT Service Continuity Management a) Implement and adhere to a defined backup procedure which specifically outlines the backup frequency. b) Test the restore functionality of the backups on a regular basis. c) Define and implement an IT Disaster Recovery plan in conjunction with the business continuity plan. The focus should be on the mission-critical systems and data with well-defined RPO’s and RTO’s. 2.2.5. Implement Availability Management a) Agree on availability percentages and system downtime thresholds with business. b) Define and implement an availability management procedure taking into account the availability percentages agreed upon. This is closely related to service continuity and service level management. 2.2.6. Implement Service Desk Management a) Define incident categories and resolution timeframes for each category. b) Monitor and report on call resolution statistics. Have discrepancy reports for incidents that are open out of their resolution timeframe. c) Provide users with feedback on the status of calls logged throughout the resolution process.  Business  IT Department  ICT Steering Committee  PMO STRATEGIC OBJECTIVE : IT Governance
  • 6. Priority level3 This initiative is important to improving the state of IT. Initiatives marked orange should be started within 3 – 6 months of the IT strategy approval and implementation. Initiative Sub-Initiative Time of achievement Key activities Responsibility 1. Business process Integration None 6 – 12 months 1.1 Define and document business processes, their integration requirements and how IT can facilitate the integration processes 1.2 Assess the current legacy applications and systems in place and their ability to meet the defined business requirements. a) If legacy applications meet the business requirements, implement adequate system integration them as per business requirements. b) If the legacy application can no longer fully meet the business requirements or integration requirements, investigate procuring a system that meets the business and integration requirements.  Business  IT Department  ICT Steering Committee  PMO 8. Information security 3 – 18 months 8.1.1. Review all existing information security policies at the G3 CONSULTING and consolidate policies where necessary. 8.1.2. Gain top management buy-in to security practices becoming part of daily routine and raise awareness around security practices. 8.1.3. Define and implement security awareness training programmes for the end users within the organisation in order to ensure that security awareness is instilled in their daily job routines. 8.1.4. Ensure adequate physical access, logical access and environmental controls are in place to mitigate risks to the organisation network and information assets. 8.1.5. Define and implement network monitoring procedures in order to detect potential vulnerabilities and threats, as well as compliance to the information security standards and procedures. 8.1.6. Define and implement formalised antivirus and patch update methodologies. Conduct regular internal and specialist external security reviews.  Business  IT Department  ICT Steering Committee  PMO
  • 7. Priority level3 This initiative is important to improving the state of IT. Initiatives marked orange should be started within 3 – 6 months of the IT strategy approval and implementation. Initiative Sub-Initiative Time of achievement Key activities Responsibility STRATEGIC OBJECTIVE 3: Convergence 9. Harnessing Big data None 3-6 months 1.3 Show value in the data that the organisation currently has. Develop different ways to present this data in meaningful and valuable ways in order to garner buy- in for the business intelligence initiative. 1.4 Clean, restructure and consolidate existing data 1.5 Identify which data will be the most valuable for reporting and evaluation and implement the reporting and evaluation processes and dashboards. 1.6 Use the data and dashboards to make strategic decisions and to evaluate the effectiveness and popularity of different products and services offered by the organisation.  Business  IT Department  ICT Steering Committee  PMO 11. Empower Business personnel with IT knowledge and IT trend awareness None 3-6 months 11.1 Provide awareness to key personnel around the latest technological innovations in the IT industry and how these are applicable to the organisation from a strategic perspective. 11.2 Empower end users with the knowledge, skills and understanding to fully harness the potential of their IT equipment, systems and applications to make their daily job functions more efficient and effective.  Business  IT Department  ICT Steering Committee  PMO 12. Empower IT personnel with Business Knowledge None 3-6 months Provide awareness to the IT personnel of the business processes they are supporting and the criticality of the IT operations and support in enabling these processes to occur.  STRATEGIC OBJECTIVE 4: Innovation and Technology Enablement
  • 8.
  • 9. Table 4: Priority level 4 Priority level4 This initiative is important to improving the state of IT, but can afford to be started at a later stage. Initiatives marked yellow should be started within 6 – 12 months of the IT strategy approval and implementation Initiative Sub-Initiative Time of achievement Key activities Responsibility Implement an IT Governance Framework 2.2 Implement Governance frameworks and procedures for IT Operations 3 - 6 weeks 2.2.7. Implement Configuration Management a) Document the current configuration details of all hardware and software components utilised at the organisation and store this as the start of the Configuration Management Database. b) Document interdependencies between Configuration Items. c) Compare these configuration settings to industry best-practice and ensure that the CI’s are aligned where applicable. 2.2.8. Define and implement Change Management Procedures a) Define and document the types of changes that could occur (Standard, normal or emergency) b) Define and document the change management procedures and approval process for each of these changes c) Establish a Change Committee responsible for approving changes d) Define and standardise a change request template that incorporates impact and risk assessments of the proposed change. 2.2.9. Implement Release Management Procedures a) Define and implement processes to take inventory of software installed on all devices within the organisation. All subsequent changes and updates to this software should be recorded. b) Define and implement processes to adequately test software changes prior to their deployment.
  • 10. Priority level4 This initiative is important to improving the state of IT, but can afford to be started at a later stage. Initiatives marked yellow should be started within 6 – 12 months of the IT strategy approval and implementation Initiative Sub-Initiative Time of achievement Key activities Responsibility 6-48 Months 2.2.10. Implement Release Management Procedures a. Define and implement processes to take inventory of software installed on all devices within the organisation. All subsequent changes and updates to this software should be recorded. b. Define and implement processes to adequately test software changes prior to their deployment. c. Implement procedures to ensure documentation of software testing and deployment is kept and lessons learned are noted. STRATEGIC OBJECTIVE : Creation of PMO 3. IT Sourcing Strategies 1-6 months 3.1. Define the business requirements and IT requirements. 3.2. Identify IT functions that are not core operations that could be outsourced to a vendor which includes vendor support. 3.3. Define and implement vendor management processes which entail managing and monitoring the performance of the vendor as per agreed upon KPIs. 3.4. Select appropriate vendors for the functions to be outsourced and define KPIs in line with business and IT requirements to monitor the vendor against. Monitor, review and report on vendor performance and amend where necessary.  Business  IT Department  ICT Steering Committee  PMO
  • 11. Priority level4 This initiative is important to improving the state of IT, but can afford to be started at a later stage. Initiatives marked yellow should be started within 6 – 12 months of the IT strategy approval and implementation Initiative Sub-Initiative Time of achievement Key activities Responsibility 4.Cloud computing none 1-3 months 4.1. Investigate the potential cost reduction benefits of implementing a SaaS cloud computing model to host certain applications such as CRM and SharePoint. 4.2. If feasible, select an appropriate external service provider as per the external vendor management process.  IT Department  ICT Steering Committee  PMO 5. IT Asset Management none 1-3 Months 5.1. Investigate the number of devices that are operating on different hardware and software platforms. 5.2. Evaluate and select the most feasible hardware and software platforms from a risk and cost perspective. 5.3. Develop a platform migration plan to get all devices operating on the selected standard hardware and software platforms. Define and implement a BYOD policy which allows only approved and secured devices to connect to the organisation network. STRATEGIC OBJECTIVE 2: Cost Effectiveness 6. Platform Standardization none 1-12 months 6.1. Investigate the number of devices that are operating on different hardware and software platforms. 6.2. Evaluate and select the most feasible hardware and software platforms from a risk and cost perspective. 6.3. Develop a platform migration plan to get all devices operating on the selected standard hardware and software platforms. Define and implement a BYOD policy which allows only approved and secured devices to connect to the organisation network.
  • 12. Priority level4 This initiative is important to improving the state of IT, but can afford to be started at a later stage. Initiatives marked yellow should be started within 6 – 12 months of the IT strategy approval and implementation Initiative Sub-Initiative Time of achievement Key activities Responsibility STRATEGIC OBJECTIVE 3: Convergence 10. Innovation Initiatives Mobile technologies, eLearning, Corporate Partnerships 3-6 months 1.7 Investigate the market need for and benefits of investing in mobile technologies and applications for service and content delivery. 1.8 Investigate the market need for and benefits of investing in eLearning technologies and partnerships for service and content delivery. Investigate partnering with various government departments and other organisations in order to leverage new technologies and provision thereof. STRATEGIC OBJECTIVE 4: Innovation and Technology Enablement