PM05 Berg Writingasolid

© 2005 Wellesley Information Services. All rights reserved.

Writing Solid and Realistic Work Plans for an SAP BW Implementation ProjectBjarne BergMyITgroup

2

What We’ll Cover …

• Which approach to use for your project• Project milestones• Resources• The SAP Solution Manager• The SAP BI Best Practices tool• The SAP Best Practices work plan• Wrap-up

3



4

The Gray Areas of Methodologies

• A first step in determining how to write a work plan is to pick a methodology for your project. While ASAP is normally the default method, there are other alternatives.

Joint Application Design(JAD)

Rapid Application Development(RAD)

Extreme Programming(EP)

System development Life-Cycle based methodologies

(SDLC)

Impact of FailureLow High

Low

High

Time to Delivery

When to Select Different Methodologies

There are in fact several dimensions when multiple

methodologies can be employed, i.e., when time to delivery is moderate, or when the impact of failure

is moderate

There are in fact several dimensions when multiple

methodologies can be employed, i.e., when time to delivery is moderate, or when the impact of failure

is moderate

5

A Brief Look at ASAP

• ASAP for BW is based on many of the same ideas and approaches that are found in the ASAP methodology for 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

6

What is ASAP?

• Project Plan, Estimating

• Design Strategies, Scope Definition

• Documentation, Issues DB

• Workshop Agenda

• Questionnaires

• End-User Procedures

• Test Plans

• Technical Procedures

• Made Easy guidebooks (printout, data transfer, system administration …)

Fill in the BlankVersus

Start from Scratch

Fill in the BlankVersus

Start from Scratch

Examples for Accelerators:

7



8

Project Preparation – Some Key Observations

1.5 Technical Requirements Planning1.4 Project Kickoff1.3 Training Preparation1.2 Project Procedures1.1 Initial Project Planning

1.6 Quality Check Project Preparation

Core Activities

Project plan: This is the first cut. It focuses on milestones and work packages.


Project charter: Represents an agreement on, and commitment to, the deliverables of the project, as well as the time constraints, resources, standards, and budget of the project


Scope: Sets the initial definition of the projectScope: Sets the initial definition of the project

Project team organization: Sets the “who” of the project. This decides who will be involved and what their goal is.

Project team organization: Sets the “who” of the project. This decides who will be involved and what their goal is.

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

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

Source: Pauline Woods-Wilson

9

Project Preparation – The Milestone Plan

• The first work plan should only consist of core tasks, milestones, and their critical dates

• Resources are simply referred to by their role instead of the names of individuals. (This can be easily done afterwards when resources are assigned.)



To write the first cut project plan, you need to have determined scope,

resource need/availability, and time

To write the first cut project plan, you need to have determined scope,

resource need/availability, and time

10

Project Preparation – Milestone Dates



The Milestone plan should be published and posted on the walls

Do not “hide it” in the project managers drawers

The Milestone plan should be published and posted on the walls

Do not “hide it” in the project managers drawers

ID TASK Dur- ation Start Finish

2 Project Preparation 18 days 5/15/2005 6/2/200511 Blueprint Phase & Planning Phase 13 days 6/29/2005 7/12/200551 Project Realization 70 days 7/5/2005 9/13/200569 Final Preparation Phase 20 days 9/10/2005 9/30/2005103 Go Live and Support Phase 14 days 10/1/2005 10/15/2005

• The Milestone Plan should consist of all major phases, start and end dates, and duration

• The plan should also include special project dates and events such as workshops, project reviews, approvals, etc.

11



12

Resources – Roles

• BW projects consists of a team of highly-skilled individuals

• The quality of the people are much more important than the number –a skilled developer can accomplish correctly what three novice developers will mess up in the same amount of time

• Think of the project team as a set of roles and 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.

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.

Project ResourcesProgram/Project Manager Application ConsultantApplication Team MemberTechnical ConsultantTechnical Team MemberTechnical Team LeadHelp Desk Provider and ManagerBusiness Process Team LeadTraining and Documentation LeadCustomer Project Sponsor

13

Team Organization – Small Project for Single Subject Area

Four to five team members and normally Three to six months duration depending on scope

Basis and functional R/3 support

• These are roles, not positions (sometimes one team member can fill more than one role)

Project Sponsor

Project Manager

Business Team Technical Team

Business analyst

Presentation developer

BW Architect

ETL developer

This is a good organization for teams that use JAD or RAD as their development methodology

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.

This is a good organization for teams that use JAD or RAD as their development methodology

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.

14

Team Organization – Mid-Sized BW Projects

Basis and Functional R/3 SupportEight to ten team members and normally

Two to four months duration depending on scope

These are roles, not positions (sometimes one team member can fill more than one role)

Project Sponsor/Steering Committee

Project Manager

BWArchitect

Business Analyst(s)

Extract, Transforms, and Loads

Data Management(InfoCubes & ODS)

Presentation Developer(s)

Sr. Business analyst

Business analyst

Sr. ETL developer

ETL developer

Sr. BW developer

BW developer

Sr. Presentation developer

Presentation developer

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.

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.

15

Basis and Functional R/3 SupportFifteen to twenty-five team members and normally

Six to eighteen months duration depending on scope

Portal developer(s)

BW Architect

Business analyst/(sub-team lead)BW developerPresentation developer(s)ETL developer

Sales Team


Finance Team


Material Mgmt. Team

Project Manager

Project Sponsor/Steering Committee

This is an organized 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 a back-end architect are used on very large projects.

This is an organized 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 a back-end architect are used on very large projects.

Team Organization – Large BW Projects

16



17

KnowledgeManagement

TestManagement

ServiceDesk

ChangeManagement

ServiceDelivery

OPERATE

IMPLEMENT

OPTIMIZE

BusinessProcess

ProjectManagement

SolutionMonitoring

KnowledgeTransfer

SAP Solution Manager – Don’t Build Everything from Scratch

There are many shared documents and tools that you can incorporate into your project. Your work plan should reflect the time savings of using these accelerators.

This SAP Solution Manager is delivered as part of your annual maintenance fee

There are many shared documents and tools that you can incorporate into your project. Your work plan should reflect the time savings of using these accelerators.

This SAP Solution Manager is delivered as part of your annual maintenance fee

Content

Gateway to SAP

Tools

Implementation PlatformSolution MonitoringService DeskE-Learning *Upgrade *Change Request Management *

Implementation ContentRoadmapsServicesBest Practice Documents

SAP Active Global Support

Service Delivery Platform

*New in 2004

18

SAP Solutions Manager – What is Useful for BW?

Define customersolution

based onSAP processes

Define customersolution

based onSAP processes

BusinessBlueprint Configuration

Synchronize customer settings

Synchronize customer settings

Configure processesConfigure processes

ProjectPreparation

Define projectDefine project

Set up systemlandscape

Set up systemlandscape

Test processes Test processes

Testing Training

Define e-learning units

and create learning maps

Define e-learning units

and create learning maps

RoadmapsRoadmaps

Project AdministrationProject Administration

Issue Tracking/Monitoring/ReportingIssue Tracking/Monitoring/Reporting

Change ManagementChange Management

All items in the Solution Manager are not very useful for the BW project team. However, there is material that can be used. Collect the material and make it part of the

deliverables for you team. Write a work plan tasks that directly references these tasks.

All items in the Solution Manager are not very useful for the BW project team. However, there is material that can be used. Collect the material and make it part of the

deliverables for you team. Write a work plan tasks that directly references these tasks.

19



20

BI Best Practice – Gives You Many Templates and a Work Plan

• SAP BI Best Practices is a new tool with consolidated access to documentation, hints, white papers, recommendations, tools, and a sample work plan. It is all based on BI scenarios.

• SAP Best Practices is a tool 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

SAP Best Practices for business intelligence supports predefined scenarios that handle core BI business requirements

21

BI Best Practice

• This tool is still being enhanced, but has several BI specific project accelerators that you will not find in the Solution Manager

A test drive is available on the Web site: https://media.sdn.sap.com/html/submitted%5Fdocs/Best%5FPractices/BW/

A test drive is available on the Web site: https://media.sdn.sap.com/html/submitted%5Fdocs/Best%5FPractices/BW/

Most of the project management tools about staffing, planning, scoping, and work plans are found here

Most of the project management tools about staffing, planning, scoping, and work plans are found here

22

Many of your team’s deliverables can be downloaded here and you can incorporate them specifically

into your work plans

Many of your team’s deliverables can be downloaded here and you can incorporate them specifically

into your work plans

An Option – Work Plans Based on Deliverables

• The best practice documents are organized around scenarios which simplify the collection of tools

23

These are tools and accelerators that you can download and make deliverables in your work plan

These are tools and accelerators that you can download and make deliverables in your work plan

Deliverables for Your Work Plan

• This example of the sales analysis gives an overview of what BW has to offer, how to build it, and best practices for a variety of technical designs

24

An Option – Create Your Work Plan Based on Scenarios

• Each scenario is described in a process overview document

25

The installation guide has step-by-step scenarios based documentation. Do NOT replicate minute steps into the work plan; keep it at a high enough

level where it is useful, but not a burden to maintain.

The installation guide has step-by-step scenarios based documentation. Do NOT replicate minute steps into the work plan; keep it at a high enough

level where it is useful, but not a burden to maintain.Note

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. The BI tool has installation guides to assist.

26

BI Best Practice – What Versions Does It Support?

• The SAP Best Practices tool is developed for BW 3.5 and was tested with:

While the install recommendations are based on BW 3.5, most management tools, accelerators, and the sample work plan are not version specific

While the install recommendations are based on BW 3.5, most management tools, accelerators, and the sample work plan are not version specific

SAPKIBIEP20002352BI_CONT

SAPKIPYI6400042004_1_640PI_BASIS

SAPKW350040004350SAP_BW

SAPKA640040004640 SAP_ABA

SAPKB640040004640SAP_BASISSAP BW

Highest Support Package

LevelReleaseSoftware Component

mySAPApplication Component

Note

Source: SAP - Sept - 2005

27



28

The Sample Work Plan

• You can download the work plan from the Project Support area:

29

The Work Plan – Some Background

• The work plan on the SAP BI Best Practice CD is a Microsoft project plan file (.mpp)

• The work plan is only an example that you are expected 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.

30

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.

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.

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.

Project ResourcesProgram/Project ManagerApplication ConsultantApplication Team MemberTechnical ConsultantTechnical Team MemberTechnical Team LeadHelp Desk Provider and ManagerBusiness Process Team LeadTraining and Documentation LeadCustomer Project Sponsor

31

Project Preparation – Some Key Observations

1.5 Technical Requirements Planning1.4 Project Kickoff1.3 Training Preparation1.2 Project Procedures1.1 Initial Project Planning

1.6 Quality Check Project Preparation

Core Activities





Scope: Sets the initial definition of the projectScope: 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.

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, documents are handled, etc. means that everyone understands what is going on.

Standards and procedures: Sets the “why” and “how” of the project. Standardizing how meetings are run, documents are handled, etc. means that everyone understands what is going on.


32

The Project Preparation Phase

• While short in duration in this example, do not spend too much time on the project prep phase

• It is easy to get intimidated by the many unknowns. Rely on yourconsultants, but keep the momentum.

Spending more than 15% of your project time in this phase is a sign of analysis-paralysis

Spending more than 15% of your project time in this phase is a sign of analysis-paralysis

ID TASK Dur- ation

Start Finish

1 SAP Best Practices BI Implementation Roadmap - read Notes 24.5d 5/28/05 8:00 AM 7/1/05 12:00 PM2 Pre-Sales Phase / Project Preparation 4.d 5/28/05 8:00 AM 6/2/05 5:00 PM3 Perform Customer Workshop & present Best Practices in Demo System 1.5d 5/28/05 8:00 AM 5/29/05 12:00 PM4 Review and select scenarios that are best fit for customer requirements .5d 5/29/05 1:00 PM 5/29/05 5:00 PM5 Carry out review of delivered business content to check for gaps .5d 5/30/05 8:00 AM 5/30/05 12:00 PM6 Define Critical Success Factors .5d 5/30/05 1:00 PM 5/30/05 5:00 PM7 Validate & Document Technical Requirements .5d 6/2/05 8:00 AM 6/2/05 12:00 PM8 Define System Landscape Strategy (maybe 2 system landscape and/or SAP One .d 6/2/05 12:00 PM 6/2/05 12:00 PM9 Perform Hardware sizing .5d 6/2/05 1:00 PM 6/2/05 5:00 PM10 Install software 2.d 5/28/05 8:00 AM 5/29/05 5:00 PM

33

The Project Preparation Phase – Dependencies

A one-day workshop can remove project confusion and delays, help in getting the right requirements,

and avoid missing “low hanging fruit.”

A one-day workshop can remove project confusion and delays, help in getting the right requirements,

and avoid missing “low hanging fruit.”

• A key to the project prep phase is the level setting of all parties. Dedicate a day to a workshop with stakeholders, managers, and sponsors

• Dedicate some time early in the workshop to demo BW and discuss capabilities of the tool set

ID TASK

28-M

ay

29-M

ay

30-M

ay

31-M

ay

1-Ju

n

2-Ju

n

1 SAP Best Practices BI Implementation Roadmap - read Notes2 Pre-Sales Phase / Project Preparation3 Perform Customer Workshop & present Best Practices in Demo System4 Review and select scenarios that are best fit for customer requirements5 Carry out review of delivered business content to check for gaps6 Define Critical Success Factors7 Validate & Document Technical Requirements8 Define System Landscape Strategy (maybe 2 system landscape and/or SAP One 9 Perform Hardware sizing

34

The Blueprinting Phase – Some Key Observations

2.7 Quality Check Business Blueprint

2.5 Organizational Structure Definition2.4 Develop System Environment2.3 Project Team Training Business Blueprint2.2 Organizational Change Management2.1 Project Management Business Blueprint

2.6 Business Process Definition

Core Activities

Deciding what will be developed inBW and what will be maintained as R/3 reports

Deciding what will be developed inBW and what will be maintained as R/3 reports

Getting the right requirements:Finding out the detailed functional specs of what the users really needand not just what they want

Getting the right requirements:Finding out the detailed functional specs of what the users really needand not just what they want

Map the functional requirements to the standard content and see what can be leveraged and what needs to be extended

Map the functional requirements to the standard content and see what can be leveraged and what needs to be extended

Create user acceptance group(s) and have them review and give feedback on the system as it is developed

Create user acceptance group(s) and have them review and give feedback on the system as it is developed

Create detailed technical specifications and designs of InfoCubes, MasterData, ODSs and high-level architectural designs

Create detailed technical specifications and designs of InfoCubes, MasterData, ODSs and high-level architectural designs

35

The Blueprinting Phase – Planning

• 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

Spend some time early on to plan user training and support; also, formalize your team organization

ID TASK Dur- Start Finish1 SAP Best Practices BI Implementation Roadmap - read Notes 24.5d 5/28/05 8:00 AM 7/1/05 12:00 PM11 Blueprint Phase & Planning Phase 9.5d 5/29/05 5:00 PM 6/12/05 12:00 PM12 Apply for Going Live Check .d 5/29/05 5:00 PM 5/29/05 5:00 PM13 Finalize Project Scope [selected scenarios] 1.d 5/30/05 8:00 AM 5/30/05 5:00 PM14 Check Content delivered by Best Practices .5d 5/30/05 8:00 AM 5/30/05 12:00 PM15 Determine those issues affecting BW Implementation and assign risk to project .25d 5/30/05 1:00 PM 5/30/05 3:00 PM16 Present Final Scope to Customer and Get Signoff of Scope .25d 5/30/05 3:00 PM 5/30/05 5:00 PM17 Project Planning Phase 8.d 5/30/05 8:00 AM 6/10/05 5:00 PM18 Set Up Development Environment .25d 5/30/05 8:00 AM 5/30/05 10:00 AM19 Define transport Strategy .25d 5/30/05 8:00 AM 5/30/05 10:00 AM20 Activate TMS .25d 5/30/05 8:00 AM 5/30/05 10:00 AM21 Define Project Organization and Create Teams 3.d 6/2/05 8:00 AM 6/4/05 5:00 PM22 Analyze Roles and Tasks by Standard Content Areas and Technical .25d 6/2/05 8:00 AM 6/2/05 10:00 AM23 Update delivered Project Plan & finalize, including resources assignments .25d 6/2/05 10:00 AM 6/2/05 12:00 PM24 Define customer rollout & training strategy for SAP BW 1.d 6/2/05 8:00 AM 6/2/05 5:00 PM25 Define types of users of the BW .33d 6/2/05 8:00 AM 6/2/05 10:38 AM26 Determine Number of users for BW .33d 6/2/05 10:38 AM 6/2/05 2:17 PM27 Determine Data Access Requirements .34d 6/2/05 2:17 PM 6/2/05 5:00 PM

36

The Blueprinting Phase – Planning Dependencies

• Many tasks can take place at the same time. The trick is to make sure that all team members are active and that the workload is evenly loaded throughout the project.

Spend some time on resource loading and workload balancing. Not all tasks are dependent.

Spend some time on resource loading and workload balancing. Not all tasks are dependent.

ID TASK

28-M

ay

29-M

ay

30-M

ay

31-M

ay

1-Ju

n

2-Ju

n

1 SAP Best Practices BI Implementation Roadmap - read Notes11 Blueprint Phase & Planning Phase12 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 Scope17 Project Planning Phase18 Set Up Development Environment19 Define transport Strategy20 Activate TMS21 Define Project Organization and Create Teams22 Analyze Roles and Tasks by Standard Content Areas and Technical 23 Update delivered Project Plan & finalize, including resources assignments24 Define customer rollout & training strategy for SAP BW 25 Define types of users of the BW26 Determine Number of users for BW27 Determine Data Access Requirements

37

The Blueprinting Phase – Design, Architecture, and Training

Define clearly when each datastore has to be loaded (time) and the frequency of the loads

Define clearly when each datastore has to be loaded (time) and the frequency of the loads

• 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, BW install, etc.)

ID TASK Dur- ation

Start Finish

11 Blueprint Phase & Planning Phase 9.5d 5/29/05 5:00 PM 6/12/05 12:00 PM17 Project Planning Phase 8.d 5/30/05 8:00 AM 6/10/05 5:00 PM24 Define customer rollout & training strategy for SAP BW 1.d 6/2/05 8:00 AM 6/2/05 5:00 PM25 Define types of users of the BW .33d 6/2/05 8:00 AM 6/2/05 10:38 AM26 Determine Number of users for BW .33d 6/2/05 10:38 AM 6/2/05 2:17 PM27 Determine Data Access Requirements .34d 6/2/05 2:17 PM 6/2/05 5:00 PM28 Business Information Warehouse Design/Archetecture Design & 3.d 6/2/05 8:00 AM 6/4/05 5:00 PM29 Document which parts of Best Practices and SAP Content are used 1.d 6/2/05 8:00 AM 6/2/05 5:00 PM30 Document Data Flow Procedures 1.d 6/3/05 8:00 AM 6/3/05 5:00 PM31 Define / Document Data Access Design .25d 6/4/05 8:00 AM 6/4/05 10:00 AM32 Define /document Authorization Strategy Design .25d 6/4/05 10:00 AM 6/4/05 12:00 PM33 Define Data Load Requirements .5d 6/4/05 1:00 PM 6/4/05 5:00 PM34 Technical/Hardware Validation .5d 6/2/05 8:00 AM 6/2/05 12:00 PM35 Confirm Hardware Readiness .5d 6/2/05 1:00 PM 6/2/05 5:00 PM36 Define BW Performance and Load Aspects .5d 6/2/05 8:00 AM 6/2/05 12:00 PM

38

The Blueprinting Phase – Planning

Plan time on the work plan for early training of your staff members

Ideal Years Experience (minimum)

Training Days (if new in the

role)

In-House Training

DaysBW Developer 2+ 15 3-5ETL Developer 3+ 15-20 3-5Presentation Developer 1+ 5-10 3-5Project Manager 5+ 10-15 3-5Business Analysts 5+ 5-10 3-5

Issue

39

The Blueprinting Phase – Project Management and Test Plans

• Make sure that you plan detailed procedures for transporting objects between the development, testing, and production landscape

• Much like an R/3 project, you should plan to test the security/roles, the load programs, update and transfer rules, as well as the 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

You should plan to spend about 20-40% of your project time on testing and fixes

ID TASK Dur- ation

Start Finish

11 Blueprint Phase & Planning Phase 9.5d 5/29/05 5:00 PM 6/12/05 12:00 PM17 Project Planning Phase 8.d 5/30/05 8:00 AM 6/10/05 5:00 PM37 Project Procedures 1.d 6/2/05 8:00 AM 6/2/05 5:00 PM38 Update Project Management Standards and Operating Procedures .5d 6/2/05 8:00 AM 6/2/05 12:00 PM39 Update Implementation Standards and Procedures to include BW specific .5d 6/2/05 1:00 PM 6/2/05 5:00 PM40 Update SAP System Admin Procedures .5d 6/2/05 1:00 PM 6/2/05 5:00 PM41 Test plans 4.d 6/5/05 8:00 AM 6/10/05 5:00 PM42 Define BW Test Plans 1.d 6/5/05 8:00 AM 6/5/05 5:00 PM43 Define Data Flow & Validation Test Plans .5d 6/6/05 8:00 AM 6/6/05 12:00 PM44 Define Data Access Test Plans .5d 6/6/05 1:00 PM 6/6/05 5:00 PM45 Define Authorizations Test Plan .5d 6/9/05 8:00 AM 6/9/05 12:00 PM46 Develop System Test Plans .5d 6/9/05 1:00 PM 6/9/05 5:00 PM47 Develop Technical Test Plans .5d 6/10/05 8:00 AM 6/10/05 12:00 PM48 Develop Functional/Performance Test Plans .5d 6/10/05 1:00 PM 6/10/05 5:00 PM

40

The Blueprinting Phase – Project Management, Test Plans, Dependencies

R/3 and BW testing is not different from a

methodology standpoint, but the

execution is

R/3 and BW testing is not different from a

methodology standpoint, but the

execution is

ID TASK

5-Ju

n

6-Ju

n

7-Ju

n

8-Ju

n

9-Ju

n

10-J

un

11 Blueprint Phase & Planning Phase17 Project Planning Phase37 Project Procedures38 Update Project Management Standards and Operating Procedures39 Update Implementation Standards and Procedures to include BW specific 40 Update SAP System Admin Procedures41 Test plans42 Define BW Test Plans43 Define Data Flow & Validation Test Plans44 Define Data Access Test Plans45 Define Authorizations Test Plan46 Develop System Test Plans47 Develop Technical Test Plans48 Develop Functional/Performance Test Plans

Test Strategy

Test Plan

Test Execution

Problem Resolution

41

The Realization Phase – Some Key Observations

3.8 Data Conversion Programs (if any)3.7 Prepare External Interfaces (non R/3)

3.5 System Management3.4 Baseline Configuration (content activation)3.3 Training Development and Approvals3.2 Organizational Change Management3.1 Project Management Realization

3.6 Final Configuration (enhancements)

Core Activities

3.9 Develop Queries3.10 Develop User Interface Enhancements3.11 Determine Additional Reporting Requirements3.12 Create Structured Reports (i.e., third party)3.13 Establish Authorization Concept3.14 Establish Data Archiving plan (if applicable)3.15 Final Integration Test3.16 Quality Check Realization

Configuration: Activate content, make extensions to BW standard content, execute test data and masterdata loads, validate data quality, build and modify transfer and/or update rules

Configuration: Activate content, make extensions to BW standard content, execute test data and masterdata loads, validate data quality, build and modify transfer and/or update rules

Development Programs: Provide details of added programming structures

Development Programs: Provide details of added programming structures

End User: Training Material, Manuals, Web site, on-line help

End User: Training Material, Manuals, Web site, on-line help

Testing: Unit testing by developers, acceptance testing by business analysts, system and integration testing by users

Testing: Unit testing by developers, acceptance testing by business analysts, system and integration testing by users

42

The Realization Phase – Development Core ActivitiesID TASK Dur-

ationStart Finish

51 Project Realization 6.25d 6/5/05 8:00 AM 6/13/05 10:00 AM52 BW Development Configuration 3.d 6/5/05 8:00 AM 6/9/05 5:00 PM53 Implement relevant Best Practices scenarios 3.d 6/5/05 8:00 AM 6/9/05 5:00 PM54 Configure Data Access Environment .25d 6/5/05 8:00 AM 6/5/05 10:00 AM55 Source Data Quality Validation .75d 6/5/05 10:00 AM 6/5/05 5:00 PM56 Collect Representitive Sample of Source Data (Transaction and Master) .5d 6/6/05 8:00 AM 6/6/05 12:00 PM57 Identify and List all issues with transaction/master data .5d 6/6/05 1:00 PM 6/6/05 5:00 PM58 Implement Standard Authorization Concept - Development Environment 1.d 6/9/05 8:00 AM 6/9/05 5:00 PM59 Document those issues affecting BW Implementation and assign risk to project .25d 6/9/05 8:00 AM 6/9/05 10:00 AM60 Communicate issues to customer and agree on criteria to clean data .5d 6/9/05 10:00 AM 6/9/05 3:00 PM61 Provide customer report on findings and agree on go forward strategy to clean .25d 6/9/05 3:00 PM 6/9/05 5:00 PM

If BW is new in the organization

you should seriously consider hiring experienced BW developer(s)

or rely on external resources during

this phase

If BW is new in the organization

you should seriously consider hiring experienced BW developer(s)

or rely on external resources during

this phase

1 Review the functional requirements and the technical design

6 Do not allow exceptions to the naming conventions

2 Make sure you have established data stewards for the masterdata and assigned the masterdata to specific developers

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 Keep details for multi-use in the ODS and do not design the ODS based on a the needs of a single infoCube.

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.

10 Developers must perform unit test on all their work and personally sign-off on their storage object.

TIPS FOR MAKING THE REALIZATION PHASE SUCCESSFUL

43

• The majority of issues during this phase will be data extraction, loading transformation, and loading. While you cannot plan for all issues, you can set aside time to deal with them.

The Realization Phase – Development Core Dependencies

Data cleansing should occur in the source system (hint: Cover this in the scope statement)

Data cleansing should occur in the source system (hint: Cover this in the scope statement)

ID TASK Dur- ation 5-

Jun

6-Ju

n

7-Ju

n

8-Ju

n

9-Ju

n

51 Project Realization 6.25d52 BW Development Configuration 3.d53 Implement relevant Best Practices scenarios 3.d54 Configure Data Access Environment .25d55 Source Data Quality Validation .75d56 Collect Representitive Sample of Source Data (Transaction and Master) .5d57 Identify and List all issues with transaction/master data .5d58 Implement Standard Authorization Concept - Development Environment 1.d59 Document those issues affecting BW Implementation and assign risk to project .25d60 Communicate issues to customer and agree on criteria to clean data .5d61 Provide customer report on findings and agree on go forward strategy to clean .25d

44

The Realization Phase – Testing Core ActivitiesID TASK Dur-

ationStart Finish

51 Project Realization 6.25d 6/5/05 8:00 AM 6/13/05 10:00 AM62 Quality Assurance Environment 3.25d 6/10/05 8:00 AM 6/13/05 10:00 AM63 Set Up Quality Assurance Environment .5d 6/10/05 8:00 AM 6/10/05 12:00 PM64 Transport Requests from Dev .25d 6/10/05 1:00 PM 6/10/05 3:00 PM65 Load data from R/3 QA Environment 1.d 6/10/05 3:00 PM 6/11/05 3:00 PM66 Test QA Environment 2.5d 6/10/05 3:00 PM 6/13/05 10:00 AM67 BW Quality Assurance Configuration .5d 6/10/05 3:00 PM 6/11/05 10:00 AM68 Execute BW Test Plans in Quality Environment 2.d 6/11/05 10:00 AM 6/13/05 10:00 AM

Tasks\Dates December 2003 January 2004 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. Business analysts are responsible for planning and executing the system testing of queries.

“There's no time to stop for

gas, we're already late” –

testing is not a waste of time!

45

The Realization Phase – Testing Core Dependencies

ID TASK

10-J

un

11-J

un

12-J

un

13-J

un

51 Project Realization62 Quality Assurance Environment63 Set Up Quality Assurance Environment64 Transport Requests from Dev65 Load data from R/3 QA Environment66 Test QA Environment67 BW Quality Assurance Configuration68 Execute BW Test Plans in Quality Environment

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.

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.

1 Create test script 6 Identify key contacts 2 Identify roles to be used 7 Communicate about transports3 Documentation on using test tools 8 Arrange time for progress control4 Procedure for documenting test results 9 Schedule facilities5 Training sessions for using test scripts

Tasks

46

The Final Preparation Phase – Some Key Observations

4.7 Quality Check Final Preparation

4.5 Detailed Cutover Planning4.4 System Management4.3 Stress and Volume Testing4.2 Training Final Preparation4.1 Project Management Final Preparation

4.6 Cutover

Core Activities

The Cutover Plan and the Technical Operations Manual describe the details on how to move to the production environment and Go-Live

The Cutover Plan and the Technical Operations Manual describe the details on how to move to the production environment and Go-Live

The End-User Training Documentdescribes the delivery of the necessary levels of SAP training prior to going live

The End-User Training Documentdescribes the delivery of the necessary levels of SAP training prior to going live

The Stress and Volume Tests confirm the production hardware’s capabilities

The Stress and Volume Tests confirm the production hardware’s capabilities


47

The Final Preparation Phase – System TestingID TASK Dur-

ationStart Finish

69 Final Preparation Phase 10.5d 6/10/05 8:00 AM 6/24/05 12:00 PM70 Setup Production Environment 3.d 6/13/05 10:00 AM 6/18/05 10:00 AM71 Define Production System Design .5d 6/13/05 10:00 AM 6/13/05 3:00 PM72 Set Up Production Environment .5d 6/13/05 3:00 PM 6/16/05 10:00 AM73 Confirm BW Production Configuration 2.d 6/16/05 10:00 AM 6/18/05 10:00 AM74 Execute BW Test Plans in Production Environment 2.d 6/16/05 10:00 AM 6/18/05 10:00 AM75 Conduct System Tests 3.d 6/16/05 10:00 AM 6/19/05 10:00 AM76 Conduct System Administration Tests .25d 6/16/05 10:00 AM 6/16/05 12:00 PM77 Conduct Backup and Restore Procedure Test .5d 6/16/05 1:00 PM 6/16/05 5:00 PM78 Conduct Failure Scenarios Test .5d 6/16/05 1:00 PM 6/16/05 5:00 PM79 Conduct Disaster Recovery Test .5d 6/17/05 8:00 AM 6/17/05 12:00 PM80 Conduct Going Live Check 1.d 6/18/05 10:00 AM 6/19/05 10:00 AM

Performance test execution1. Identify queries to be performance tuned 2. Determine cut-off load – i.e., 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 benchmarks5. If needed, build aggregates, indexes, etc. 6. Record findings in a formal tracking tool available to everyone

48

The Final Preparation Phase – System Testing DependenciesID TASK

10-J

un

11-J

un

12-J

un

13-J

un

14-J

un

15-J

un

16-J

un

17-J

un

18-J

un

19-J

un

69 Final Preparation Phase70 Setup Production Environment 71 Define Production System Design72 Set Up Production Environment73 Confirm BW Production Configuration74 Execute BW Test Plans in Production Environment75 Conduct System Tests76 Conduct System Administration Tests77 Conduct Backup and Restore Procedure Test78 Conduct Failure Scenarios Test79 Conduct Disaster Recovery Test80 Conduct Going Live Check

Don’t underestimate the need for system testing for performance and recovery purposes

Don’t underestimate the need for system testing for performance and recovery purposes

• A typical back-up strategy is to 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?)

49

The Final Preparation Phase – User Training and Support

Many BI projects succeed or fail based on how good the training and well the user support is

organized and executed

Many BI projects succeed or fail based on how good the training and well the user support is

organized and executed

ID TASK Dur- ation

Start Finish

69 Final Preparation Phase 10.5d 6/10/05 8:00 AM 6/24/05 12:00 PM81 Training Plans 3.d 6/10/05 8:00 AM 6/12/05 5:00 PM82 Develop Final End User Training and Documentation Content 2.d 6/10/05 8:00 AM 6/11/05 5:00 PM83 Prepare for End User Training and Documentation Delivery 1.d 6/10/05 8:00 AM 6/10/05 5:00 PM84 Deliver End User Training 1.d 6/12/05 8:00 AM 6/12/05 5:00 PM85 Train System Administration Staff 1.d 6/12/05 8:00 AM 6/12/05 5:00 PM86 Define Long-Term Production Support Strategy 2.d 6/17/05 1:00 PM 6/19/05 12:00 PM87 Refine Production Support Plan .25d 6/17/05 1:00 PM 6/17/05 3:00 PM88 Reorganize Team for Production Support .25d 6/17/05 3:00 PM 6/17/05 5:00 PM89 Establish Help Desk 1.d 6/18/05 8:00 AM 6/18/05 5:00 PM90 Realization Review .5d 6/19/05 8:00 AM 6/19/05 12:00 PM

Types of training:! Web-based

! All users! Training ! Tutorials

! Instructor-led ! On-site! Power users! Executives

! Vendor-based ! Developers ! Support staff

50

• This is the time to execute the production support plans and re-organize 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

The Final Preparation Phase – DependenciesID TASK

10-J

un

11-J

un

12-J

un

13-J

un

14-J

un

15-J

un

16-J

un

17-J

un

18-J

un

19-J

un

69 Final Preparation Phase81 Training Plans82 Develop End User Training and Documentation Content 83 Prepare for End User Training and Documentation Delivery84 Deliver End User Training85 Train System Administration Staff86 Define Long-Term Production Support Strategy87 Refine Production Support Plan88 Reorganize Team for Production Support89 Establish Help Desk90 Realization Review

51

The Final Preparation Phase – The “Go” Decision

Quality is paramount for each go-live Quality is paramount for each go-live

• 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

ID TASK Dur- ation

Start Finish

69 Final Preparation Phase 10.5d 6/10/05 8:00 AM 6/24/05 12:00 PM91 Final Preparation Tasks 5.5d 6/17/05 8:00 AM 6/24/05 12:00 PM92 Transport to Production Environment 1.d 6/17/05 8:00 AM 6/17/05 5:00 PM93 Perform Conversions 1.d 6/17/05 8:00 AM 6/17/05 5:00 PM94 Cutover 2.d 6/18/05 8:00 AM 6/19/05 5:00 PM95 Perform Cutover to Production System 1.d 6/18/05 8:00 AM 6/18/05 5:00 PM96 Confirm Production Readiness 1.d 6/19/05 8:00 AM 6/19/05 5:00 PM97 Verify Users are Ready .25d 6/20/05 8:00 AM 6/20/05 10:00 AM98 Final Preparation Review .5d 6/20/05 10:00 AM 6/20/05 3:00 PM99 Conduct Quality Check 1.d 6/20/05 3:00 PM 6/23/05 3:00 PM100 Conduct Final Preparation Review .5d 6/23/05 3:00 PM 6/24/05 10:00 AM101 Sign off Final Preparation Phase .25d 6/24/05 10:00 AM 6/24/05 12:00 PM102 Final Approval for Going Live .d 6/24/05 12:00 PM 6/24/05 12:00 PM

52

The Final Preparation Phase – Dependencies

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.

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.

• You can often cut over to the production box before the go-live. If you already have BI user 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

ID TASK

17-J

un

18-J

un

19-J

un

20-J

un

21-J

un

22-J

un

23-J

un

24-J

un

69 Final Preparation Phase91 Final Preparation Tasks92 Transport to Production Environment93 Perform Conversions94 Cutover95 Perform Cutover to Production System96 Confirm Production Readiness97 Verify Users are Ready98 Final Preparation Review99 Conduct Quality Check100 Conduct Final Preparation Review101 Sign off Final Preparation Phase102 Final Approval for Going Live

53

Go-Live – Some Key Observations

5.2 Project End

5.x Lessons learned review

5.1 Production SupportCore Activities

The last deliverable for the implementation ensures high system performance through monitoring and feedback

The last deliverable for the implementation ensures high system performance through monitoring and feedback


We need to execute issue resolution plans and contingency plans

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

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

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

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

54

Go-Live Activities

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.

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.

ID TASK Dur- ation

Start Finish

103 Go Live and Support Phase 5.d 6/24/05 1:00 PM 7/1/05 12:00 PM104 Setup Production Support 1.d 6/24/05 1:00 PM 6/25/05 12:00 PM105 Go Live & Support Review .5d 6/25/05 1:00 PM 6/25/05 5:00 PM106 Provide Production Support .d 6/25/05 5:00 PM 6/25/05 5:00 PM107 Post Go Live Activities 3.5d 6/26/05 8:00 AM 7/1/05 12:00 PM108 Review and Close Open Issues 1.d 6/26/05 8:00 AM 6/26/05 5:00 PM109 Close Open Issues and Sign off Go-Live and 1.d 6/26/05 8:00 AM 6/26/05 5:00 PM110 Review Business scenarios 1.d 6/27/05 8:00 AM 6/27/05 5:00 PM111 Validate Live Business Process Results .5d 6/30/05 8:00 AM 6/30/05 12:00 PM112 Strategic BW Planning 1.d 6/30/05 1:00 PM 7/1/05 12:00 PM113 Develop Strategic Plan for BW .5d 6/30/05 1:00 PM 6/30/05 5:00 PM114 Identify additional requirements concerning

Web Reporting and Bex Analyzer Reports and Layout.5d 7/1/05 8:00 AM 7/1/05 12:00 PM

115 Project End .d 7/1/05 12:00 PM 7/1/05 12:00 PM

55

Go-Live – Post Go-Live ActivitiesID TASK

24-J

un

25-J

un

26-J

un

27-J

un

28-J

un

29-J

un

30-J

un

1-Ju

l

103 Go Live and Support Phase104 Setup Production Support105 Go Live & Support Review106 Provide Production Support107 Post Go Live Activities108 Review and Close Open Issues109 Close Open Issues and Sign off Go-Live and Support Phase110 Review Business scenarios111 Validate Live Business Process Results112 Strategic BW Planning 113 Develop Strategic Plan for BW114 Identify additional requirements concerning Web Reporting and Bex Analyzer 115 Project End

AlignmentAlignment BenefitsBenefits

Capability/EfficiencyCapability/EfficiencyIntegrationIntegration

Are we doingthe right things?

Are we doingthem the right way?

Are we getting the benefits?

Are we getting them done well?

56



57

Resources

Start to Finish Guide to IT Project Management by JeremyKadlec, Digital: 109 pages. Publisher: NetImpress; ISBN:B0000W86H2

Information Technology Project Management, Second Edition byKathy Schwalbe. 561 pages. Publisher: Course Technology;ISBN: 0619035285

BI Best Practices, SAP Development Network:https://media.sdn.sap.com/html/submitted%5Fdocs/Best%5FPrctices/BW

58

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 20% of project time in the prep phase

and plan to use about 20-40% in total test time (unit, system, integration, and performance)

59

7 Key Points to Take Home (cont.)

• Use strong dedicated BI development resources in the realization phase. Learning while being productive is almost impossible.

• Don’t keep too much detail in the work plan. Show what should be done, not how to do it. ! If your work plan exceeds 200-300 line items you probably

have too much detail

60

Your Turn!

How to contact me:Dr. Bjarne Berg

[email protected]

Questions?

PM05 Berg Writingasolid

Documents

Transcript of PM05 Berg Writingasolid