Transcript Presentation title is 36 points

Projects to Programs to
Transformation
11 Habits of Highly Successful Projects
Business Outcomes
Think Big, Start Small, Scale Fast
1
Succeed
With An Initial
Project
A BPM Project should
deliver targeted results that
directly support the strategic
goals of the business. Thus,
a successful BPM Project
requires close collaboration
between business
operations and
technologists.
2
2
Establish
A Program
A successful BPM program
ties all business process
projects to core business
initiatives.
3
Extend Success
Across The
Enterprise
A Transformational BPM
Program enables you to
manage your processes
and support corporate
initiatives such as improving
product quality, reducing
time-to-market, expanding
to new markets, raising
customer satisfaction, and
increasing profit margins.
Project Scope
Habit #1
Prove business value first
 Don’t forget the focus should be on business value
 Be willing to make trade-offs for the first release
3
Iterative Implementation Methodology
A proven methodology for scaling from project to program to
transformation
Week 1
Definition
Infrastructure
Configuration
4
Weeks 2-3
Mapping
Weeks 4 to 10
Development
Training/ Mentoring
Weeks
11 to 12
Test
Week
13
Go
Live
Infrastructure
Deployment
Habit #2
Make it about Productivity AND Visibility
 Metrics, KPI’s and SLA’s should be part of the DEFINE Phase
 Don’t scope OUT metrics
 Remember visibility is critical to IMPROVEMENT
5
Habit #3
Never “One and Done”
 Iterative Approach….. Continuous Process Improvement
 Phases 2,3 or Versions 2,3 will always happen
 Trade-offs (but don’t trade-off the metrics!)
7
BPM Accelerates Better Business Outcomes
Traditional build programs
Complex tooling
IT-centric development
Big-bang deployment
Range of
traditional
outcomes
Program
initiation
Month 0
8
6
12
18
24
30
Month 36
BPM Accelerates Better Business Outcomes
Scalable BPM programs
Model-driven tooling
Integrated development
Iterative deployment
Targeted
outcome
$
$
$
$
Program
initiation
Month 0
9
$
6
Plus: Faster cash returns
12
18
24
30
Month 36
Habit #4
Don’t Skip Process Analysis
 Requirements documents are not process analysis
 Don’t over-do the initial requirements (Define) phase
 Include Process Analysis skills on your team early
10
Project Success Depends on Understanding
Process Analysis Illuminates the End-to-End Process
What is the data needed at different points?
What is the velocity that we need in this process?
How quickly must the turnaround time be?
Where are the issues with meeting this requirement?
Process Analysis is designed to help you…
Understand the main problem areas in the current
process
Analyze specific business processes
Formulate a roadmap for recommended improvements
11
Habit #5
Take the Time to Deliver Value
 A project longer than 90 days is not a failure
 Self-sufficiency can extend project time-lines
 Timelines can depend on the sophistication of the process
12
Think Big, Start Small, Scale Fast
Business Outcomes
Scaling a successful project into a program
1
Succeed
With An Initial
Project
A BPM Project should
deliver targeted results that
directly support the strategic
goals of the business. Thus,
a successful BPM Project
requires close collaboration
between business
operations and
technologists.
13
2
Establish
A Program
A successful BPM program
ties all business process
projects to core business
initiatives.
3
Extend Success
Across The
Enterprise
A Transformational BPM
Program enables you to
manage your processes
and support corporate
initiatives such as improving
product quality, reducing
time-to-market, expanding
to new markets, raising
customer satisfaction, and
increasing profit margins.
Project Scope
Habit #6
Build a complete team
 Java (or .Net) developers aren’t all you need
 Have the right mix of resources on the team
 Identify good pools of talent for BPM developers
14
Habit #7
Make self-sufficiency a priority
 Don’t allocate partial human beings
 Make sure all of the right skills are represented
 Don’t mix self-sufficiency with tight deadlines
15
Business Outcomes
Think Big, Start Small, Scale Fast
1
Succeed
With An Initial
Project
A BPM Project should
deliver targeted results that
directly support the strategic
goals of the business. Thus,
a successful BPM Project
requires close collaboration
between business
operations and
technologists.
16
2
Establish
A Program
A successful BPM program
ties all business process
projects to core business
initiatives.
3
Extend Success
Across The
Enterprise
A Transformational BPM
Program enables you to
manage your processes
and support corporate
initiatives such as improving
product quality, reducing
time-to-market, expanding
to new markets, raising
customer satisfaction, and
increasing profit margins.
Project Scope
Habit #8
Fund to value … not first release
 BPM is about Continuous Process Improvement
 BPM should be programmatic (programs spanning projects/LOBs)
 Funding model should contemplate Projects and the Program
17
Habit #9
Force collaboration
 Consider carefully for the first project
 Co-locate team members from business and IT
 Leverage the Playbacks
19
Make BPM Pervasive Across the Organization
“Playbacks” Drive Engagement
Process Developers
Call Center Managers
20
Confidential
VP, Pharmacy
Operations
Habit #10
Establish the owners
 Processes are business-owned
 BPM is the discipline/program
 BPMS is the enabling technology
21
Habit #11
Market your work
 Create regular internal communication about progress
 Use videos, wikis, portals to “show off” new processes
 BPMS or BRMS is the enabling technology
22
11 Habits That Drive Success
23
Get started today
 Visit www.blueworkslive.com
for a free 30-day trial
 Contact IBM for a Business
Process Discovery Workshop
 Test drive BPM software at:
IBMBPMDemos.com
24
© 2010 IBM Corporation
IBM or our Partners can help you get started!
A complimentary workshop to help you evaluate your
process improvement initiative (1-3 days)
 Conducted onsite with your business & IT
stakeholders with IBM solution & domain experts
IBM Process Improvement
Discovery Workshop
 Define the business need and map to a baseline
solution architecture and recommended
implementation approach
 Get a summary of key findings, recommendations
& a report for stakeholder analysis enabling
decision-making
 Optional: Develop a project ROI




Evaluate the applicability of BPM technology for the proposed project.
Evaluate the best place to start for the current project scope
Understand the realistic business impacts of the solution
Define a baseline BPM architecture early in the project.
© 2010 IBM Corporation
Q2-3 Regional Impacts & ICTYs
Event Dates as of 4/12/2012
IOT
Europe
Local Impact Comes To You
ALL GEOs (Multiple Cities)
May – October
North America
IMT
City
Date
Type*
Nordic
Helsinki
May 10th
Cross
Switzerland
TBD
June 5th
Cross
Italy
Rome
June 7th
Regional
UK
London
June 12th
Regional
Spain
TBD
TBD
Cross
Canada
Toronto
June 19th
ICTY
US
Charlotte
June 12th
ICTY
US
Kansas City
June 7th
ICTY
US
Charlotte
June 19th
ICTY
US
Chicago
June 5th
ICTY
US
Reston
Sept 6th
ICTY
US
Costa Mesa
Sept 6th
ICTY
US
Nashville
Sept 11th
ICTY
US
Edmonton
Sept 13th
ICTY
US
Minneapolis
Sept 13th
ICTY
US
New York
Sept 20th
ICTY
US
Boston
Sept 26th
ICTY
*Type: Cross = Cross SWG Event, ICTY = Impact Comes to You Event, Regional = Regional Impact
© 2010 IBM Corporation
Every cultural revolution has to start somewhere
You’re just one project away from unleashing the value of BPM
It’s worth the Journey
• BPM is an exciting technology
• Everybody will want it
• You’ll be a hero
IBMBPMDemos.com
© 2010 IBM Corporation
Thank You …
Q&A
28