SAP TechEd 2017 CPL216 - Continuous Delivery. An Introduction

EXTERNAL
CPL126 – Continuous Delivery
An Introduction.

2EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Speakers 2017
Las Vegas
September 25 - 29
Bangalore
October 25 - 27
Barcelona
November 14 - 16
Dirk Lüdtke
Christoph Szymanski
Ganesh Poojar Christoph Szymanski
Wolfram Kramer

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service
or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related
document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this
presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided
without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross
negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.
Disclaimer

What this Session is about
Never
change a running
System
Change
as often as
Possible

What this Session is about
Never
change a running
System
Change
as often as
Possible
Continuous Delivery
… is the ability to get changes of all types - including new features,
configuration changes, bug fixes and experiments - into production,
or into the hands of users, safely and quickly in a sustainable way.

What slows us down?
Never
change a running
System
Change
as often as
Possible
unclear
requirements
features that don’t meet
business needs
lack of transparency
who is doing what
fear to break something
manual processes
complex release
dependencies
lack of modern
development
skills
inefficient testing
silos and inconsistent
solutions
late fixing
and reworks

It is not just a technical Transformation
improve
experience
Continuous
Delivery
Process
for Continuous Delivery
Process to get changes into
Production – fast – safely -
sustainable
Accelerator
improve
experience
DevOps
Close cross function
collaboration
to gain speed
Foundation
Skills and methods to do
the right things
and things right
improve
experience
Agile

Measure
the
Success
time to market
from idea to availability
shipped defects
number of fixes required
work-life balance
of your Workforce
customer feedback
&satisfaction
Step 1: Bring in the Business Perspective
Possible Success Indicators
High Risk
Change
time
$
Low Risk
Change
time
$

Building the Foundation for Continuous Delivery
improve
experience
Continuous
Delivery
Process
sustainable
Accelerator
improve
experience
DevOps
collaboration
to gain speed
Foundation
the right things
and things right
improve
experience
Agile

Scrum, Kanban, … – what really counts at the end of the day
Short
cycle
Product
Backlog
Team
Backlog
Working Product
Version
Iterate in small cycles!
Adjust the plan by listening to the experts.

What is Agile Software Engineering?
Unit
Testing
Test
Isolation
Test
Driven
Development
Clean
Code
Refactoring
Continuous
Integration
Pair
Programming
Exploratory
Testing
Acceptance
Test Driven
Development
Team
Work
Backlog
Estimation
Agile
Planning
Automated
UI Testing
Scrum/
Kanban

Never code alone
Pair Programming
Better Code, simpler design
Knowledge and skill distribution
Reduce risk of single code-
ownership
Raise discipline for writing clean
code
Teambuilding
Code Reviews
Is a vehicle of code quality
Clean Code is Teamwork

Coverage of entire functional test
pyramid from team perspective Exploratory Testing
System/UI Testing
Integrated / Component
Testing
Unit Testing
Effort & Test coverage
Testcosts&runtime
automatedmanual
Test Methods

Enable Cleanup for Sustainable Speed
refactoring refactoring
time
System
Behavior
System
Behavior
System
Behavior
Stable Stable

Continuous Integration

Our Learning – Key Aspects
Design to motivate frequent submit of small changes
Design for Speed
One code-line only
100% automated
should not run longer than 5 - 10min
Low entry barrier
fosters collaboration
State of the art tools
Lightweight
Allow to plugin team specific process
steps
Extensible
Team Specific Views, Thresholds, …
Customizable
Simple to get status of “my” change
Alarming in case of problems
Transparency
Team committed to
stop the line in case of problems
continuously improve to become better
and faster
Team Commitment

improve
experience
Agile
Process
sustainable
Accelerator
improve
experience
DevOps
collaboration
to gain speed
Foundation
the right things
and things right
improve
experience
Contiunuous
Delivery

From Continuous Integration to Continuous Delivery
Software
Engineer
ProductionHolistic End-2-End Delivery Process
Potentially shippable
Product increments any time

Why Continuous Integration might no be enough
Software
Engineer
Production
?
Where to execute long
running tests?
Typical example: security scans,
scenario testing, …
?
Where to run semi-automated
acceptance tests?
Specification Check, Documentation testing,
…
? Handover to
other teams?
?
Controlled Deployment into
Production
Deploy any change automatically might
not be possible…

Continuous Delivery Pipeline Stages – Setup Proposal
Software
Engineer
Production
Commit
Stage
Acceptance
Test Stage(s)
automated
Acceptance
StageAcceptance
Test Stage(s)
manual
is working technically
is working
functionally
is usable
is live!
Build
UnitTest
Component
Tests
Deploy
Regression
Tests
Security Scans
Code Checks
Load Test
….
Exploratory
Testing
Usability
Testing
Documentation
Testing
Scenario
Testing
Compliance
Checks
Final Go
Decision
Deployment
to production

Continuous Delivery Pipeline - to be considered
Software
Engineer
Production
Commit
Stage
Acceptance
Test Stage(s)
automated
Higher Quality
Acceptance Level
more
Production-like
 feedback-time
 manual interaction
 cost to fix
Acceptance
StageAcceptance
Test Stage(s)
manual

Our Learning – Key Aspects
Build once
principle
no more build after
commit stage
Transparency along the entire lifecycle
dashboards along the entire process
Engineer can access info at any time on click:
Where is my change? How does it work? How is it used?
Test Environment similar
to Production
Make test-environments similar
to production as fast as possible
core lifecycle processes like
“deploy” always identical
Acceptance Tests as
Contracts
close collaboration with
stakeholders on acceptance
criteria
Stop the line
principle
Don’t push into a
broken system
fixing over features
Automate the
Release Step
reliable, repeatable
procedure

What to use?
Software
Engineer
Production
Commit
Stage
Acceptance
Test Stage(s)
automated
Acceptance
StageAcceptance
Test Stage(s)
manual

Our Proposal for you
See Continuous Integration (CI) Best
Practices with SAP
Soon on
Ready-to-use Pipelines for
SAP Development Processes
S4H234 Introducing SAP S/4HANA Cloud SDK
S4H624
Build Applications with SAP S/4HANA
Cloud SDK on SAP Cloud Platform.
CPL144
Integrate SAP S/4 HANA with SAP Success
Factors Using SAP S/4HANA Cloud SDK
CPL144
SAP S/4HANA Extensions for Customers
and Partners with SAP Cloud Platform
CPL216
Best of Two Worlds: Continuous Integration
and Change Management
CPL275
Continuous Delivery for SAP Fiori Apps
on SAP Cloud Platform

improve
experience
Agile
Process
sustainable
Accelerator
improve
experience
DevOps
collaboration
to gain speed
Foundation
the right things
and things right
improve
experience
Contiunuous
Delivery

DEV OPS
What is the Problem?
DevOps: A culture where people,
regardless of title or background,
work together to imagine,
develop, deploy and operate a
system.
http://kenmugrage.com/post/my-new-definition-of-devops/
- Ken Mugrage, ThoughtWorks

“It need to change it fast.”
DEV
“I own the application.”
OPS
“I own the application runtime”
“I need to keep it stable”
Problem 1: Conflicting Goals?
Production
Conflicting Goal in the
Organization

“On my PC it’s working.”
DEV
“I own the application.”
OPS
“I own the application runtime”
“I can’t get it running without you!”
Problem 2: Tight Coupling between Application and Runtime?
Production
Throw over the wall behavior

Some Practices to fix it
DEV OPS
Collaborative Culture
assure close cooperation
between teams, roles, levels
respect for each other
Same Values
common goals
common values
common incentives
common success
Same Responsibility
life-site first for everyone
joint application
tracking/monitoring
Same Practices
agile operation
automation
infrastructure as code

• Ensure a solid foundation based on agile principles before introducing DevOps at large scale
• Build a Continuous Integration process that motivates developers to submit small changes
frequently
• Build a Continuous Delivery process that is transparent and provides feedback to the engineer
• Forster a collaborative culture between Dev and Ops
• It is never done - iterate to get better continuously, measure and learn!
• Consult Continuous Integration Best Practices with SAP for more information
Key Take-Aways

Demo
A short insight – how it is done at SAP

Access replays of
 Keynotes
 SAP TechEd live interviews
 Select lecture sessions
http://sapteched.com/online
Continue your SAP TechEd discussion after the
event within the SAP TechEd Community!
 Read and reply to blogposts
 Ask your questions
 Join conversations
sap.com/community
See all SAP TechEd Blogposts
SAP TechEd Online/Community

Further information
Related SAP TechEd sessions
CPL275 Continuous Delivery of an SAP Fiori Application to SAP Cloud Platform
CPL216 Best of Two Worlds: Continuous Integration and Change Management….
DX261 Continuous Integration: How This Can Be Realized for Apps with SAPUI5
DX709 Realizing Continuous Integration with SAPUI5 Designed Apps
S4H111 Change Control Management-Continuous delivery in agile and hybrid solutions
SAP Public Web
https://www.sap.com/developer/tutorials/ci-best-practices-intro.html
Watch SAP TechEd Online
www.sapteched.com/online

Thanks for attending this session.
Please complete your session
evaluation for CPL126.
Dirk Lüdtke
Dirk.Luedtke@sap.com
Christoph Szymanski
Christoph.Szymanski@sap.com
Feedback
Wolfram Kramer
Wolfram.Kramer@sap.com
Contact information:

SAP TechEd 2017 CPL216 - Continuous Delivery. An Introduction

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to SAP TechEd 2017 CPL216 - Continuous Delivery. An Introduction

Similar to SAP TechEd 2017 CPL216 - Continuous Delivery. An Introduction (20)

Recently uploaded

Recently uploaded (20)

SAP TechEd 2017 CPL216 - Continuous Delivery. An Introduction