Guided Implementations

Engage

• Call #1 Introduce Info-Tech’s business architecture methodology.
• Call #2 Develop a stakeholder engagement strategy.
• Call #3 Review the stakeholder engagement strategy.

Model

• Call #1 Create a strategy map & define value streams.
• Call #2 Model business capability maps.
• Call #3 Map value streams to business capabilities.

Drive

• Call #1 Introduce Info-Tech's capability assessment framework.
• Call #2 Create and assess application capability map.
• Call #3 Analyze investments through initiative portfolio maps.

Focus

• Call #1 Determine the goals of the continual improvement plan, and align them to organizational goals and strategy.
• Call #2 Identify critical success factors for the project, conduct a service desk audit, and review the results.

Build

• Call #1 Brainstorm and prioritize continual improvement initiatives for the service desk.
• Call #2 Draw on the prioritized list of service desk initiatives to build a continual improvement plan and strategic roadmap.

Run

• Call #1 Build a plan to communicate progress, promote the benefits of the projects, and reflect on lessons learned.

Assess security requirements

• Call #1 Understand the value and challenges of security governance and management to create your business case.
• Call #2 Define your risk tolerance and determine your security pressure posture.

Perform a gap analysis

• Call #1 Perform a current state assessment of your capabilities and maturity levels.
• Call #2 Establish the governance and management target state.

Develop gap initiatives

• Call #1 Identify where there are existing gaps and where initiatives should be built.
• Call #2 Prioritize the gaps based on resources and efforts to create an implementation timeline.

Implement gap initiatives

• Call #1 Review and finalize the governance and management roadmap and action plan.
• Call #2 Build out your governance and management deliverables.

Launch the project

• Call #1 Identify the project leader with the appropriate skills.
• Call #2 Assemble a well-rounded project team.
• Call #3 Develop a mission statement and change messages.

Identify enterprise services

• Call #1 Create a comprehensive list of enterprise services that are used across the organization.
• Call #2 Create a categorization scheme that is based on the needs of the business users.

Identify line of business services

• Call #1 Walk through the two Info-Tech methodologies and understand which one is applicable.
• Call #2 Define LOB services using the appropriate methodology.

Complete service definitions

• Call #1 Decide what should be included and what should be kept internal for the service record design.
• Call #2 Complete the full service definitions.

Get executive buy-in for your PPM strategy

• Call #1 Scoping call: discuss the current state of PPM and review strategy options.
• Call #2 Understand how to wireframe realistic process goals, rooted in your PPM strategic expectations, that will be sustained by the organization.

Align PPM processes to your strategic goals

• Call #1 Examine your current-state PPM process and create a high-level description of the target-state process for each of the five PPM processes (1-2 calls per process).

Complete your PPM strategic plan

• Call #1 Assess your PPM tool requirements to help support your processes.
• Call #2 Determine the costs and potential benefits of your PPM practice.

Define BCP scope, objectives, and stakeholders

• Call #1 Scope your requirements. Assess current maturity. Identify fit-for-need and a pilot project.
• Call #2 Create business process workflows.

Define RTOs and RPOs based on your BIA

• Call #1 Identify process dependencies, alternates and workarounds.
• Call #2 Create an impact scoring scale and conduct a BIA.
• Call #3 Identify target RTO and RPO.

Create a recovery workflow

• Call #1 Conduct a tabletop planning exercise and document the recovery workflow.
• Call #2 Identify gaps in recovery capabilities and alternate site requirements.

Establish a BCMS to govern and improve your BCP

• Call #1 Summarize the pilot results and plan next steps, including additional documentation.
• Call #2 Define BCMS roles and responsibilities.
• Call #3 Make the case for a wider BCMS program.

Create a vision for the CoE

• Call #1 Understand the significance of building a CoE for your enterprise application. Define the scope of the CoE and identify stakeholders.
• Call #2 Align the CoE goals with corporate objectives.
• Call #3 Understand the four defining elements of the CoE Operating Model. Determine current support capability under each element.

Design the CoE future state

• Call #1 Analyze and classify requirements.
• Call #2 Identify CoE initiatives to address classified requirements.
• Call #3 Create a map of the ideal state that ties identified initiatives with the CoE Operating Model.

Develop a CoE roadmap

• Call #1 Assess the capabilities required to build the CoE.
• Call #2 Prioritize CoE initiatives and identify any dependencies.
• Call #3 Measure and track the success of each initiative using KPIs.