SAP Leonardo Project – All you need to know!
SAP Leonardo is a combination of industry and business process knowledge together with expertise in new technologies like IoT, Machine learning, Big data, Blockchain etc. The user design-led innovation approach helps customers in the digital transformation of the business. This blog focuses different aspects of SAP Leonardo project.
Roles and responsibilities
CDEL (Customer Design Engagement Lead)
- Business, technology, and design thinking
- First POC for customer team
- Engaged in throughout the project. Lead the technical team. Present the prototype, POC to customers
- Key points to successfully perform the role is put yourself in their shoes, identify the business challenges, ensure that we are delivering the value to the customer
- Technical delivery track and UX delivery track running in parallel help to get a good outcome for the customer
- Responsible for user research findings, design mockups, communicate the design to the development team
- They have to perform different roles like UX, UI designer
- Lead the development team and make sure the requirements from the customer are developed and deliver
- Involved in the project from start to end but major role in discover, design/prototype and deliver
- Deliverables are the prototype of the scope
- Closely work with the customer from Discover to Deliver phase of the project
Project managers from IT
- Continuously works with customer and design team to make sure the project is delivered on time and with right expectations
Business sponsor – To make sure that there is executive buying for the project
End users – To get the information regarding pain areas in the business process
The project is divided into four phases – Explore, Discover, Design and Prototype, Deliver
- Identify most important use cases and target end users to get the information
- SAP experts give the information regarding Leonardo technologies like IoT, Big Data, Machine learning, Analytics etc
- Ask the customer about business challenges, pain points in the business
- The color code is important
- Yellow – Pain points
- Green – Wishes/Ideas/Inspiration
- Blue – Market threat and Barriers they are facing
- Pink – Title for group
- Ask the customer to vote the most important cluster. This will reduce the time required for discussion
- Ask the customer to put the cluster on Value heat map to get the most valued cluster. This gives us the scope, time required for deployment, stakeholders and end users to be interviewed
- Develop the game plan –
- What are the challenges of the game plan?
- What the success look like?
- What key objectives and deliverable do we need in the project?
- What is out of scope for this project?
- List down the action items and team involved
- User research – Identify the pain points, analyze findings and start finding the solution
- Understand the user issues, the technology they use, activity and the data they use
- Discuss your findings and validate the research with the end user. This is the stage where you can bring project sponsors and connect them to the people who are benefited from the project
- Point of view statement and brainstorm new users – This will give them an idea of what technology they are going to use, what data they may need to change and show them low fidelity prototype
- Golden thread – A storyboard that connects the problem, possible solution and benefits of the solution that helps people that may not have deep knowledge of project and software
Design and Prototype
- High fidelity prototype
- Duration could be 2-6 weeks depending on the scope of a project
- SAP Build –
- Workspace – In this section, we create the prototype
- Create project
- Create study – Add questions and send it to users for review. Based on the feedback we can get an idea about the reaction from the user against the prototype
- Learning – Learn about tool and design thinking
- Gallery – Prototypes that you can use and start from there
- Services – Section where you can get help for your prototype
- Blog – Information regarding releases
- Workspace – In this section, we create the prototype
- SAP FIORI –
- SAP FIORI simplifies the most complex applications and shows the most relevant information to the user based on user role
- SAP FIORI allows you to work from anywhere regardless of any type of device that you use. Whether it is a laptop, tablet or cell phone
- Design gates (D-Gate) – Think from an end-user point of view. What they expect is highest design quality. Design gates are conducted by UX expert group from Global SAP team. Experts will make sure that the FIORI design is made with the highest quality and with an optimized procedure.
Let’s take a look at three different design gates
D-Gate 0 – In SAP BUILD you need three main artifacts Persona, Low-fidelity prototype, and Golden thread. You can add more documents like Heatmap, Stakeholder map etc. Make sure to add required documents before submitting the project for review. After the review meeting reviewer updates the decision.
D-Gate 1 – AT this stage you need to have High fidelity mockups and submit the project for review. After the review meeting reviewer updates the decision. Reviewer sends the notification to project team members. The notification includes The result, Reviewer’s note, Link to build project and reviewer name
D-Gate 2 – After passing D-Gate 1, you can start implementation. Once the development is done then you can request D-Gate 2. Artifacts required here is Link to the application and necessary access data
- People involved in this phase – CDEL, Development lead, Front end/Back end developers, Development architect and UX Developer
- This phase is to build the proof of concept and assess what it would take to have a scalable solution in client landscape
- UX developer needs to make sure the design guidelines have been followed and also optimal user experience while balancing the technical feasibility
- SAP UI5 HTML Library – Good place to check which high fidelity prototype is FIORI compliant
- CDEL (Customer Design Engagement Lead) will need to make final solution and proposal beyond POC with stakeholders and business users. Show the new solution proposition and explain how it is a valuable addition to the business