HANA Mang Presen

7/31/2019 HANA Mang Presen

1/14

HANA Iterations ImplementationMethodologyIntroduction & High-Level Overview


2/14

2011 SAP AG. All rights reserved. 2

Agenda

1. What are HANA Iterations?

2. How does it work?

3. HANA Iterations Benefits

4. HANA Iterations Prerequisites


3/14


What are HANA Iterations?

The term HANA Iterations means light or quick.

Based on LEAN software development (SCRUM, XP).

SAP NL took this as a basis and adapted it to SAP project implementations.

Most important characteristics:

Breaks tasks into small increments.

Iterations are short time frames ('time-boxed).

Each iteration is worked on by a team through a full cycle, including planning,requirements analysis, design, coding/configuration, unit testing, and acceptance

testing when a working product is demonstrated to stakeholders.

Concentrate on most valuable functionality first.


4/14


Agenda






5/14


Overview of HANA Iterations Business Add-on to ASAP

ProjectPreparation

Blueprint Realization

ProcessComposition

ServiceModeling

ServiceImplementation

and Test

UI Development

2-to-4 wks

cycle

FinalPreparation

Go LiveSupport

Run


6/14


Data Management

RUN SAP

Organisational Change Mangement

Hybrid HANA Iterations- ASAP 7 Acceleration Add-On

ProjectPrep.

Baseline

Build

Working

Software

Release 1

Delta List

Sprint

Sprint

Sprint

Busine

ssPriority

Time

Project

PrepRealisation Release 1

Demo

Evaluate

Demo

Demo

GoLiv

e

Define&AnalyzeScope

DemoSAPStand

ard

Settingthesce

ne

Must

ShouldCould

16

15

14

13

12

11

10

09

0807

06

05

0403

02

01

Would

Blue PrintFinal

Prep

Go-Live

Support

Demo

Support

Evaluation

&Relea

se

Planin

g

ITFinalPrep.

Prep. Sprint

Sprint

Release2

Sign-O

ff

Realisation Release 2

Demo

Demo

S

ProcessW

S

&Sol.Arc

hit.

4

5

1

8

2

7

3

4

2

2

4

3

36

4

5

Priority Effort

Accelerators

Checkpoint

Checkpoint

Checkpoint

Enablement

Gettingthe

organizationready


7/14 2011 SAP AG. All rights reserved. 7

Sprint

2-4 weeks

Objective: Potentially shippable Software



Agenda







Advantages at a glance

After each iteration

working software isdelivered

Value: Customer

gets what he wants.

working software

delivered based on

value prioritized bycustomer

Working software is

measure for progressRegular

Checkpoints (demos)

to check

requirements and

results with business

Risks are quicklyidentified and better

manageable

Can respond to

changes per sprintThe customer

discovers what he

wants. Can take

account of insight

into the business.

Faster Results More Transparency Increased Flexibility



Agenda







HANA Iterations Prerequisites

Before starting with a HANA project

Prepare your Organization & align stakeholdersUnderstanding the rules of HANA Iterations (Change is normal, adapt, scope,

speed, business driven projects)

Align stakeholders what to expect from HANA Iterations project approach

(chances, risks)

Assign proper resources (quantitative & qualitative) to the project and havethem focus on the project.

Identify capable business process owners (product owners)= one of the most critical success factors

Fast decision making necessary, you need to empower the key people but they

also need to know when its time to involve the Steering Committee.

Be available on a daily basis and mandatory participation in Daily Scrum

meeting, Sprint meeting, demo, lessons learned etc.

Know your objectives and the business prioritiesKnow the To Be (not As-is) processes in scope

Know what you want to achieve and what brings value for your organization.



HANA Iterations Mind Set- Customers Perspective

Before starting with an Agile project

Start with Standard SAPFrom Functionality and Business Process Perspective

Set the right expectations to the organization

Invest in training & Coaching- Mind ChangeTrain your process owners and implementation team in HANA Iterations & SAP

functionality

HANA Coaching

Prepare IT Operations

IT Landscape to be available on time before Baseline starts

IT Operations to handle requests on timely manner

In case of outsourcing partners get commitment from them

Define level of documentation & align expectationsAddress Organizational Change Management & Communication timely



Discussing ASAP_HANAThere are different levels of HANA Iterations

Conditions that Challenge HANA Iterations

HANA Hardware available and ready to start design.

(SAP SLT, DATA Loads)

Lack of business contributions and commitment or

slow decision-making.

Physically separated project team members.

Separation reduces the efficiency of an Agile

communication process.

Limited possibilities to slice & dice: Implementation

projects with complex system landscapes and

interdependent applications that share data structures

and processes, which cannot be replaced separately

makes management of dependencies more

challenging.

Initiatives that require long term planning and

approval processes due to organizational strategic

commitments or the nature of the industry (e.g.

regulated industries)

Acceleration techniques need to be tailored

To the customers situation, culture, and risk profile

Good Practices of HANA Iterations

Leverage HANA Models and Best Practice Processes

as a baseline to add value in short iterations.

Identify bite size pieces: work with a manageable

scope of processes and controllable dependencies

Gain buy in and build confidence through early review

cycles: receive early and frequent confirmation that

their requirements can be met

Succeed through incremental improvements and

growing functionality

Allow for flexibility - Ability to respond to change

through manageable portions

Manage deadlines Time is fixed- scope will be

adapted


14/14

Thank You!

Contact information:

F name MI. L name

Title

Address

Phone number

Documents

HANA Mang Presen