Vous êtes sur la page 1sur 12

5 REASONS WHY YOU NEED

AN AGILE DELIVERY MODEL FOR SAP

basistechnologies.com Whitepaper
Business Impact

The developing digital economy is driving a big change in the way


applications and infrastructure are provisioned and delivered.

But what if youre running applications like SAP and the digital
transformation doesnt have a direct impact on you, at least not right now?

Perhaps youre focused on trying to improve operational efficiency and


implement process improvements, and you want to be able to deliver them
with the minimum of disruption.

In that case you might be wondering why methodologies like Agile, Lean,
DevOps and Continuous Delivery have any relevance - you already have
robust processes in place to deliver applications in a traditional way, after all.

The answer is the early delivery of business value.

basistechnologies.com
Traditional
Development IN LARGE RELEASES

The business waits a long time to get



new features, so people get frustrated

Theres nothing inherently wrong with delivering applications


in a waterfall fashion, where theyre pre-planned, budgeted Its
 difficult to change direction or
and have a well defined scope, but working this way doesnt refine what was asked for;
mean that risk is removed.

A more agile approach to managing application change allows There are high levels of business

requirements to be delivered to the business in shorter, more impact and testing;
frequent releases.

So whats so good about that and why should you do it? Recovery
 from failure is difficult and
time consuming due to the volume
of changes deployed all at once - so
theres less time to build new features.

basistechnologies.com
Designed to inhibit change

In traditional development requirements are Day-one obsolescence and the spectre of feature
documented up-front based on what people think creep can hang over long-running projects. More
they want at that time. When the project gets and more requirements are discovered during
delivered - often many months later - stakeholders design, build and test, becoming increasingly hard to
realise that things dont work as they expected or, accommodate.
even worse, its taken so long to deliver that theyre no
longer relevant.

basistechnologies.com
Agile Development WHY AGILE?

1. Fail fast and respond


Delivering requirements at speed enables fast feedback
loops for constant improvement.
2. Smaller chunks reduce risk and impact
Splitting releases into smaller batches allows the simpler
Agile accelerates business value delivery, and and faster delivery of critical features.
through a process of continuous planning and 3. Avoid temporary workarounds
feedback, ensures that value continues to be Taking a lean approach to delivery ensures that solutions
maximized throughout the development process. are more efficient and cost effective.
4. Visibility, Control & Measurement
Involving all stakeholders on a day-to-day basis creates
better visibility and ensures that priorities are constantly
managed.
5. Fast recovery
The risk and uncertainty that surrounds massive deploy-
ments is almost eliminated, freeing more time to spend
building new features and creating business value.

basistechnologies.com
1. Fail fast and respond

One of the key benefits of an Agile approach is that Agile development permits the business to
requirements are delivered faster so the business can experience this delivery failure and learn from it so
benefit from them far sooner. And, even if they dont that less time is wasted building things that no one
quite work right, fast feedback loops enable constant wants. It allows testing of whats been built to ensure
improvement. that it meets business needs - in the old world
nothing would have been seen until the end of a long
project many months later, with little or no opportunity
to make changes.

basistechnologies.com
2. Smaller chunks reduce risk and impact

With big releases come big risks and impact. Deploy- It makes testing and user adoption far simpler and
ing hundreds or thousands of changes at once might allows immediate deployment of distinct changes as
seem like a better way of doing things but its hugely soon as theyre ready to go.
risky and theres a large business impact (adopting
and learning many new features and processes at the Some analysis of existing business processes is
same time requires considerable effort). required in order to fully understand the impact of
more frequent deployment, but an Agile approach
Breaking down releases into smaller, more man- means that changes can be accepted into produc-
ageable chunks takes away a large element of risk. tion much faster.

basistechnologies.com
3. Avoid temporary workarounds

When the pace of change is slow, people natural- ded into processes, creating large levels of technical
ly attempt to build creative solutions that can work debt and a high cost to maintain and run.
around bottlenecks and be delivered more quickly.
Agile development avoids these workarounds be-
Unfortunately, most of these temporary cause the delivery pipeline moves faster. Not only
workarounds dont operate in an optimal way. Its all are solutions more efficient, but theyll be easier and
too easy for them to become permanently embed- cheaper to run in the long term as well.

basistechnologies.com
4. Visibility, control and measurement

In traditional development the testing is largely done and prioritized product backlog and in each iteration
in one big lump at the end. That means its almost its easy to see whats been done, what needs to be
impossible to know the current status of anything or done and what the risks and blockers are.
to anticipate and manage issues as they arise.
As users are actively involved they can steer
Agile processes promote transparency through the development at every step of the way. And if
involvement of all stakeholders on a day-to-day basis. requirements change its much easier for the team to
Business requirements live in a constantly updated shift attention to higher priorities.

basistechnologies.com
5. Fast recovery

So what do you do when something goes wrong issues and provide the necessary resolutions.
after the deployment of a project? Its really hard to
measure and recover from failure when changing The risk and uncertainty that surrounds massive
many things in each release. deployments is almost eliminated, freeing more time
to spend building new features and creating business
The smaller deployments that come with Agile value.
processes make it far easier and faster to unpick any

basistechnologies.com
An efficient IT delivery
model

The methodologies introduced earlier - DevOps, Lean, Agile


and Continuous Delivery - are an ideal way to approach major
programmes of change such as a digital transformation project.
However, they also support a much more efficient IT delivery model
thats designed to give the business exactly what it needs, when it
needs it, regardless of the bigger picture.

When applied to SAP this can transform what is all too often a slow
and inflexible way of delivering business value.

basistechnologies.com
For more information
on how to run Agile
development for SAP
please download
this eBook

In the digital economy, agility is fundamental. We focus on continuous


delivery helping our customers align IT closer to the business.
At Basis Technologies we create automation tools that allow
companies to deliver enterprise application changes at the speed of
business.
By harnessing the agility of our DevOps suite, thousands of IT
professionals worldwide are able to deliver high-quality SAP releases at
pace capitalizing on their current infrastructure and remaining relevant
to future business strategy. The results produce faster time-to-market,
longer production uptime, and lower operational costs.

basistechnologies.com

Email info@basistechnologies.com UK Germany Canada USA Basis Technologies International


Ltd., 2015. All rights reserved.

Follow +44 20 7958 9025 +49 30 300 11 4606 +1 703 476 4565 +1 703 476 4565