Discover how to achieve faster time to higher value with a template-based implementation approach. Learn how this new methodology uses SAP’s best practices to implement SAP Hybris solutions reliably and reach predictable and fast business go-lives. https://www.hybris.com/

1. PUBLIC
Sebastian Kress,SAP
October2017
Smart Adoption Methodology
for SAP Hybris

2. 2PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Overview and objectives
l SAP acts as a prime partner to selected customers in all industries
and for all products
l All expertise is on board – joint venture of customer, SAP, and partner
experience
l Customer and SAP define the scope/backlog, which is 100%
transparent at all times
l We deliver the scope in an agile development methodology
l Usable software is delivered after each sprint
l User acceptance after “show and tell,” aka demo sessions per sprint
l We reuse implementation project templates and repeatable custom
solutions
l Risk is low due to custom development fixed-price project
l We have reference customers in many industries

3. 3PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
The business model | Facts and figures
l Key success factor: sales, presales, aftersales, and delivery out of one hand
l Global reach and scale through SAP Digital Business Services, SAP Custom Development, and
selected partners
l Short project runtime: 3–12 months
l Lean and agile working model

4. 4PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Explain
1 day
Discover
3–6 weeks
Build
3–12 months
Adjust user stories during workshops
together with customer business
Create new user stories if needed
Remove nonrelevant user stories from
scope
Our methodology in 3 phases | Explain, discover, build
Agile project
methodology
Prime and fixed
price
Build demo systems
Repeatable
custom solution
Low risk,
fast time to value,
transparent cost and
delivery structure
Deliver sprints every 2 weeks
Achieve first go-live within 3 months
Hold “show and tell,” aka demo sessions and
user acceptance tests after each sprint
Implementation
projecttemplate
Contract1 Contract2

5. 5PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
• JIRA project template with ~1,400 predefined user
stories
• Every user story is assigned to
• Personas
• Business process
Phase 1 | Explain

6. 6PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Phase 1 | Explain

7. 7PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Phase 2 | Discover
l Set up customer project in JIRA
l Set up demo system
l Run discovery workshops with business and IT
l Adjust and enhance the user stories by screenshots from
demo systems
l Create missing user stories (check if these user stories are
relevant for project template)
l Get sign-off for every user story including acceptance
criteria by customer
l Track the progress of the workshops in JIRA
l Templates for every workshop in Confluence available
l Prioritize the product backlog
l Create sprint plans
Build demo systems

8. 8PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Phase 2 | Discovery template

9. 9PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Phase 2 | Discovery progress

10. 10PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Phase 3 | Build
§ Development sprint cycle of 2 weeks
§ Implemented and documented user story
§ “Show and tell” aka demo session after each sprint
§ User acceptance tests after each sprint by customer
§ Regression-free consolidation environment
§ Described manual test cases in Zephyr (JIRA add-on)
per user story
§ Automated test cases (Selenium) for delivered user
stories to help ensure quality of future delivery

11. 11PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Phase 3 | Build

12. 12PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
= Show and tell
= User acceptance test (UAT)
Exemplary project plan

13. 13PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Reporting | Predefined dashboards and reports
§ Sprint burndown charts
§ Sprint reports
§ Velocity chart
§ Release burndown
§ Version reports
§ Test execution reports
§ Test execution burndown chart
§ And more…

14. 14PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
User story tools and processes | JIRA
§ User story repository
§ Capture and organize requirements
§ Visibility of changes
§ Visibility on progress
§ Story shared with project stakeholders
§ Updates received by e-mail to stories
§ Technical tasks created for developers to deliver to
§ Work estimated by story
§ Development progress able to be seen

15. 15PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
User story tools and processes | Confluence
§ Co-operative working tool for content
§ Content shared with project stakeholders
§ Repository for project documentation
§ Ability to see published dates
§ Ability to see who has edited content
§ Pages able to be shared with smaller specific groups only (if needed)

16. Thank you.
Contact information:
Sebastian Kress
sebastian.kress@sap.com