Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • Risks in S4H Implementation PDF

    Uploaded by

    Aleksandar K
    40 views1 page
    Eight risks are identified for S/4HANA implementations: 1) extensive customization may prevent delivering on time/cost, 2) teams may revert to waterfall instead of Agile, 3) legacy integrations are difficult, 4) non-SAP tools may not integrate, 5) replicating process/data gaps increases cost/complexity, 6) incomplete testing allows defects, 7) focus on process may neglect controls/security, 8) Activate may omit reporting/BI despite HANA's tools.

    Original Description:

    Original Title

    Risks in S4H implementation.pdf

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    Eight risks are identified for S/4HANA implementations: 1) extensive customization may prevent delivering on time/cost, 2) teams may revert to waterfall instead of Agile, 3) legacy integrations are difficult, 4) non-SAP tools may not integrate, 5) replicating process/data gaps increases cost/complexity, 6) incomplete testing allows defects, 7) focus on process may neglect controls/security, 8) Activate may omit reporting/BI despite HANA's tools.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    40 views1 page

    Risks in S4H Implementation PDF

    Uploaded by

    Aleksandar K
    Eight risks are identified for S/4HANA implementations: 1) extensive customization may prevent delivering on time/cost, 2) teams may revert to waterfall instead of Agile, 3) legacy integrations are difficult, 4) non-SAP tools may not integrate, 5) replicating process/data gaps increases cost/complexity, 6) incomplete testing allows defects, 7) focus on process may neglect controls/security, 8) Activate may omit reporting/BI despite HANA's tools.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    of 1

    Eight specific risks for S/4HANA implementations

    Area Risk Solution


    The implicit assumption with S/4HANA is that clients will use Review areas which have high levels of
    It’s all in the
    1 box
    standard functionality, but if there are extensive areas where this is customisation or use SAP in an unusual
    not the case, the project won’t be delivered to time and cost. way.

    System integrators and existing SAP staff will have primarily used Assess current skills level and plans +
    Does everyone
    2 get Agile?
    ASAP or similar waterfall approaches. When faced with difficulties, STAGE GATES to monitor adoption of
    the risk is that they will revert to this approach, which takes longer. Activate.

    All SAP systems need to integrate with legacy applications and other Review of legacy application framework,
    SAP is an
    3 Island
    cloud based / industry specific systems. These integration points are assess dependencies, and challenge
    difficult to design, build, and test. overall roadmap.

    The assumptions are that you will use SAP tools such as Solution Review governance over tools and the
    Using SAP
    4 tools
    Manager, but these may need to work in parallel with your existing way in which non-SAP tools are
    tools, with risk of duplication or compromise. integrated with the standard SAP tools.

    Gaps in These gaps will be enshrined in your business-as-usual processes and, Use Data & Analytics to assess the impact
    5 existing without challenge, it is easy to replicate these as ‘essential of this gaps and how much this functions
    process / data requirements’ in HANA, causing addition cost and complexity. are used in legacy.

    Ensuring all An agile approach can make it more difficult to obtain an end-to-end Specific deep dive on testing – to assess
    6 requirements view of requirements and potential customer/process journeys, with requirements traceability, test approach,
    are tested the consequence that testing is incomplete and defects not captured. and minimum viable product.

    Controls, In an agile process it is easy to focus on the process and not have
    Specific deep dive on Security and
    7 security and enough time to design the related controls. Controls will change with
    Controls.
    compliance HANA and it is easy to miss opportunities to improve and automate.

    The Activate methodology does not have a specific step for


    Business Specific deep dive on Data & Analytics
    8 Intelligence
    reporting/BI so it is easy to omit. Although HANA provides powerful
    supported by our Empower technology.
    reporting tools these only work if supported by processes and data.

    You might also like