Tips for Writing a Solid and Realistic Work Plan for Your SAP NetWeaver

Tips for Writing a
Solid and Realistic
Work Plan for Your
SAP NetWeaver
BI Project
Dr. Bjarne Berg
© 2007 Wellesley Information Services. All rights reserved.
What We’ll Cover …
•
•
•
•
•
•
•
Selecting an approach to use for your project
Defining project milestones
Allocating appropriate resources
Using SAP Solution Manager
Taking advantage of SAP Best Practices BI tool
Leveraging the SAP Best Practices work plan
Wrap-up
1
The Gray Areas of Methodologies
•
•
First step in determining how to write a work plan is to
pick a methodology for your project
While Accelerated SAP (ASAP) is normally the default
method, there are alternatives
When to Select Different Methodologies
High
Joint Application Design
(JAD)
System development Life-Cycle
based methodologies
(SDLC)
Extreme Programming
(EP)
Rapid Application Development
(RAD)
Time to
Delivery
Low
Low
There are several dimensions
when multiple methodologies can
be employed (i.e., when time to
delivery is moderate, or when the
impact of failure is moderate)
High
Impact of Failure
2
A Brief Look at ASAP
•
ASAP for SAP NetWeaver BI is based on many of
the same ideas and approaches found in the ASAP
methodology for SAP R/3
• SAP standard
• Single, pragmatic, and standardized
methodology
• Evolved out of 20 years of experience
• Manageable scope, cost, and common
expectations
• Common language
• Preconfigure documentation and tools
Source: SAP
3
What is ASAP?
Examples for Accelerators:
• Project plan, estimating
• Design strategies, scope definition
• Documentation, issues DB
Fill in the Blank
Fill in the
Blank
vs. Start
from
Versus
Scratch
Start from Scratch
• Workshop agenda
• Questionnaires
• End- user procedures
• Test plans
• Technical procedures
• Made easy guidebooks (printout, data transfer,
system administration …)
Source: SAP
4
What We’ll Cover …
•
•
•
•
•
•
•
Selecting an approach to use for your project
Defining project milestones
Allocating appropriate resources
Using SAP Solution Manager
Taking advantage of SAP Best Practices BI tool
Leveraging the SAP Best Practices work plan
Wrap-up
5
Project Preparation — Some Key Observations
Project charter: Represents an agreement on,
and commitment to, the deliverables of the
project, as well as project time constraints,
resources, standards, and budget.
Scope: Sets the initial definition of the project.
Project plan: This is the first cut. It focuses on
milestones and work packages.
Core Activities
Project team organization: Sets the “who” of
the project. This decides who will be involved
and what their goal is.
1.1 Initial Project Planning
1.2 Project Procedures
1.3 Training Preparation
Standards and procedures: Sets the “why”
and “how” of the project. Standardizing how
meetings are run, how documents are handled,
etc., meaning that everyone understands what
is going on.
1.4 Project Kickoff
1.5 Technical Requirements Planning
1.6 Quality Check Project Preparation
Source: Pauline Woods-Wilson
6
Project Preparation — The Scope Statement
•
Scope statement should include:






Technical source systems and
modules (e.g., SAP R/3 CCA)
Technology components (SAP
NetWeaver PI, SAP NetWeaver BI, SEM-CPM, SAP APO,
XML, etc.)
Functional purpose (profit loss statement, sales analysis, etc.)
User community (location, organization, types, numbers)
Access interfaces (Web portal, cockpit, Business Explorer
(BEx), Crystal, third-party)
Security (encryption, single sign-on, data level security, role
security, etc.)
7
Project Preparation — The Scope Statement (cont.)
•
Scope statement should include
(cont.):




Hardware components
(development environment, test,
QA and production, Unix, NT, Web servers, app servers,
leverage of existing infrastructure)
Impacted organizations
Retirement of legacy reporting systems (if any)
Project language and documentation system
Remember to include in the scope statement,
what is not included in the scope and make
sure it is agreed to before the project starts.
8
Project Preparation — The Milestone Plan
Project plan: This is the first cut. It focuses on
milestones and work packages.
•
•
The first work plan should
consist of only core tasks,
milestones, and their
critical dates
Resources are simply
referred to by their role
instead of individual names
individuals (update later
when resources
are assigned)
To write the first cut project plan, you
need to have determined scope,
resource need/availability, and time
9
Project Preparation — Milestone Dates
Project plan: This is the first cut. It focuses on
milestones and work packages.
•
The milestone plan should be
published and posted on the walls.
Do not “hide it” in the project
manager’s drawer.
The Milestone
Plan should ID
TASK
consist of
2
Project Preparation
18 days
all major
11
Blueprint Phase & Planning Phase
13 days
Realization
70 days
phases, start 5169 Project
Final Preparation Phase
20 days
103
Go Live and Support Phase
14 days
and end
dates, and
duration
The plan should also include special project
dates and events such as workshops, project
reviews, approvals, etc.
Dur- ation
•
Start
Finish
5/15/2005
6/2/2005
6/29/2005
7/12/2005
7/5/2005
9/13/2005
9/10/2005
9/30/2005
10/1/2005
10/15/2005
10
What We’ll Cover …
•
•
•
•
•
•
•
Selecting an approach to use for your project
Defining project milestones
Allocating appropriate resources
Using SAP Solution Manager
Taking advantage of SAP Best Practices BI tool
Leveraging the SAP Best Practices work plan
Wrap-up
11
Resources — Roles
•
•
SAP NetWeaver BI projects
consist of a team of highly-skilled
individuals
The quality of the people is much
more important than the number
•
•
Project Resources
A skilled developer can accomplish
correctly what three novice
developers will mess up in the same
amount of time
Program/Project Manager
Application Consultant
Application Team Member
Technical Consultant
Technical Team Member
Technical Team Lead
Help Desk Provider and Manager
Business Process Team Lead
Training and Documentation Lead
Customer Project Sponsor
Think of the project team as a set
of roles, not individuals
•
A person may fulfill more than one
role during the project
You should staff your project based on the needs, not based on
who is available at a given time. Sometimes the right decision is
to delay a project until the right people can participate.
12
Team Organization — Small Project for Single Subject Area
•
These are roles, not positions (sometimes one team
member can fill more than one role)
This is a good organization for
teams that use Joint Application
Development (JAD) or Rapid
Application Development (RAD) as
their development methodology.
Project Sponsor
Project Manager
Business Team
Technical Team
Business Analyst
BI Architect
Presentation Developer
ETL Developer
Basis and functional SAP R/3 support
The development is interactive,
scope is small, and the timeline for
each implementation is short.
Larger projects can create multiple
project teams working on
dedicated areas. However, very
tight coordination is required to
pull this off in practice.
Four to five team members and normally
three to six months duration depending on scope
ETL = Extract, transform and load
13
Team Organization — Mid-Sized SAP NetWeaver BI Projects
This organization by roles is useful on mid-sized projects using system
development lifecycle methodologies such as ASAP. It is scalable, but business
analysts must be given direct access to developers to make this work in practice.
Project Sponsor/
Steering Comm.
Project Manager
BI
Architect
Business
Analyst(s)
Data Management
(InfoCubes & ODS)
ETLs
Presentation
Developer(s)
Sr. Business Analyst
Sr. ETL Developer
Sr. BI Developer
Sr. Presentation Developer
Business Analyst
ETL Developer
BI Developer
Presentation Developer
Basis and Functional SAP R/3 Support
These are roles, not positions
(sometimes one team member
can fill more than one role)
Eight to ten team members and normally
two to four months duration depending on scope
14
Team Organization — Large SAP NetWeaver BI Projects
This organization is grouped by functional areas. It is very scalable for large projects, but
requires solid coordination between the architect and the developers on each sub-team.
Sometimes both a front-end and back-end architect are used on very large projects.
Project Sponsor/
Steering Committee
Project Manager
BI Architect
Portal developer(s)
Sales Team
Finance Team
Business Analyst/(sub-team lead)
BI Developer
Presentation Developer(s)
ETL Developer
Business Analyst/(sub-team lead)
BI Developer
Presentation Developer(s)
ETL Developer
Material Mgmt. Team
Business Analyst/(sub-team lead)
BI Developer
Presentation Developer(s)
ETL Developer
Basis and Functional SAP R/3 Support
Fifteen to twenty-five team members and normally
six to eighteen months duration depending on scope
15
What We’ll Cover …
•
•
•
•
•
•
•
Selecting an approach to use for your project
Defining project milestones
Allocating appropriate resources
Using SAP Solution Manager
Taking advantage of SAP Best Practices BI tool
Leveraging the SAP Best Practices work plan
Wrap-up
16
SAP Solution Manager: Don’t Build Everything from Scratch
Tools
Content
Implementation Platform
Solution Monitoring
Service Desk
E-Learning
Upgrade
Change Request Management
Implementation Content
Roadmaps
Services
Best Practice Documents
SAP Active Global Support
Gateway to SAP
Service Delivery Platform
Source: SAP
You can incorporate many shared documents and tools into your project.
Your work plan should reflect the time savings of using these accelerators.
SAP Solution Manager is delivered as part of your annual maintenance fee.
17
SAP Solution Manager: What Is Useful for BI?
Project
Preparation
Define project
Set up system
landscape
Business
Blueprint
Define customer
solution
based on
SAP processes
Configuration
Testing
Configure
processes
Test processes
Synchronize
customer settings
Training
Define
e-learning units
and create
learning maps
Project Administration
Issue Tracking/Monitoring/Reporting
Roadmaps
Change Management
Green areas indicate material that can be leveraged in SAP NetWeaver BI
All items in SAP Solution Manager are not equally useful for the BI project team. However,
some material can be used. Collect the material and make it part of the deliverables for you
team. Write work plan tasks that directly reference the BI tasks you decide to use.
Note
SAP Solution manager Version 3.2 SP8 or higher is required to upgrade to SAP
NetWeaver 7.0.
18
SAP Solution Manager: EarlyWatch Reports Are Great!
•
EarlyWatch reports:


•
Provide a simple way to confirm how your system is running
and to catch problems
Are a “goldmine” for system recommendations
A copy of a full 40 pages from a real report is included
on the conference CD
19
SAP Solution Manager: EarlyWatch Reports Sample
•
•
Run them periodically
and read the details
Let’s take a look at a
real EarlyWatch report
from a mid-sized
company that has
been running SAP BW
for the last few years
20
SAP Solution Manager: EarlyWatch Reports Sample (cont.)
1 Performance Indicators
The following table shows the relevant performance indicators in various system areas.
Area
System Performance
Hardware Capacity
Database Space Management
Query Performance
Indicators
Active Users
Max. CPU Utilization on DB Server
Max. CPU Utilization on Appl. Server
DB Size
Last Month DB Growth
Avg. Total Runtime of the BW Queries
Avg. Database Runtime of the BW Queries
Value
18
74 %
74 %
355.52 GB
118.63- GB
11.5 s
8.0 s
Trend
down
steady
steady
steady
steady
down
steady
1 Performance Overview
The performance of your system was analyzed with respect to the average response times and total
workload. We did not detect any major problems that could affect the performance of your system.
The following table shows the average response times for various task types:
Task type
DIALOG +
RFC
UPDATE
UPDATE2
BATCH
HTTP
Dialog
Steps
195240
Avg. Resp.
Time in ms
3253.3
Avg. CPU
Time in ms
728.7
Avg. Wait
Time in ms
1.8
Avg. Load
Time in ms
2.5
5
48
59288
257762
984.2
133.2
11599.3
693.5
28.2
17.1
2091.2
183.7
26.0
0.7
0.6
4.4
15.2
3.3
8.5
2.2
Avg. DB
Avg. GUI
Time in ms Time in ms
1110.9
6.3
585.4
80.8
5772.6
405.0
1.1 Current Workload
The following table lists the number of current users (measured from our workload analysis) in your system.
Users
Measured in System
Low Activity
98
Medium Activity
11
High Activity
7
Total Users
116
21
What We’ll Cover …
•
•
•
•
•
•
•
Selecting an approach to use for your project
Defining project milestones
Allocating appropriate resources
Using SAP Solution Manager
Taking advantage of SAP Best Practices BI tool
Leveraging the SAP Best Practices work plan
Wrap-up
22
SAP Best Practices for Business Intelligence
•
Is a new tool with consolidated access to
documentation, hints, white papers, recommendations,
tools, and a sample work plan

•
•
•
All based on BI scenarios
Gives you many templates and a work plan
Is intended for mid-sized enterprises that need rapid
implementation or by large companies that need to
create a corporate template for their subsidiaries
New SAP customers can also combine this with the
Baseline Package or an industry-specific version of SAP
Best Practices
SAP Best Practices for Business Intelligence supports
predefined scenarios that handle core BI business requirements.
23
SAP Best Practices for Business Intelligence (cont.)
This tool has been enhanced over the last two
years, and has several BI specific project
accelerators that you will not find in SAP
Solution Manager.
A test drive is available at
http://help.sap.com/bp_biv170/index.htm.
24
An Option — Work Plans Based on Deliverables
•
The best practice documents are organized around
scenarios that simplify the collection of tools
Many of your team’s deliverables
can be downloaded here. You can
incorporate them specifically into
your work plans.
25
Deliverables for Your Work Plan
•
Sales analysis example gives an overview of what SAP
NetWeaver BI has to offer, how to build it, and best
practices for a variety of technical designs
These are tools and accelerators that you can download and make
deliverables in your work plan.
26
An Option — Create Your Work Plan Based on Scenarios
•
Each scenario is described in a process
overview document
27
Keep the Work Plan at a Manageable Level
•
Don’t load too many details into the work plan


Explain what needs to be done, not how to do it
SAP Best Practices for BI has installation guides to assist
Note
The installation guide has step-by-step scenario-based documentation.
Do not replicate minute steps in the work plan; keep it at a high
enough level where it is useful, but not a burden to maintain.
28
What Versions Does It Support?
SAP NetWeaver BI 7.0
The SAP Best
Practices tool was
developed for SAP BW
3.5, and later updated for
SAP NetWeaver BI 7.0
SAP
App.
Compon
ent
Software
Component
Release
Level
Highest
Support
Package
SAP BW
SAP_BASIS
700
0007
SAPKA70007
SAP_ABA
700
0007
SAPKA70007
SAP_BW
700
0007
SAPKW70007
PI_BASIS
2005_1_700
0007
SAPKIPYJ77
BI_CONT
702
0004
SAPKIBIHP4
SCM
500
0002
SAPKY50002
SAP_BW
700
0005
SAPKW70005
SAP_BASIS
700
0005
SAPKB70005
SAP_ABA
700
0009
SAPKA70005
SAP_BASIS
700
0007
SAPKA70007
SAP_ABA
700
0007
SAPKA70007
SAP_APPL
600
0004
SAPKH60004
PI_BASIS
2005_1_700
0007
SAPKIPYJ77
SAP_BASIS
700
0007
SAPKA70007
SAP_ABA
700
0007
SAPKA70007
BBPCRM
500
0004
SAPKU50004
PI_BASIS
2005_1_700
0007
SAPKIPYJ77
SAP SCM
SAP BW 3.5
mySAP
Application
Component
SAP BW
Software
Component
Release
Level
Highest Support
Package
SAP_BASIS
640
0004
SAPKB64004
SAP_ABA
640
0004
SAPKA64004
SAP_BW
350
0004
SAPKW35004
PI_BASIS
2004_1_640
0004
SAPKIPYI64
BI_CONT
352
0002
SAPKIBIEP2
Source: SAP – Jan, 2007
SAP ERP
2005
SAP CRM
While installation recommendations are based on SAP BW 3.5 or SAP NetWeaver BI 7.0,
most management tools, accelerators, and the sample work plan are not version-specific.
29
What We’ll Cover …
•
•
•
•
•
•
•
Selecting an approach to use for your project
Defining project milestones
Allocating appropriate resources
Using SAP Solution Manager
Taking advantage of SAP Best Practices BI tool
Leveraging the SAP Best Practices work plan
Wrap-up
30
The Sample Work Plan
You can download the work plan from the Project Support area.
31
The Work Plan — Some Background
•
The work plan on the SAP BI Best Practice CD (and on the
Web site) is a Microsoft Project project plan file (.mpp)
•
The work plan is only an example that you need to modify
to fit your project’s scope, resources,
and timelines
•
The example is based on a rapid development of a single
subject area over a five week period

However, the tasks and their dependencies are relevant to larger
projects that may require substantially more time
32
The Work Plan — Some Background (cont.)
•
The resource plan assumes that 11 roles are filled on
the project (two part-time)

This includes two consultants and one project sponsor
Project Resources
Program/Project Manager
Application Consultant
Application Team Member
Technical Consultant
Technical Team Member
Technical Team Lead
The work plan is an example and should not be
used as a “cookie cutter” for your work plan.
Sound judgments must still be applied.
Help Desk Provider and Manager
Business Process Team Lead
Training and Documentation Lead
Customer Project Sponsor
33
Project Preparation — Some Key Observations
Project charter: Represents an agreement on,
and commitment to, the deliverables of the
project, as well as project time constraints,
resources, standards, and budget.
Project plan: This is the first cut. It focuses on
milestones and work packages.
Scope: Sets the initial definition of the project.
Project team organization: Sets the “who” of
the project. This decides who will be involved
and what is their goal.
Standards and procedures: Sets the “why”
and “how” of the project. Standardizing how
meetings are run, how documents are handled,
etc., means that everyone understands what is
going on.
Source: Pauline Woods-Wilson
Core Activities
1.1 Initial Project Planning
1.2 Project Procedures
1.3 Training Preparation
1.4 Project Kickoff
1.5 Technical Requirements Planning
1.6 Quality Check Project Preparation
34
Project Preparation Phase
ID
1
TASK
SAP Best Practices BI Implementation Roadmap - read Notes
2
Pre-Sales Phase / Project Preparation
Duration
Start
Finish
24.5d
5/28/05 8:00 AM
7/1/05 12:00 PM
4.d
5/28/05 8:00 AM
6/2/05 5:00 PM
3
Perform Customer Workshop & present Best Practices in Demo System
1.5d
5/28/05 8:00 AM
5/29/05 12:00 PM
4
Review and select scenarios that are best fit for customer requirements
.5d
5/29/05 1:00 PM
5/29/05 5:00 PM
5
Carry out review of delivered business content to check for gaps
.5d
5/30/05 8:00 AM
5/30/05 12:00 PM
6
Define Critical Success Factors
.5d
5/30/05 1:00 PM
5/30/05 5:00 PM
7
Validate & Document Technical Requirements
.5d
6/2/05 8:00 AM
6/2/05 12:00 PM
.d
6/2/05 12:00 PM
6/2/05 12:00 PM
.5d
6/2/05 1:00 PM
6/2/05 5:00 PM
2.d
5/28/05 8:00 AM
5/29/05 5:00 PM
8
9
Define System Landscape Strategy (maybe 2 system landscape and/or SAP One
Server)
Perform Hardware sizing
10
Install software
•
•
•
While short in duration, do not spend too much time on
the project prep phase
It is easy to get intimidated by the many unknowns
Rely on your consultants, but keep the momentum
Spending more than 15% of your project time
in this phase is a sign of analysis-paralysis.
35
Project Sizing — 1. Base It on the Scope (Real Example)
Customi
zation
L
M
L
M
L
M
L
L
L
L
L
L
L
L
L
M
M
M
M
Tech. Dev.
infocube
Financials
General ledger line item (ODS)
COPA
Prod cost planning released cost
estimates (COPC_C09)
Exploded itemization standard
product cost (COPC_C10)
Cost and allocations
(COOM_C02)
Cost object controlling
(0PC_C01)
Order
Extraction and Report
transforms
and roles
Security and
scheduling
Web
development
User
support/
planning
Project mgmt System docs Tech infraand admin
& manuals
structure
Bus. Analysis,
training, req.
gathering, change
mgmt.
Total
Hours
216
158
216
229
286
229
188
153
188
101
127
101
132
153
133
134
152
135
100
120
100
79
94
79
150
180
150
403
470
403
1,732
1,893
1,734
238
286
216
126
153
152
120
94
180
470
2,035
216
1144
188
101
132
135
100
79
150
403
2,648
238
286
216
137
153
152
120
94
180
470
2,046
216
216
216
229
229
229
187
187
187
101
101
101
132
132
132
135
135
135
100
100
100
79
79
79
150
150
150
403
403
403
1,732
1,732
1,732
216
229
187
101
132
135
100
79
150
403
1,732
216
216
228
228
187
187
101
101
132
132
135
135
100
100
79
79
150
150
403
403
1,731
1,731
Delivery data of shipment stages
(0LES_C13)
Delivery service (0SD_C05)
Planning and Scheduling
Material Movements (0IC_C03)
216
228
187
101
132
135
100
79
150
403
1,731
180
229
133
101
132
134
100
79
150
403
1,641
216
457
132
101
132
134
100
79
150
403
1,904
APO Planning
SNP Integration
Manufacturing Processes
Production Orders
Cross Applications
Total Hours
277
277
832
832
216
216
127
127
153
153
152
152
120
120
94
94
180
180
470
470
2,621
2,621
277
277
4,298
832
832
8,074
216
216
3,587
127
127
2,110
153
153
2,656
152
152
2,681
120
120
2,040
94
94
1,606
180
180
3,060
470
470
8,126
2,621
2,621
38,238
Billing
Sales order
Acct. Rec. (0FIAR_C03)
Deliver
Shipment cost details
(0LES_C02)
Shipment header (0LES_C11)
Stages of shipment (0LES_C12)
Remember that your sizing also has to be based on the
team’s experience and skill level.
36
Project Sizing — 2. Prioritize the Effort
•
The next step is to prioritize and outline the effort on a
strategic timeline
Financials
General ledger line item (ODS)
COPA
Prod cost planning released cost estimates
(COPC_C09)
Exploded itemization standard product cost
(COPC_C10)
Cost and allocations (COOM_C02)
Cost object controlling (0PC_C01)
Order
Billing
Sales order
Accounts receivables (0FIAR_C03)
Deliver
Shipment cost details (0LES_C02)
Shipment header (0LES_C11)
Stages of shipment (0LES_C12)
Delivery data of shipment stages (0LES_C13)
Delivery service (0SD_C05)
Planning and Scheduling
Material Movements (0IC_C03)
APO Planning
SNP Integration
Manufacturing Processes
Production Orders
Cross Applications
qtr 1
2005
qtr 2 qtr 3
qtr 4
qtr 1
Make sure your sponsor and the business
community agree with your delivery schedule
2006
qtr 2 qtr 3
qtr 4
qtr 1
2007
qtr 2
qtr 3
37
Project Sizing — 3. General Guidelines
2005
qtr 1
Financials
General ledger line item (ODS)
866
COPA
946.5
Prod cost planning released cost
estimates (COPC_C09)
Exploded itemization standard product
cost (COPC_C10)
Cost and allocations (COOM_C02)
Cost object controlling (0PC_C01)
Order
Billing
Sales order
Accounts receivables (0FIAR_C03)
Deliver
Shipment cost details (0LES_C02)
Shipment header (0LES_C11)
Stages of shipment (0LES_C12)
Delivery data of shipment stages
(0LES_C13)
Delivery service (0SD_C05)
Planning and Scheduling
Material Movements (0IC_C03)
APO Planning
SNP Integration
Manufacturing Processes
Production Orders
Cross Applications
Total 1,813
Note
qtr 2
2006
qtr 3
qtr 4
qtr 1
qtr 2
qtr 3
qtr 4
qtr 1
2007
qtr 2
qtr 3
866
947
867
867
1,732
1,893
1,734
1017.5
1017.5
2,035
1324
1023
1324
1023
2,648
2,046
866
866
866
866
866
866
1,732
1,732
1,732
866
865.5
865.5
865.5
866
865.5
865.5
865.5
1,732
1,731
1,731
1,731
820.5
820.5
1,641
952
1310.5
1310.5
1,813
4,232
4,232
2,598
2,598
4,283
4,283
3,573
952
1311
1311
1,904
2,621
2,621
1311
1311
1,311
1,311
2,621
2,621
6,195
2,622
38,238
Plan to spend 15% of the project time on project prep, 25% on
blueprinting, 45% on realization and 15% on go-live.
There is a risk of spending too much time on design and short changing
development time, which often causes project delays. Accept that you
will not have answers to all questions until you see the data and queries.
38
1
2
3
4
5
6
7
8
9
2-Jun
1-Jun
31-May
30-May
TASK
29-May
ID
28-May
Project Preparation Phase — Dependencies
SAP Best Practices BI Implementation Roadmap - read Notes
Pre-Sales Phase / Project Preparation
Perform Customer Workshop & present Best Practices in Demo System
Review and select scenarios that are best fit for customer requirements
Carry out review of delivered business content to check for gaps
Define Critical Success Factors
Validate & Document Technical Requirements
Define System Landscape Strategy (maybe 2 system landscape and/or SAP One
Server)
Perform Hardware sizing
•
Key to project prep phase is the level setting of all parties


One-day workshop with stakeholders, managers, and sponsors
Dedicate some time early in the workshop to demo SAP
NetWeaver BI and discuss capabilities of the tool set
A one-day workshop can remove project confusion
and delays, help in getting the right requirements,
and avoid missing “low hanging fruit.”
39
Blueprinting Phase — Some Key Observations
Getting the right requirements:
Finding out the detailed functional
specs of what the users really need
and not just what they want
Deciding what will be developed in
SAP NetWeaver BI and what will be
maintained as SAP R/3 reports
Map the functional requirements to
the standard content and see what can
be leveraged and what needs
to be extended
Core Activities
2.1 Project Management Business Blueprint
2.2 Organizational Change Management
Create detailed technical specifications
and designs of InfoCubes,
MasterData, ODSs and high-level
architectural designs
2.3 Project Team Training Business Blueprint
Create user acceptance group(s) and
have them review and give feedback on
the system as it is developed
2.6 Business Process Definition
ODS = Operational Data Store
2.4 Develop System Environment
2.5 Organizational Structure Definition
2.7 Quality Check Business Blueprint
40
Blueprinting Phase — Planning
ID
TASK
1 SAP Best Practices BI Implementation Roadmap - read Notes
11
Blueprint Phase & Planning Phase
12
Apply for Going Live Check
13
Finalize Project Scope [selected scenarios]
14
Check Content delivered by Best Practices
15
Determine those issues affecting BW Implementation and assign risk to project
16
Present Final Scope to Customer and Get Signoff of Scope
17
Project Planning Phase
18
Set Up Development Environment
19
Define transport Strategy
20
Activate TMS
21
Define Project Organization and Create Teams
22
Analyze Roles and Tasks by Standard Content Areas and Technical
23
Update delivered Project Plan & finalize, including resources assignments
24
Define customer rollout & training strategy for SAP BW
25
Define types of users of the BW
26
Determine Number of users for BW
27
Determine Data Access Requirements
•
•
Duration
24.5d
9.5d
.d
1.d
.5d
.25d
.25d
8.d
.25d
.25d
.25d
3.d
.25d
.25d
1.d
.33d
.33d
.34d
Start
5/28/05 8:00 AM
5/29/05 5:00 PM
5/29/05 5:00 PM
5/30/05 8:00 AM
5/30/05 8:00 AM
5/30/05 1:00 PM
5/30/05 3:00 PM
5/30/05 8:00 AM
5/30/05 8:00 AM
5/30/05 8:00 AM
5/30/05 8:00 AM
6/2/05 8:00 AM
6/2/05 8:00 AM
6/2/05 10:00 AM
6/2/05 8:00 AM
6/2/05 8:00 AM
6/2/05 10:38 AM
6/2/05 2:17 PM
Finish
7/1/05 12:00 PM
6/12/05 12:00 PM
5/29/05 5:00 PM
5/30/05 5:00 PM
5/30/05 12:00 PM
5/30/05 3:00 PM
5/30/05 5:00 PM
6/10/05 5:00 PM
5/30/05 10:00 AM
5/30/05 10:00 AM
5/30/05 10:00 AM
6/4/05 5:00 PM
6/2/05 10:00 AM
6/2/05 12:00 PM
6/2/05 5:00 PM
6/2/05 10:38 AM
6/2/05 2:17 PM
6/2/05 5:00 PM
Lock-down the detailed scope early and obtain formal
written approval for your detailed scope statement
Implement a formal change
approval process
Spend some time early on to plan user training and
support; also, formalize your team organization
41
2-Jun
1-Jun
31-May
30-May
TASK
29-May
ID
28-May
Blueprinting Phase — Planning Dependencies
1 SAP Best Practices BI Implementation Roadmap - read Notes
11
Blueprint Phase & Planning Phase
12
Apply for Going Live Check
13
Finalize Project Scope [selected scenarios]
14
Check Content delivered by Best Practices
15
Determine those issues affecting BW Implementation and assign risk to project
16
Present Final Scope to Customer and Get Signoff of Scope
17
Project Planning Phase
18
Set Up Development Environment
19
Define transport Strategy
20
Activate TMS
21
Define Project Organization and Create Teams
22
Analyze Roles and Tasks by Standard Content Areas and Technical
23
Update delivered Project Plan & finalize, including resources assignments
24
Define customer rollout & training strategy for SAP BW
25
Define types of users of the BW
26
Determine Number of users for BW
27
Determine Data Access Requirements
•
Many tasks can take place at the same time

The trick is to ensure all team members
are active and the workload is
evenly balanced throughout project
Spend some time on resource loading and
workload balancing. Not all tasks are dependent.
42
Blueprinting Phase — Design, Architecture, and Training
ID
TASK
11
17
24
25
26
27
28
29
30
31
32
33
34
35
36
Blueprint Phase & Planning Phase
Project Planning Phase
Define customer rollout & training strategy for SAP BW
Define types of users of the BW
Determine Number of users for BW
Determine Data Access Requirements
Business Information Warehouse Design/Archetecture Design &
Document which parts of Best Practices and SAP Content are used
Document Data Flow Procedures
Define / Document Data Access Design
Define /document Authorization Strategy Design
Define Data Load Requirements
Technical/Hardware Validation
Confirm Hardware Readiness
Define BW Performance and Load Aspects
•
•
•
•
Duration
9.5d
8.d
1.d
.33d
.33d
.34d
3.d
1.d
1.d
.25d
.25d
.5d
.5d
.5d
.5d
Start
5/29/05 5:00 PM
5/30/05 8:00 AM
6/2/05 8:00 AM
6/2/05 8:00 AM
6/2/05 10:38 AM
6/2/05 2:17 PM
6/2/05 8:00 AM
6/2/05 8:00 AM
6/3/05 8:00 AM
6/4/05 8:00 AM
6/4/05 10:00 AM
6/4/05 1:00 PM
6/2/05 8:00 AM
6/2/05 1:00 PM
6/2/05 8:00 AM
Finish
6/12/05 12:00 PM
6/10/05 5:00 PM
6/2/05 5:00 PM
6/2/05 10:38 AM
6/2/05 2:17 PM
6/2/05 5:00 PM
6/4/05 5:00 PM
6/2/05 5:00 PM
6/3/05 5:00 PM
6/4/05 10:00 AM
6/4/05 12:00 PM
6/4/05 5:00 PM
6/2/05 12:00 PM
6/2/05 5:00 PM
6/2/05 12:00 PM
Users should be defined in terms of power users, casual users, and executives
Each user group will have different interface requirements
Spend some time writing the data flow to each ODS and InfoCube
Perform a quality validation on your hardware
implementation (RAID, O/S, RDBMS, network, BI
install, etc.)
Define clearly when each datastore has to be loaded
(time) and the frequency of the loads.
43
Blueprinting Phase — Resource Planning
BI Developer
ETL Developer
Presentation Developer
Project Manager
Business Analysts
Ideal Years
Experience
(minimum)
2+
Training Days In-House
(if new in
Training
the role)
Days
15
3-5
3+
15 - 20
3-5
1+
5 - 10
3-5
5+
10 - 15
3-5
5+
5 - 10
3-5
Plan time on the work plan for early
training of your staff members
Issue
44
Blueprinting Phase — Project Management and Test Plans
Duration
ID
TASK
11
17
37
38
39
40
41
42
43
44
45
46
47
48
Blueprint Phase & Planning Phase
Project Planning Phase
Project Procedures
Update Project Management Standards and Operating Procedures
Update Implementation Standards and Procedures to include BW specific
Update SAP System Admin Procedures
Test plans
Define BW Test Plans
Define Data Flow & Validation Test Plans
Define Data Access Test Plans
Define Authorizations Test Plan
Develop System Test Plans
Develop Technical Test Plans
Develop Functional/Performance Test Plans
•
•
9.5d
8.d
1.d
.5d
.5d
.5d
4.d
1.d
.5d
.5d
.5d
.5d
.5d
.5d
Start
5/29/05 5:00 PM
5/30/05 8:00 AM
6/2/05 8:00 AM
6/2/05 8:00 AM
6/2/05 1:00 PM
6/2/05 1:00 PM
6/5/05 8:00 AM
6/5/05 8:00 AM
6/6/05 8:00 AM
6/6/05 1:00 PM
6/9/05 8:00 AM
6/9/05 1:00 PM
6/10/05 8:00 AM
6/10/05 1:00 PM
Finish
6/12/05 12:00 PM
6/10/05 5:00 PM
6/2/05 5:00 PM
6/2/05 12:00 PM
6/2/05 5:00 PM
6/2/05 5:00 PM
6/10/05 5:00 PM
6/5/05 5:00 PM
6/6/05 12:00 PM
6/6/05 5:00 PM
6/9/05 12:00 PM
6/9/05 5:00 PM
6/10/05 12:00 PM
6/10/05 5:00 PM
Ensure you plan detailed procedures for transporting objects between
the development, testing, and production landscape
Much like an SAP R/3 project, you should plan to test the
security/roles, load programs, update and transfer rules, as well as
data stores, aggregated delta-enabled extractors, and
time-dependent objects
You should plan to spend about 20 - 40%
of your project time on testing and fixes.
45
10-Jun
9-Jun
Blueprint Phase & Planning Phase
Project Planning Phase
Project Procedures
Update Project Management Standards and Operating Procedures
Update Implementation Standards and Procedures to include BW specific
Update SAP System Admin Procedures
Test plans
Define BW Test Plans
Define Data Flow & Validation Test Plans
Define Data Access Test Plans
Define Authorizations Test Plan
Develop System Test Plans
Develop Technical Test Plans
Develop Functional/Performance Test Plans
8-Jun
11
17
37
38
39
40
41
42
43
44
45
46
47
48
7-Jun
TASK
6-Jun
ID
5-Jun
Blueprinting Phase — Project Management, Test Plans,
Dependencies
Test Strategy
Test Plan
Test Execution
Problem Resolution
SAP R/3 and BI testing is
not different from a
methodology standpoint,
but the execution is.
46
Realization Phase — Some Key Observations
Core Activities
3.1 Project Management Realization
3.2 Organizational Change Management
3.3 Training Development and Approvals
3.4 Baseline Configuration (content activation)
3.5 System Management
Development Programs: Provide details
of added programming structures
3.6 Final Configuration (enhancements)
End User: Training material, manuals,
Web site, on-line help
3.8 Data Conversion Programs (if any)
Configuration: Activate content, make
extensions to SAP NetWeaver BI
standard content, execute test data and
masterdata loads, validate data quality,
build and modify transfer and/or
update rules
3.7 Prepare External Interfaces (non SAP R/3)
3.9 Develop Queries
3.10 Develop User Interface Enhancements
3.11 Determine Additional Reporting Requirements
3.12 Create Structured Reports (e.g., third-party)
3.13 Establish Authorization Concept
3.14 Establish Data Archiving Plan (if applicable)
Testing: Unit testing by developers,
acceptance testing by business analysts,
system and integration testing by users
3.15 Final Integration Test
3.16 Quality Check Realization
47
Realization Phase — Development Core Activities
Duration
TASK
ID
51
52
53
54
55
56
57
58
59
60
61
Project Realization
BW Development Configuration
Implement relevant Best Practices scenarios
Configure Data Access Environment
Source Data Quality Validation
Collect Representitive Sample of Source Data (Transaction and Master)
Identify and List all issues with transaction/master data
Implement Standard Authorization Concept - Development Environment
Document those issues affecting BW Implementation and assign risk to project
Communicate issues to customer and agree on criteria to clean data
Provide customer report on findings and agree on go forward strategy to clean
6.25d
3.d
3.d
.25d
.75d
.5d
.5d
1.d
.25d
.5d
.25d
Start
6/5/05 8:00 AM
6/5/05 8:00 AM
6/5/05 8:00 AM
6/5/05 8:00 AM
6/5/05 10:00 AM
6/6/05 8:00 AM
6/6/05 1:00 PM
6/9/05 8:00 AM
6/9/05 8:00 AM
6/9/05 10:00 AM
6/9/05 3:00 PM
Finish
6/13/05 10:00 AM
6/9/05 5:00 PM
6/9/05 5:00 PM
6/5/05 10:00 AM
6/5/05 5:00 PM
6/6/05 12:00 PM
6/6/05 5:00 PM
6/9/05 5:00 PM
6/9/05 10:00 AM
6/9/05 3:00 PM
6/9/05 5:00 PM
TIPS FOR MAKING THE REALIZATION PHASE SUCCESSFUL
If SAP NetWeaver BI is
new in the organization
you should seriously
consider hiring
experienced BI
developer(s) or rely on
external resources
during this phase.
1 Review the functional requirements and
the technical design
2 Make sure you have established data
stewards for the masterdata, & assigned
the masterdata to specific developers
6 Do not allow exceptions to the naming
conventions
7 Make sure that “ putting out fires ” do not
take precedence and becomes the “defaulted”
architecture and standard.
3
Have your ETL developers report
functionally to an individual who is
responsible for creating process chains
8 Try new ideas in a Sandbox environment
and do not contaminate the development
environment.
4
Avoid nested ODS layers and keep the
architecture as pristine as possible
9
5
Make your transformations as part of
update rules into InfoCubes if you need
to be able to reconcile to the source
system. Keep the details in the ODS.
Keep details for multi- use in the ODS and
do not design the ODS based on the needs
of a single InfoCube.
10 Developers must perform unit test on all
their work and personally sign - off on their
storage object.
48
51
52
53
54
55
56
57
58
59
60
61
Project Realization
BW Development Configuration
Implement relevant Best Practices scenarios
Configure Data Access Environment
Source Data Quality Validation
Collect Representitive Sample of Source Data (Transaction and Master)
Identify and List all issues with transaction/master data
Implement Standard Authorization Concept - Development Environment
Document those issues affecting BW Implementation and assign risk to project
Communicate issues to customer and agree on criteria to clean data
Provide customer report on findings and agree on go forward strategy to clean
•
9-Jun
8-Jun
7-Jun
Duration
TASK
6-Jun
ID
5-Jun
Realization Phase — Development Core Dependencies
6.25d
3.d
3.d
.25d
.75d
.5d
.5d
1.d
.25d
.5d
.25d
Most issues during this phase will be data ETL

While you cannot plan for all issues, you can set aside time to deal with them
Data cleansing should occur in the source
system. (Hint: Cover this in the scope statement.)
Source: SAP
49
Realization Phase — Tracking Progress
•
Examine the work plan and the hours spent on a task vs.
the task accomplished level

•
To make this work, you need time tracking (by work
plan), and you need to manage your projects by tasks
accomplished

•
For example, if a task was scheduled to take 20 hours and the
deliverables are 75% complete in the weekly status report, the
hours used on the task should not exceed 15 hours
Tasks accomplished should be reported on weekly status
reports by each team member
Developers have a tendency to quickly report 99%
completion, but never formally sign off on their work

Monitor the hours used vs. the task completion early in the
project to make sure you are on track and can detect issues
before they become problems
50
Realization Phase — Testing Core Activities
ID
51
62
63
64
65
66
67
68
Duration
TASK
Project Realization
Quality Assurance Environment
Set Up Quality Assurance Environment
Transport Requests from Dev
Load data from R/3 QA Environment
Test QA Environment
BW Quality Assurance Configuration
Execute BW Test Plans in Quality Environment
Tasks\Dates
December 2003
January 2004
Start
6/5/05 8:00 AM
6.25d
3.25d 6/10/05 8:00 AM
.5d 6/10/05 8:00 AM
.25d 6/10/05 1:00 PM
1.d 6/10/05 3:00 PM
2.5d 6/10/05 3:00 PM
.5d 6/10/05 3:00 PM
2.d 6/11/05 10:00 AM
Finish
6/13/05 10:00 AM
6/13/05 10:00 AM
6/10/05 12:00 PM
6/10/05 3:00 PM
6/11/05 3:00 PM
6/13/05 10:00 AM
6/11/05 10:00 AM
6/13/05 10:00 AM
February 2004 1-Mar 8-Mar 15-Mar 22-Mar 29-Mar 5-Apr
Identify People for Testing
Schedule Facilities
Prioritize Test Areas (Queries)
Send out Meeting Notice
Execute System Test
Document Results
Problem Resolution
Business analysts are responsible for planning and executing the system testing of queries.
51
51
62
63
64
65
66
67
68
13-Jun
12-Jun
TASK
11-Jun
ID
10-Jun
Realization Phase — Testing Core Dependencies
Project Realization
Quality Assurance Environment
Set Up Quality Assurance Environment
Transport Requests from Dev
Load data from R/3 QA Environment
Test QA Environment
BW Quality Assurance Configuration
Execute BW Test Plans in Quality Environment
Tasks
1
2
3
4
5
Create test script
Identify roles to be used
Documentation on using test tools
Procedure for documenting test results
Training sessions for using test scripts
6
7
8
9
Identify key contacts
Communicate about transports
Arrange time for progress control
Schedule facilities
Have a formal testing process and document the findings.
While many issues are easy to fix, it is the lessons learned
that will pay off in the long run.
52
Final Preparation Phase — Some Key Observations
Cutover Plan and the Technical
Operations Manual: Describe the details
on how to move to the production
environment and Go-Live
Stress and Volume Tests: Confirm the
production hardware’s capabilities
End-User Training Document:
Describes the delivery of the necessary
levels of SAP training prior to going live
Source: Pauline Woods-Wilson
Core Activities
4.1 Project Management Final Preparation
4.2 Training Final Preparation
4.3 Stress and Volume Testing
4.4 System Management
4.5 Detailed Cutover Planning
4.6 Cutover
Source: SAP
4.7 Quality Check Final Preparation
53
Final Preparation Phase — System Testing
ID
TASK
69
70
71
72
73
74
75
76
77
78
79
80
Final Preparation Phase
Setup Production Environment
Define Production System Design
Set Up Production Environment
Confirm BW Production Configuration
Execute BW Test Plans in Production Environment
Conduct System Tests
Conduct System Administration Tests
Conduct Backup and Restore Procedure Test
Conduct Failure Scenarios Test
Conduct Disaster Recovery Test
Conduct Going Live Check
•
Duration
10.5d
3.d
.5d
.5d
2.d
2.d
3.d
.25d
.5d
.5d
.5d
1.d
Start
Finish
6/10/05 8:00 AM
6/13/05 10:00 AM
6/13/05 10:00 AM
6/13/05 3:00 PM
6/16/05 10:00 AM
6/16/05 10:00 AM
6/16/05 10:00 AM
6/16/05 10:00 AM
6/16/05 1:00 PM
6/16/05 1:00 PM
6/17/05 8:00 AM
6/18/05 10:00 AM
6/24/05 12:00 PM
6/18/05 10:00 AM
6/13/05 3:00 PM
6/16/05 10:00 AM
6/18/05 10:00 AM
6/18/05 10:00 AM
6/19/05 10:00 AM
6/16/05 12:00 PM
6/16/05 5:00 PM
6/16/05 5:00 PM
6/17/05 12:00 PM
6/19/05 10:00 AM
Performance test execution
1. Identify queries to be performance tuned
2. Determine cut-off load (e.g., 40% of expected actual users — not named)
3. Schedule queries to run in background to simulate “real” user load
Execute each query while scripts are running
4. Attempt tuning at query level and perform analysis based on benchmarks
5. If needed, build aggregates, indexes, etc.
6. Record findings in a formal tracking tool available to everyone

54
69
70
71
72
73
74
75
76
77
78
79
80
•
19-Jun
18-Jun
17-Jun
16-Jun
15-Jun
14-Jun
13-Jun
12-Jun
TASK
11-Jun
ID
10-Jun
Final Preparation Phase — System Testing Dependencies
Final Preparation Phase
Setup Production Environment
Define Production System Design
Set Up Production Environment
Confirm BW Production Configuration
Execute BW Test Plans in Production Environment
Conduct System Tests
Conduct System Administration Tests
Conduct Backup and Restore Procedure Test
Conduct Failure Scenarios Test
Conduct Disaster Recovery Test
Conduct Going Live Check
Typical backup strategy


Run a full system backup on the weekends and only delta backups each day
before the load process starts
Make sure that you can actually restore from the backups and that the system has
the resources it needs (i.e., Will one application server be enough?)
Don’t underestimate the need for system testing
for performance and recovery purposes.
55
Final Preparation Phase — User Training and Support
Duration
ID
TASK
69
81
82
83
84
85
86
87
88
89
90
Final Preparation Phase
Training Plans
Develop Final End User Training and Documentation Content
Prepare for End User Training and Documentation Delivery
Deliver End User Training
Train System Administration Staff
Define Long-Term Production Support Strategy
Refine Production Support Plan
Reorganize Team for Production Support
Establish Help Desk
Realization Review
10.5d
3.d
2.d
1.d
1.d
1.d
2.d
.25d
.25d
1.d
.5d
Start
6/10/05 8:00 AM
6/10/05 8:00 AM
6/10/05 8:00 AM
6/10/05 8:00 AM
6/12/05 8:00 AM
6/12/05 8:00 AM
6/17/05 1:00 PM
6/17/05 1:00 PM
6/17/05 3:00 PM
6/18/05 8:00 AM
6/19/05 8:00 AM
Finish
6/24/05 12:00 PM
6/12/05 5:00 PM
6/11/05 5:00 PM
6/10/05 5:00 PM
6/12/05 5:00 PM
6/12/05 5:00 PM
6/19/05 12:00 PM
6/17/05 3:00 PM
6/17/05 5:00 PM
6/18/05 5:00 PM
6/19/05 12:00 PM
Types of training:


 Vendor-based
Web-based
 Developers
 All users
 Support staff
 Training
 Tutorials
Instructor-led
 On-site
 Power users
Many BI projects succeed or fail based on
 Executives
how good the training and how well the user
support is organized and executed.
56
69
81
82
83
84
85
86
87
88
89
90
19-Jun
18-Jun
17-Jun
16-Jun
15-Jun
14-Jun
13-Jun
12-Jun
TASK
11-Jun
ID
10-Jun
Final Preparation Phase — User Training and
Support Dependencies
Final Preparation Phase
Training Plans
Develop End User Training and Documentation Content
Prepare for End User Training and Documentation Delivery
Deliver End User Training
Train System Administration Staff
Define Long-Term Production Support Strategy
Refine Production Support Plan
Reorganize Team for Production Support
Establish Help Desk
Realization Review
•
•
This is the time to execute the production support plans and reorganize the project team into a sustainable organization, or plan the
hand-off to a support organization if one exists
Remember to plan for the integration of your support plans with
your organization’s existing support systems
and help desk routing
57
Final Preparation Phase — The “Go” Decision
ID
TASK
69
91
92
93
94
95
96
97
98
99
100
101
102
Final Preparation Phase
Final Preparation Tasks
Transport to Production Environment
Perform Conversions
Cutover
Perform Cutover to Production System
Confirm Production Readiness
Verify Users are Ready
Final Preparation Review
Conduct Quality Check
Conduct Final Preparation Review
Sign off Final Preparation Phase
Final Approval for Going Live
•
•
Duration
Start
Finish
10.5d 6/10/05 8:00 AM 6/24/05 12:00 PM
5.5d 6/17/05 8:00 AM 6/24/05 12:00 PM
1.d 6/17/05 8:00 AM 6/17/05 5:00 PM
1.d 6/17/05 8:00 AM 6/17/05 5:00 PM
2.d 6/18/05 8:00 AM 6/19/05 5:00 PM
1.d 6/18/05 8:00 AM 6/18/05 5:00 PM
1.d 6/19/05 8:00 AM 6/19/05 5:00 PM
.25d 6/20/05 8:00 AM 6/20/05 10:00 AM
.5d 6/20/05 10:00 AM 6/20/05 3:00 PM
1.d 6/20/05 3:00 PM 6/23/05 3:00 PM
.5d 6/23/05 3:00 PM 6/24/05 10:00 AM
.25d 6/24/05 10:00 AM 6/24/05 12:00 PM
.d 6/24/05 12:00 PM 6/24/05 12:00 PM
A formal “go,” “no-go” decision should be made by the sponsor and
stakeholders at the end of the final preparation phase
Users will not remember if you bring the system online 14 days late,
but they will remember if it had major issues
Quality is paramount for each go-live.
58
24-Jun
23-Jun
22-Jun
21-Jun
20-Jun
19-Jun
TASK
18-Jun
ID
17-Jun
Final Preparation Phase — Dependencies
69 Final Preparation Phase
91
Final Preparation Tasks
92
Transport to Production Environment
93
Perform Conversions
94
Cutover
95
Perform Cutover to Production System
96
Confirm Production Readiness
97
Verify Users are Ready
98
Final Preparation Review
99
Conduct Quality Check
100
Conduct Final Preparation Review
101
Sign off Final Preparation Phase
102
Final Approval for Going Live
•
You can often cut over to the production box before the go-live

If you already have BI users live in-the-box, you can mask the new functionality
by not mapping the new queries to the user’s role menu until you are ready
If you are already live with other content, plan for a weekend
cut-over and spend Saturday to validate the production box.
This gives you Sunday to fix any major issues.
59
Go-Live — Some Key Observations
The last deliverable for the implementation
ensures high system performance through
monitoring and feedback.
We need to execute issue resolution plans
and contingency plans.
A “lessons learned” session should be held
at the end of the project to assure
organizational awareness and education.
The support organization will take over the
system after a pre-determined time period.
Some team members may transition into
their new roles as support staff.
This is a critical time when a “SWAT” team
that quickly addresses user concerns can
make all the difference in how the system is
received among the users.
Source: Pauline Woods-Wilson
Core Activities
5.1 Production Support
5.2 Project End
5.x Lessons Learned Review
60
Go-Live Activities
ID
103
104
105
106
107
108
109
110
111
112
113
114
115
TASK
Go Live and Support Phase
Setup Production Support
Go Live & Support Review
Provide Production Support
Post Go Live Activities
Review and Close Open Issues
Close Open Issues and Sign off Go-Live and
Review Business scenarios
Validate Live Business Process Results
Strategic BW Planning
Develop Strategic Plan for BW
Identify additional requirements concerning
Web Reporting and Bex Analyzer Reports and Layout
Duration
Start
Finish
5.d
1.d
.5d
.d
3.5d
1.d
1.d
1.d
.5d
1.d
.5d
.5d
6/24/05 1:00 PM
6/24/05 1:00 PM
6/25/05 1:00 PM
6/25/05 5:00 PM
6/26/05 8:00 AM
6/26/05 8:00 AM
6/26/05 8:00 AM
6/27/05 8:00 AM
6/30/05 8:00 AM
6/30/05 1:00 PM
6/30/05 1:00 PM
7/1/05 8:00 AM
7/1/05 12:00 PM
6/25/05 12:00 PM
6/25/05 5:00 PM
6/25/05 5:00 PM
7/1/05 12:00 PM
6/26/05 5:00 PM
6/26/05 5:00 PM
6/27/05 5:00 PM
6/30/05 12:00 PM
7/1/05 12:00 PM
6/30/05 5:00 PM
7/1/05 12:00 PM
.d
7/1/05 12:00 PM
7/1/05 12:00 PM
Project End
Maintain an issue log from two weeks before
go-live, until six weeks after the go-live.
Conduct a formal post implementation review
with team members to learn from the project.
61
1-Jul
30-Jun
29-Jun
28-Jun
27-Jun
26-Jun
TASK
25-Jun
ID
24-Jun
Go-Live — Post Go-Live Activities
103 Go Live and Support Phase
104 Setup Production Support
105 Go Live & Support Review
106 Provide Production Support
107 Post Go Live Activities
108
Review and Close Open Issues
109
Close Open Issues and Sign off Go-Live and Support Phase
110
Review Business scenarios
111
Validate Live Business Process Results
112
Strategic BW Planning
113
Develop Strategic Plan for BW
114
Identify additional requirements concerning Web Reporting and Bex Analyzer
115
Project End
Make sure all end-of-project decisions are
communicated before the project is closed.
62
What We’ll Cover …
•
•
•
•
•
•
•
Selecting an approach to use for your project
Defining project milestones
Allocating appropriate resources
Using SAP Solution Manager
Taking advantage of SAP Best Practices BI tool
Leveraging the SAP Best Practices work plan
Wrap-up
63
Resources
•
Jeremy Kadlec, Start to Finish Guide to IT Project
Management (NetImpress 2003, ISBN: B0000W86H2,
Digital)
• COMERIT.NET
presentations, tutorials, and articles
http://www.comerit.net
•
SAP Best Practices for Business Intelligence

http://help.sap.com/bp_biv170/index.htm
64
7 Key Points to Take Home
•
•
•
•
•
•
•
Use Best Practice deliverables — don’t create
from scratch
Download a sample work plan and enhance it
Organize your team early and provide training
Have a formal scope statement and change process
Spend no more than 15% of project time in the prep
phase and plan to use about 10 - 15% in total test time
(unit, system, integration, and performance)
Use strong dedicated BI development resources in
realization phase — learning while being productive is
almost impossible
Don’t keep too much detail in the work plan
65
Your Turn!
Questions?
How to contact me:
Dr. Bjarne Berg
[email protected]
66