Professional Documents
Culture Documents
v5 April 2014
Designed by:
Salahuddin Khawaja
s@decklaration.com
I II III IV V VI VII
Introduction Basic Slides Executive Models and Project Frameworks 7 Deck Rules
Summary Objects Management and
Templates Templates Methodologies
Why re-invent the
wheel
when building
presentations?
Just copy-steal-
paste
This deck has 100+ slides that can easily be
leveraged for any presentation that you need to build
Current State
ProcessX has evolved over the last 15 years
– Processes and systems have been cobbled together as a result of mergers and acquisitions
The core platform has had no strategic structural change
The organization is currently structured in functional silos
Key Issues
Enhancing or adding functionality is increasingly complex and requires significant effort and cost
Increasingly difficult to keep pace with the changing business landscape and providing value added services
– It is expected that current and new business strategic initiatives will make increasing demands
The ProcessX lifecycle has become fragmented which increases internal control risks
High risk of not being able to meet certain complex requirements
Go Forward Approach
Launched multiple programs to move towards:
– A single integrated global Platform (from a process and technology perspective)
– The adoption of a “Utility Mindset”
– Leverage Like Functions, Centers of Excellence, Across LOBs
– Holistic business process management (alignment with client, end-to-end control framework etc.)
8
Simple Table
Overall project is green and on track. Planning, Scoping & Analysis and Build are 50% complete. Testing has
commenced and a significant number of defects have been found.
Operational
4 (Not started) Documentation of procedures and controls to start
Readiness
9
Chevrons
Approach to Change – Understanding the future of the Banking Sector and a bank can get there will involve
launching a Strategic Initiative that will have 3 phases.
Approach
Assess internal and external Determine future state based Develop business case and
factors (Risk Appetite, on strategic objectives, change roadmap based on project
Regulations, Technology trends drivers and leading practices priorities, impact, cost and
etc) resource requirements
Perform Gap Analysis
Identify change drivers Develop methodology for
prioritization and critical path of
Perform a current state
the identified projects, and
assessment across People,
define resources and cost
Process and Technology
implications with executive
Define the strategic objectives inputs
Implement various program
10
Model 1
Technology
Regulatory Drivers Industry Direction
Performance Measures
Leading Practices and Targets
Financial Modeling and
Customer Analysis
Technology Trends Planning
Geographical Regulatory Drivers
Considerations
Market Analysis Strategy Formulation
INPUTS OUTPUTS
11
Model 2
Maturity Model – A maturity model can be used to help develop the Future State Architecture and perform the
Gap Analysis.
Value / Leader
12
Call Out
Developing a business case can show management the business imperative and value of adopting a particular
approach.
1 2 3 4 5 6 7
Executive Strategy and Change Drivers Vendor Cost and Risks and Implementation
Summary Current State Evaluation Benefits Derailers Plan
Assessment
(optional)
13
General Timeline
14
Timeline – Gantt Chart
The best way to plan out a project is to look at the various activities visually. The best tool to do that is a simple
Gantt Chart. A Gantt Chart is a visual representation of the various project activities.
Wave 1
Develop Business Case
Development / Build
Go-Live
Wave 2
Wave 3
Wave 4
Today
15
I II III IV V VI VII
Introduction Basic Slides Executive Models and Project Frameworks 7 Deck Rules
Summary Objects Management and
Templates Templates Methodologies
Executive Summary 1 (Situation, Complication, Resolution)
To support the future growth of our business, lower the cost of running ProcessX, and more efficiently manage
our business we recommend the implementation of the StrategyX
Situation
Since December, we have completed the Planning phase, updated financials, gathered customer views, and complied a
list of key projects
Based on these results the new proposed platform meets our needs and could be implemented within a 24-46 month
period
Complication
Internal meetings with various teams confirmed that current and new strategic initiatives, and evolving business needs will
continue to put increasing demands on the legacy system
Resolution
To support the future growth of our business, lower the cost of running ProcessX, and more efficiently manage our risks
the program team recommends the implementation of StrategyX
17
Executive Summary 2 (Business Case View)
Program Status
Business Imperative
Financial Summary
Recommendation
18
Executive Summary 3 (Analysis Summary)
Background
Analysis
Conclusion To-Date
Next Steps
19
I II III IV V VI VII
Introduction Basic Slides Executive Models and Project Frameworks 7 Deck Rules
Summary Objects Management and
Templates Templates Methodologies
List 1 – Simple
21
List 2 – Depicting Numbers
Mobility 75% Ratio of all workers that have some level of mobility associated with their job
22
Chevrons 1 – Timeline / Roadmap
The future roadmap based on the strategic objectives, current state assessment and recommendations.
Approach
Defined vision and Analyzed the current Develop future state. Prioritize projects based
strategic objectives to state across three Then develop in impact and cost.
evolve to the next level. dimensions: people, recommendations Develop high-level
process and technology. (projects, etc.) to implementation plan.
address gaps.
23
Chevrons 2 – Process
24
Chevrons 3 – Circular
Text Text
Text
Text
Text
Text
Text
Text Text
Text Text
Text Text
Text Text
25
Pyramid 1 – Three Levels
Business
Delivery
Technical
Delivery
26
Pyramid 2 – Multi-dimensional
MISSION
Leading
Bank
VALUES
Performance
Trust Commitment
VISION
Client Service
27
Venn Diagrams
Text Text
28
Circle 1 – Basic
Shareholders Board
Management Customers
MISSION
VALUES
VISIONS
Employees Society
Regulators Partners
29
Circle 2 – Callouts
Key to getting the certification is getting a deep understanding of the 9 Knowledge Areas and their corresponding
sub-process (a total of 42).
X X
X X X
X X
31
Circle 4 – Cross-hair
Company Division
Product/
Region
Service
32
Circle 5 – Flow (4 steps)
Heading
[Summary text]
Heading Heading
Focus
[Summary text] [Summary text]
Heading
[Summary text]
33
Circle 5 – Flow (5 steps)
Heading
[Summary text]
Heading Heading
[Summary text] [Summary text]
Focus
Heading Heading
[Summary text] [Summary text]
34
Honeycomb
Lines
of Business
2 3
Risk Operations
Management
Risk
Management
4 5
Compliance
Control Technology
6
Finance
35
Organizational Chart
Name_here
Title_here
Name_here
Title_here
Name_here
Responsibility1
Responsibility1
36
Cube
Operation
Integration
Business Requirements
Engineering
Planning
Technical Requirements
Operational Requirements
Non-Functional Requirements
37
I II III IV V VI VII
Introduction Basic Slides Executive Models and Project Frameworks 7 Deck Rules
Summary Objects Management and
Templates Templates Methodologies
Status Report 1
Overall project is green and on track. Planning, Scoping & Analysis and Build are 50% complete. Testing has
commenced and a significant number of defects have been found.
Operational
4 (Not started) Documentation of procedures and controls to start
Readiness
39
Status Rating G
Status Report 2
Current status is Green for Go Live on Dec 5. Phase 2 scheduled for Q2 2015.
82% UAT Test Cases completed (75% passed) Complete UAT by October15th
10 defects remain open (8 are critical)
Phase IV:
Amber Total 22 defects have been opened till-date
UAT
Due to high number of defects UAT Sign off delayed to
Oct 15
Parallel Plan framework developed; details are being Complete Parallel Plan
Phase V: firmed up Finalize action plans to address risks
Green
Parallel Plan Some risk have been identified (infrastructure, cleansed Parallel run to start
data etc/) and action plans are being developed
Go-Live and Migration plan being developed Complete Go-Live and Migration plan
Phase VI:
Green Plan developed to communicate to key stakeholders
Go Live during
2014 2015
J F M A M J J A S O N D J F M A M J
Build
System Integration Testing
UAT
UAT Completed A
Parallel Testing
R Red A Amber G Green
KEY N Parallel Test Complete
H On Hold C Complete N Not Started
N Phase 2 Go Live
Go Live Nov 5 (TBD)
40
Gantt Chart
The best way to plan out a project is to look at the various activities visually. The best tool to do that is a simple
Gantt Chart. A Gantt Chart is a visual representation of the various project activities.
Wave 1
Develop Business Case
Development / Build
Go-Live
Wave 2
Wave 3
Wave 4
Today
41
Gantt Chart – Variations and Symbols
Various variations and symbols can be used to give more dimensions/depth to visual Gantt charts
99%
RAG Milestones
Sprints
R Red
A Amber
G Green
H On Hold
C
Complete
N Not Started
Build Complete +
(In Stages)
Today
42
Objects – Harvey Balls and Status
G
Green: On track (0-1
Closing Significant Progress
week delay)
Complete Complete
43
R Green (On track)
A Amber (At risk)
44
Risk/Issue Template
Target
Type Title Description Impact Mitigation Strategy Impact Owner Date Raised
Date
Red
Red
Amber
Amber
Green
Green
45
Actions Item Template
# Item Action Update Owner Date Opened Status
1 Defects Management requested that the program Defect tracking has been put in place
Jack June 7 Open
team get a firm plan to address defects
2 Production Review issues that resulted from the parallel Post Mortem and Lessons learned to be completed
Parallel test Jane July 5 Closed
46
Project Dashboarding
Risk and Issues are communicated to management via the Dashboarding process.
Slide 51
Slide 52 Slide 53
47
RAG Status
Objective
Scope
Dependency
Benefits/ROI
Financials
Priority: Risk
Completion Date:
48
RAG Status
Roadmap – Gantt
49
RAG Status
Additional Comments
50
RAG Status
Risks / Issues
Target Close
# Risk / Issue Owner Type Severity Likelihood Open Date Change Mitigation Strategy and Current Status
Date Date
51
RAG Status
52
RAG Status
Off Track
53
I II III IV V VI VII
Introduction Basic Slides Executive Models and Project Frameworks 7 Deck Rules
Summary Objects Management and
Templates Templates Methodologies
Slides
presented in
this section are
in no particular order …
- 55 -
Business Transformation Approach
A complex business transformation could take multi-years. Not all phase’s depicted below are necessary.
Phase III:
III
Vendor Selection
IVPhase IV:
Program
Implementation
56
Business Transformation Approach – Details
Approach
Define overall vision and Develop business case Document high-level Prioritize projects based
strategic objectives and roadmap based on requirements; issue RFI in impact and cost
project priorities, impact, and RFP
Perform a strategy & Develop high-level
cost and resource
current state assessment Conduct Deep Dive implementation plan
requirements
across People, Process Assessments
Sign agreements with
and Technology (identify
Conduct reference calls & vendors
gaps)
customer visits
Implement various
Determine target state
Performed independent program and project
based on strategic
research initiatives.
objectives, change
drivers and leading Performed due diligence
practices
57
Strategy Sample – Mobile Strategy
Mobile applications should be developed using a methodology tailored for mobile devices
Approach
Defined mobility goals Develop mobile use Develop various mobile End to end testing
(revenue, efficiency, cases products
Launch various mobile
customer experience Process requirements Develop/modify services products
etc.)
User interface Mobile web
Integrate mobile with
Define business case and Data requirements existing channels Mobile app
prioritize the roadmap
Develop overall solution System Testing Blog
Budget approval architecture Social Media
Current state assessment Develop wireframes
of Mobility infrastructure Prototype critical features
Develop launch approach
58
Program Vision and Strategic Principles
The Program Management Office (PMO) vision and associated strategic objectives
guide all change related activities.
Strategic Objectives
3 Partner with key stakeholders to drive enhanced experience and new functionality
Tier 2 5 Streamline processing business and technical architecture to increase time to market
59
Strategy Development Framework
Approach to Strategy Development – A strategy can be developed based on a current state assessment in
conjunction with a set of external/internal inputs.
Technology
Regulatory Drivers Industry Direction
Performance Measures
Leading Practices and Targets
Financial Modeling and
Customer Analysis
Technology Trends Planning
Geographical Regulatory Drivers
Considerations
Market Analysis Strategy Formulation
INPUTS OUTPUTS
60
Maturity Model
Background
The Finance Department has played a critical role over the years from both a revenue and business support perspective
We have evolved globally as a result of marketplace demands, mergers and acquisitions and changes in regulations
The existing platform has been developed in an unstructured manner, resulting in a fragmented lifecycle
Varying drivers have resulted in a compelling business case to strategically re-architect the platform
Value / Leader
61
Business Case
Developing a business case can show management the business imperative and value of adopting a particular
approach.
1 2 3 4 5 6 7
Executive Strategy and Change Drivers Vendor Cost and Risks and Implementation
Summary Current State Evaluation Benefits Derailers Plan
Assessment
(optional)
62
Process Analysis – SIPOC
SIPOC Framework is a Six Sigma tool used for process analysis and can be used to perform a current statement
assessment.
S I P O C
Provider of inputs to Materials, resources A structure ser of Products or services The recipients of the
the process or data required to activities that transform a that result from the process outputs
execute the process set of inputs into specified process
outputs, providing value
to customers and
stakeholders
63
Rationale for Platform Upgrade
Varying drivers have resulted in a compelling business case to strategically re-architect the platform.
64
Derailers – Key Implementation Risks
As with any large undertaking, we foresee a series of risks that can potentially derail various programs and
projects under the PMO umbrella.
2 Resources constraints
4 Budget
9 Shift in priorities
65
Roadmap Development Approach
Part II
Part I Part III
Project Prioritization and
Project Templates Roadmap Development
Dependency Analysis
Project owners to complete Project Consolidate project information Develop strategic roadmap
scoping
Prioritize based on cost, benefit and risk
Identify dependencies
66
Project Template
Project
Project Name High / Medium / Low
Complexity
Target
Completion Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
Project 2014 2015
Description
X X X
Project Impact
People Process Technology
Project # of
Project Size High / Medium / Low
FTEs
Project Drivers
X X X X X
Operational Revenue Cost Reduction Regulatory Value Added Customer Security and
Efficiency Increase Experience Reliability
67
Roadmap – Option 1
2013 2014 2015 2016
J F M A M J J A S O N D Q1 Q2 Q3 Q4 Q1/2 Q3/4 Q1-4
Select Vendor
Sprint 0 Complete
(Entry into Build)
Build Complete
(In Agile Sprints)
UAT Complete
Parallel Test
Complete
Decommission
Legacy System
Post Implementation
Review
68
Vendor Evaluation – Approach
RFI
RFP
Deep Dive
Assessments
Independent Research
Due Diligence
69
Vendor Evaluation – Guiding Principles
A set of principles should be defined to guide the Customer Relationship Manager (CRM) vendor evaluation
process.
Select a flexible, functionally rich, and industry proven package that can support
1 our CRM vision and objectives
Ensure ability to take ownership of product (not source code) and support with
5 minimal reliance on vendor post implementation
70
Option Analysis
Pro 1 Pro 1
Pro Pro 2 Pro 2
Pro 3 Pro 3
Con 1 Con 1
Con Con 2 Con 2
Con 3 Con 3
Conclusion ????
71
Program Organization
The Program Organization has 4 key roles: Program Office, Business Integrator, Systems Integrator and Solution
Delivery
Program
Office
Solution Delivery
72
Business Strategy and the 3 P’s
To manage change the Program Management Office (PMO) is tasked with putting in a disciplined approach
towards: Portfolio Management, Program Management and Project Management.
Portfolio Management
Program Management
Portfolio Management Project Management
73
Risk Management Process – Overview
Develop
Issue & Risk
Management
Plan
Close Risk
74
Reset – Mission, Values & Vision
The Mission, Values and Vision of the organization should be adjusted based on the broader set of stakeholders
MISSION
Leading
Bank
VALUES
Performance
Trust Commitment
VISION
Client Service
75
Cost Reduction
Approach
Stakeholder management
(buy-in, consensus, communication etc.)
76
Requirements Traceability Matrix (RTM)
The RTM provides a framework to trace the requirements to the types of testing being performed to ensure
complete coverage. When properly implemented, the RTM will help manage cost and quality.
Reconciliation Deployment
Parallel Testing
Requirements Parallel Test Specifications
Analysis
Business Requirements User Acceptance Testing
User Acceptance Test Specifications
Development
Coding / Debugging Unit Testing
Unit Test
Specifications
77
Business Portfolio 3x3
High
Competitive Position
Medium
Low
Product/Market Attractiveness
78
World Map
79
United States Map
80
I II III IV V VI VII
Introduction Basic Slides Executive Models and Project Frameworks 7 Deck Rules
Summary Objects Management and
Templates Templates Methodologies
7 Deck Rules – Overview
Understand
the Canvas
I
Make it Keep it
Sing Simple
VII II
V IV
Focus on Solve a
Composition Problem
82
7 Deck Rules – Benefits
Bottom line:
It will help you convey your
message in a compelling
way.
83
Rule I: Understand the Canvas
The Company Logo is displayed Page number in the middle of the The Department or Project Name
4 5 6
for branding purposes slide is displayed for branding purposes
84
Rule II: Keep it Simple
85
Rule III: Tell a Story – Storyboarding Depicted
1 2 3 4 5
Storyboarding is the A great storyline has an Its easier for the audience In combination, the Slide The storyboard process
method for the creation of engaging beginning, to understand complex Title and the Slide Lead will converts brilliant, abstract
a storyline of a deck insightful content & a clear concepts when explained summarize the entire deck ideas into a coherent
conclusion in a storyline storyline
86
Rule IV: Solve a Problem
A Deck should solve a problem. A methodical approach should
be taken when solving a problem.
A methodical process should be used to find the right viable solution, Divide the problem into smaller discreet parts such that there is no
not just any solution. overlap, no gaps.
Using formal frameworks to structure your analysis will help support the Problems can be complex – typical with little effort a major part of the
conclusions reached. problem can be solved. So focus on what is important.
87
Rule V: Focus on Composition
Use correct grammar, punctuation & spelling Use clear, concise and precise language Focus writing on the subject matter
Follow conventional rules Utilize ethical and inoffensive Language Align writing with the deliverable objective
Principle 4: Structure Principle 5: Leveling & Labeling Principle 6: Voice & Tone
Group thoughts into clusters Distill your message (levels of details) Use active voice (vs. passive voice)
Sequence thoughts logically Using headings to label content Express ideas in positive terms
88
Rule VI: Leverage a Library
Why re-invent the wheel when building deliverables? Have a library of slides handy and leverage.
Work bench with basic objects that are frequently used All objects and models that can be used for visuals
A standard one page executive summary template Established frameworks and methodologies
89
Rule VII: Make it Sing
The slide flow should be understood in a Colors have deep meaning. Use creative diagrams to illustrate – as
flash. To achieve this, structure the slide Choose your colors as would choose your simply as possible – concepts, models
in a way so as to guide the viewer eyes. words – carefully. and processes
90
Keep reading at:
decklaration.com/bullet
s-do-kill
Author’s Message
This deck will save you time, ensure a consistent look-feel and help
you produce a more polished and powerful product.
The purpose of this slide deck is to help you create insightful presentations.
This timesaver has a large number of preformatted slides (40+) that can be
easily leveraged. It also has frameworks and methodologies (35+) that you
can utilize when faced with a challenging problem.
Or, can’t think of the right way to depict a thought? Brain-cramp? Peruse the
content. This will get the creative juices going.
Happy decking!
92