How to select a software?

Software selection should follow a strict, compliant, and verifiable process.

The duration depends on the process, system, and geographical scope. You should not spend more than 6 weeks to 3 months on software selection.

The 4-step process for software selection looks like this:

1. Business requirements catalogue and longlist
2. RfI process and shorlist
3. RfP process, fit-gap analysis, and scenario modeling, including business case creation
4. Recommendation and decision

Followed by contract negotiation and signature.

What are best practices?

The business requirements catalog should contain

• Legal and regulatory requirements, e.g., E-Invoicing, DORA in terms of Financial Services,
• Requirements that are mapped differently in different software packages.

Banal requirements, such as it must be possible to create a customer, should not be considered.

The shortlist should not contain more than 4 providers.

The scenarios should not be modeled based on more than 6 criteria, namely coverage of the required functionality, extensibility, integrability, costs, risks, and usability.

The business case should include benefits.

How we can help

• Adhering to a strict, compliant, and verifiable process
• Providing a requirements catalog with requirements, legal and regulatory specifications, from which requirements are selected, but not defined from scratch
• Providing accelerators and templates, e.g., RfI and RfP documents, business case, and many more that need to be adapted, but not created from scratch
• Carrying out a fit-gap analysis
• Providing a benefits catalog from which the benefits are selected

Can you do this yourself?

Yes, but with us you will be faster, more effective, and more cost-effective.

Make it work, make it great, make it stick is the smart Swedish approach for business transformations reducing the risk that they fail

I learned about this successful approach during the 3 years I worked in Sweden, and apply it to all projects that we support.

𝗗𝗼 𝘆𝗼𝘂 𝘄𝗮𝗻𝘁 𝘁𝗼 𝗹𝗲𝗮𝗿𝗻 𝗺𝗼𝗿𝗲 𝗮𝗯𝗼𝘂𝘁 𝘁𝗵𝗶𝘀 𝘀𝗺𝗮𝗿𝘁 𝗦𝘄𝗲𝗱𝗶𝘀𝗵 𝗮𝗽𝗽𝗿𝗼𝗮𝗰𝗵 𝗳𝗼𝗿 𝗕𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗧𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻𝘀?

1️⃣   Make it work

✅ Reducing scope to the minimum that is required. You have great expectations when you start a program/ project. There is a business case, there are improvements that should have been done within the last years, but they have been postponed due to budget, time, resources or because of the business transformation ahead. Slice and dice it into digestible portions (releases). Realize the minimum with a first release.

✅ Working on the integrator relationship. You decided on an integrator. As in a marriage, the hard work comes after saying “yes”. You must communicate, discuss, come to joint decisions, sometimes compromises, and adjustments each day. This is applicable to all levels within the program/ project organization. You will be rewarded with a successful project as it is always the people who makes a project a success.

2️⃣   Make it great

✅ Reality checking business needs,
✅ Potentially adjusting the scope that did not went live with the first release.
✅ Realizing the outstanding scope with different releases.

3️⃣   Make it stick

✅ Making sure that

✅ The solution is used as it is supposed to be,
✅ Potential errors are solved in time,
✅ Training needs are analyzed, and delta trainings are performed on a regular basis,
✅ KPIs are monitored and reported on a regular basis
(e.g., guidelines and process adherence, data quality etc.)
✅ Data is maintained in a clean manner (no duplicates etc.), and
✅ Customizing of the solution is neither expanded exhaustively nor not documented properly.

𝗗𝗼 𝘆𝗼𝘂 𝗳𝗮𝗰𝗲 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝗰𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲𝘀? Explore how we can help you: www.norda-advisory.com.

#businesstransformation #sap #s4hana #transformation #makeitwork #makeitgreat #makeitstick

In dieser Folge von SAP Transformationsprojekte spricht Antje-Kathrin Schumann, unsere Geschäftsführerin, mit Seyde Sosnovski, Business Development Manager bei SAP, über das Thema SAP Learning Hub und darüber, wie SAP Unternehmen dabei unterstützt, ihre Trainingsziele zu erreichen.

Im Detail werden folgende Fragestellungen beleuchtet:

Wie hilft mir SAP Learning Hub meine Trainingsziele zu erreichen?

1. Weshalb ist #SAP Training wichtig?
2. Wie versetze ich meine Anwender in die Lage, erfolgreich mit einer Software zu arbeiten?
   1. Zu welchen Zeitpunkte(n) trainiere ich welche Nutzergruppen?
   2. Welche Nutzergruppen existieren im Unternehmen?
3. Wie etabliere ich eine selbstmotivierte Lernkultur im Unternehmen?
4. Wie unterstützt SAP Learning Hub Unternehmen im Rahmen von Transformationen?

Testen Sie SAP Learning Hub selbst mit einer 14tägigen kostenlosen Trial-Version: zum SAP Learning Hub

Stehen Sie vor denselben Herausforderungen? Kontaktieren Sie uns gern.

Jetzt anschauen!

How to move to SAP S/4 HANA in a smart way?

Nowadays the professional discourse revolves around “How to move to SAP S/4 HANA in a smart way?”, no longer about “Should we move?” and “When to move?”. The last two questions were absolutely justified a few years ago when SAP S/4 HANA was at its starting point and entire areas, processes or functions were missing. But these are no longer valid questions and certainly not with the current releases in 2022.

How to identify a smart way moving to SAP S/4 HANA? Which building blocks should be dealt with?

1️⃣ Which approach should be chosen: Greenfield, Brownfield, or SNP Group’s Bluefield™ approach?

2️⃣ How does the timeline look like?

3️⃣ What kind of and how many internal and external resources do we need?

4️⃣ How do we engage and enable our internal resources?

5️⃣ Which services do we source from which partner?

6️⃣ How do we ensure that all parties and people work collaboratively together?

7️⃣ What are the benefits that can be leveraged?

8️⃣ How does the benefits-cost case look like?

This post will focus on the different approaches, additional posts will focus on the other topics.

Which approach to choose when moving to SAP S/4 HANA?

Many of our articles compare transformation to building a new home. However, the choice is more akin to being overall very happy with your existing home, but it needs some upgrades, or you are considering building a new one to be custom-made for you.

When moving from SAP ERP to S/4 HANA there are three possibilities at hand:

1️⃣ Taking the greenfield approach in which effectively a new system is set up. The new system is designed, customized, and developed and data are migrated in from the pre-existing system(s). In this case, you have a whole new house to move into and set up as you see fit.

2️⃣ Or taking the brownfield approach which primarily consists of migration. The system is emptied of data, technically upgraded and the data are migrated in again. In this scenario, you move out of your home completely for a little bit, including all of your belongs, while renovation takes place, and then move back in with a similar arrangement. Even in cases where a brownfield approach is chosen, there are some topics where no migration path is available. This means for specific processes or new functionalities (e.g., business partner), a greenfield approach is needed.

3️⃣ Or taking the SNP bluefield™ approach combines elements of the green- and brownfield approaches. It is supported by SNP’s CrystalBridge®.

What are the advantages and disadvantages of the different approaches?

If you favor high security clearly a brown or Bluefield approach is the right choice as you don’t need a fallback solution. Your tried-and-true processes and functionalities are kept as they were. The changes can be performed worst case with workarounds for a reasonable timeframe. In the case of greenfield, there is no real fallback solution. It would mean rolling back to SAP ERP and then starting again as you need to move to S4 HANA. This is risky, potentially lengthens your time frame and has higher associated costs.

If you favor a high degree of standardization, clearly greenfield is the answer. By contrast, industry-specific processes may be covered with a lower degree of standardization in SNP bluefield™.

If you favor lower effort (regarding budget, resources, and timeline) brownfield is the answer; here again in the middle you will find SNP bluefield™ with somewhat higher effort than brownfield.

As you see SNP bluefield™ combines the best of both worlds, providing high security, medium standardization, and medium effort.

Do you face the same challenges? Find the best approach moving to SAP S/4 HANA with NORDA Advisory. Explore how we can help you: www.norda-advisory.com.

#businesstransformation #sap #s4hana #transformation