Description
Chapter 1 - What is SAP S4HANA SolutioningEstimating/Budgeting and monitoring SAP S4HANA Projects. It expands on why traditional estimation models (like function point analysis in programming) does not apply to SAP S4HANA projects. It informs the reader about SAP S4HANA Solutioning framework and its uses whether its implementation/support or even small-time enhancements.
Chapter 2 - Solutioning Components Starts with Process/Functional effort. Then takes it forward with Development, Data, Testing and Project Management. It delves also into, why clients should not ignore the Organization Change Management/Training area. It also touches upon the Technical Architecture/ Infrastructure area.
Chapter 3 - Process/Functional Effort in SAP S4HANAIntroduces the reader to Factor-based estimations. What drives functional effort - module scope/process hierarchy, number of configurations. How do you solution for functional design effort? It also expands on the other areas where functional teams get involved - data conversion, testing, even delivery of the training. How to estimate for the effort where often functional teams get pulled into?
Chapter 4 - Development Effort in SAP S4HANA It is a most industrialized method such as using RICEF list to drive this effort. Why should you not ignore efforts such as transport management, defect fixes or even in data migration done by Development teams or hyper care support?
Chapter 5 - Data Effort in SAP S4HANAData is often biggest (and poorly solutioned) components of SAP S4HANA projects. It talks about data quality/profiling and why you should not ignore data cleansing effort. Why manual data loading effort often gets under-staffed/under solutioned? What factors drive data conversion solutions - the number of data conversion objects/cycles/mock conversions? Why should you have separate RACI for data, to properly allocate effort across streams as data is often parallel stream in the project?
Chapter 6 - Testing Effort in SAP S4HANATesting is often outsourced/industrialized area of SAP S4HANA Projects. But it's also most stressful activity due to poor solutioning. The client often underestimates their commitment to it. How a test scripts/test cycles drive the testing solution? How to accurately solution for system integration testing? Why client often underestimate on legacy integration testing? Why and how infrastructure/landscape manage effort should be considered during test cycles?
Chapter 7 -Tech Arch/Infrastructure EffortWhy small items like setting up the printers/desktop configurations need to be considered upfront? With cloud/HEC scenarios prevalent in SAP S4HANA Projects, why a client should be clear on RACI with multiple partners operating in this area. What factors drive the solutions in this area?
Chapter 8 - Organization Change Management (OCM)Why is OCM often seen just as training activity? It also includes - communications management, stakeholder analysis, job/role design. What factors drive this effort and why SAP S4HANA clients often underestimate for this effort?
Chapter 9 - Miscellaneous Factors Terms such as governance, cutover, deployments - why it's important to estimate/allocate effort to these buckets upfront?
Chapter 10 - How it All Comes Together?How to combine all the above data points for solutioning purpose? How it affects client/vendor resources and ultimately price paid by the client for SAP S4HANA Implementation?
Chapter 11 - Evolution of SAP S4HANA Solutioning approachesWould your solution separately for SaaS projects such as Concur/SuccessFactors or HEC Implementation? How has Fiori/S
Author: Sanket Kulkarni
Publisher: Apress
Published: 09/30/2019
Pages: 228
Binding Type: Paperback
Weight: 0.78lbs
Size: 9.21h x 6.14w x 0.53d
ISBN13: 9781484245194
ISBN10: 1484245199
BISAC Categories:
- Computers | Data Science | General
- Computers | Software Development & Engineering | General
- Business & Economics | Management Science
Chapter 2 - Solutioning Components Starts with Process/Functional effort. Then takes it forward with Development, Data, Testing and Project Management. It delves also into, why clients should not ignore the Organization Change Management/Training area. It also touches upon the Technical Architecture/ Infrastructure area.
Chapter 3 - Process/Functional Effort in SAP S4HANAIntroduces the reader to Factor-based estimations. What drives functional effort - module scope/process hierarchy, number of configurations. How do you solution for functional design effort? It also expands on the other areas where functional teams get involved - data conversion, testing, even delivery of the training. How to estimate for the effort where often functional teams get pulled into?
Chapter 4 - Development Effort in SAP S4HANA It is a most industrialized method such as using RICEF list to drive this effort. Why should you not ignore efforts such as transport management, defect fixes or even in data migration done by Development teams or hyper care support?
Chapter 5 - Data Effort in SAP S4HANAData is often biggest (and poorly solutioned) components of SAP S4HANA projects. It talks about data quality/profiling and why you should not ignore data cleansing effort. Why manual data loading effort often gets under-staffed/under solutioned? What factors drive data conversion solutions - the number of data conversion objects/cycles/mock conversions? Why should you have separate RACI for data, to properly allocate effort across streams as data is often parallel stream in the project?
Chapter 6 - Testing Effort in SAP S4HANATesting is often outsourced/industrialized area of SAP S4HANA Projects. But it's also most stressful activity due to poor solutioning. The client often underestimates their commitment to it. How a test scripts/test cycles drive the testing solution? How to accurately solution for system integration testing? Why client often underestimate on legacy integration testing? Why and how infrastructure/landscape manage effort should be considered during test cycles?
Chapter 7 -Tech Arch/Infrastructure EffortWhy small items like setting up the printers/desktop configurations need to be considered upfront? With cloud/HEC scenarios prevalent in SAP S4HANA Projects, why a client should be clear on RACI with multiple partners operating in this area. What factors drive the solutions in this area?
Chapter 8 - Organization Change Management (OCM)Why is OCM often seen just as training activity? It also includes - communications management, stakeholder analysis, job/role design. What factors drive this effort and why SAP S4HANA clients often underestimate for this effort?
Chapter 9 - Miscellaneous Factors Terms such as governance, cutover, deployments - why it's important to estimate/allocate effort to these buckets upfront?
Chapter 10 - How it All Comes Together?How to combine all the above data points for solutioning purpose? How it affects client/vendor resources and ultimately price paid by the client for SAP S4HANA Implementation?
Chapter 11 - Evolution of SAP S4HANA Solutioning approachesWould your solution separately for SaaS projects such as Concur/SuccessFactors or HEC Implementation? How has Fiori/S
Author: Sanket Kulkarni
Publisher: Apress
Published: 09/30/2019
Pages: 228
Binding Type: Paperback
Weight: 0.78lbs
Size: 9.21h x 6.14w x 0.53d
ISBN13: 9781484245194
ISBN10: 1484245199
BISAC Categories:
- Computers | Data Science | General
- Computers | Software Development & Engineering | General
- Business & Economics | Management Science
About the Author
Sanket has more than 18 years of experience in implementing SAP solutions worldwide. He has consulted with many customers on complex SAP transformations involving multi-year rollouts. He has worked across a range of industries such as consumer goods, oil and gas, semiconductor, and transportation. Over the last few years, he has been coaching customers undergoing SAP S/4HANA-driven digital transformations.