Agile Implementation Methodology Introduction & High-Level Overview

Agile Implementation MethodologyIntroduction & High-Level Overview

Agenda • Introduction • What is Agile? • How does it work? • Agile Benefits • Agile Prerequisites

What do we do? FIELD SERVICES BUILD PLAN RUN CREATE & PROVE VALUE REDUCE TCI REDUCE TCO

Agile, offering the customer an alternative way to Rome ASAP ASAP Focus AGILE Show & Tell Look forValue Change is welcome Highlyinteractive Eliminate Waste

What is Agile? • The term Agile 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.

Run Final Preparation Go Live Support Project Preparation Overview of Agile Business Add-on to ASAP Blueprint Realization Sprint backlog / Revised / prioritized project backlog Determined project scope Prioritized delta list & release planning 2-to-4 wkscycle Work product increment Process-based composite application, business process, service or other functionality. Work product release

Hybrid Agile- ASAP 7 Acceleration Add-On Working Software 4 5 1 8 2 7 3 4 2 2 4 3 3 6 4 5 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 Priority Effort Release2 Business Priority Would Delta List Sprint Sprint Prep. Sprint Release 1 Could Define & Analyze Scope Demo SAP Standard IT Final Prep. Support Sprint Checkpoint Checkpoint Checkpoint Setting the scene Should Sprint Getting the organization ready Sprint Must Demo Evaluate Accelerators Time Project Prep. Evaluation & Release Planing Process WS & Sol.Archit. Baseline Build Sign-Off Go Live Demo Demo Demo Demo Demo Data Management RUN SAP Organisational ChangeMangement Enablement Realisation Release 2 Project Prep Realisation Release 1 Final Prep Go-Live Support Blue Print

Sprint 2-4 weeks Objective: Potentiallyshippable Software

Advantages at a glance Increased Flexibility More Transparency Faster Results • Working software is measure for progress • Regular Checkpoints (demos) to check requirements and results with business • Risks are quickly identified and better manageable • • Can respond to changes per ‘sprint’ • The customer discovers what he wants. Can take account of insight into the business. • After each iteration working software is delivered • Value: Customer gets what he wants. working software delivered based on value prioritized by customer

Agile Prerequisites • Prepare your Organization & align stakeholders • Understanding the rules of Agile (Change is normal, adapt, scope, speed, business driven projects) • Align stakeholders what to expect from Agile project approach (chances, risks) • Assign proper resources (quantitative & qualitative) to the project and have them 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 it’s 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 priorities • Know the To Be (not As-is) processes in scope • Know what you want to achieve and what brings value for your organization. Before starting with an Agile project……

Agile Mind Set- Customer’s Perspective Start with Standard SAP • From Functionality and Business Process Perspective • Set the right expectations to the organization Invest in training & Coaching- Mind Change • Train your process owners and implementation team in Agile & SAP functionality • Agile 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 expectations • Address Organizational Change Management & Communication timely Before starting with an Agile project……

Discussing Agile“There are different levels of Agility” • Conditions that Challenge Agile • 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) • Good Practices of Agile • Leverage pre-configured and Best Practice Processes as a baseline to add value in short iterations. • Integration of pre-configured content and value prototyping services • 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 • Acceleration techniques need to be tailored • to the customer’s situation, culture, and risk profile

Agile Implementation Methodology Introduction & High-Level Overview