| Handover to support |
Accessing SAP Fiori launchpad set up know-how |
| Universal application identification |
Clear identification of the applications in scope |
| Scope control |
Scope creep and impact on maintenance and support costs |
| Gathering requirements |
Content duplication, 1 to N mapping, and consistency |
| Recording test results |
Recording test results |
| Evaluating upgrade impact |
Evaluating upgrade impact |
| Adding new application to user |
Additional decisions on updating catalogs |
| Clarity of responsibility |
Diffused responsibility on the content that is shared |
| Naming conventions |
Consistent naming when different team members create and change content identifiers |
| SAP Fiori setup transparency |
SAP Fiori setup specification transparent for all project members. |
| Comparing blueprint with system setup |
Comparing blueprint with system setup |
| Transparency of app technology categories |
Insight into the app technology category to ensure the availability of a competent expert and plan technology improvements |
| Changes history |
Tracking the history of changes in the app |