Untitled

ONE AH GROUP: RS AND BPDD
DOCUMENTATIONS AND QGS
22.03.2023
RS and BPDD documentations and QGs

AGENDA:
01 QGs
02 BPDD Documentation
03 RS Documentation
04 Baseline Documentation
QUALITY GATES
01
oneAHgroup Project & Order Phases with Defined Milestones
Program/Project Management & Methodology with Quality-Gate Transparency
= Quality Gates to assure phase output quality
BP Iteration 1
Tests passed
5.Go-Live Prep.
SIT, UAT & Migr.
ü Do
G o
(ü) = Order phase states reached by passing phase quality gate

Integration Test done
User Acceptance Test done
ü
= Integrated order processing by agile sprints per order phase
(Integration assured by Enterprise Architecture & Cross Integration) Best-Practice 4. Deploy oD  Tests fully executed
Processes
(Tests/Defects) D  Bugs fully fixed
= Phase & Stream Sprint Planning Lead  Retesting successful
 Go-Live approval by GPO
AH (GPE/GPO) Definition of Done
3. Realize
ü I
Consultant/Developer Gap Concept &  Training Dok created
Specification (RS)
(Implementation Do  Tester trained
 Tests fully executed
)  Bugs fully fixed
 Retesting successful
ü
Identified Gaps
2. Explore R  Order release by GPE
Do
in Onboarding Definition of Implemented
 Order is implemented
(Conception) complete, correct & compliant
 Unit Test successfully done QG Legend:
ü
 Knowhow Transfer to GPE & SAP-CC
1. Prepare E DoR = Definition of Ready for Impl. = Quality-Gates
Do
done and GPE confirms understanding
 Concept & tests for order are
(Requirements) complete, correct & stable
 Released for order testing DoE = Definition of Explore
by Implementer, GPE, SAP-CC Resp. (Requirements released)
 Effort/Cost Estimation done
 Sorting for realization done by GPO DoR = Definition of Ready for Impl.
DoE = Definition of Explore (Conception released)
 Requirements definition is  Released for implementation work
by GPE, SAP-CC Responsible & PL DoI = Definition of Implemented
complete, correct & stable (Implementation released)
 Released for concept work DoD = Definition of Done
& benefit by GPO & GPE (Implementation released)
5 oneAHgroup | Project Organization DoGO = Definition of Go-Live
(Busines use released)
DOE
 Describe the benefit for that

Gap/BP
 Approval by GPO through a
mail or in the respective OIM
entry
 If the approval is done by OIM,
put Gernot and Michael Zier as
viewers
6
ARGO-HYTOS RS and BPDD documentations and QGs
TIMESLOTS FOR QGS DOR
 Gernot reserves a timeslot each

Monday between 13 and 16 hs
 First come, first serve
7
UNIT TESTS IN WHICH PHASE
 Unit Tests are conducted in the DoI phase

 The function is tested
 If a gap is specifically developed for a country, it needs
to be tested for that company code
 For other company codes a sample check could be
done
 For BPs and Gaps all company codes need to bested in
the DoD phase
 MPM Training documents are created for BP in the DoD
phase and should be incrementally extended by the
gaps for that BP.
8
BPDD DOCUMENTATION
02
OIM/NOMENCLATURE
 All existing BP entries of the BP list have been transferred to OIM with the old
nomenclature
 New BP have the nomenclature BPNXX with a consecutive number
 New BPs and their estimations just need to be maintained in OIM, not in the BP list
 The related documentation is within the existing folder structure on the sharedrive
10
WORKING DOCUMENTS / RELATED FOLDERS
11
FLOW CHARTS AND RELATED GAPS
 A BPDD document contains two flow charts
 The plain BP flow chart
 The BP flow chart containing the gaps, marked in red
12
ADJUST FLOW CHARTS WITHOUT SIGNAVIO
•Search for BP-Content (rapid.sap.com) – the example

contains Best-Practice BD9
•Download flowchart BPMN2 (in the example)
•Extract and unpack ZIP File
13
•Either double click on ZIP file and move the filesto your
desktop
•Right Click of the mouse on ZIP folder and extract

everything
14
•Open webpage BPMN.IO and click „Try Online“
15
•Click open and choose extracted ZIP file
16
•BPNN is shown, could be adjusted and saved
17
CHAPTERS
 Yellow marked chapters need to be

described
 Other chapters are either optional or
irrelevant
18
GAPS FOR THE BPS
 Gaps of the BP are listed in chapter 5

 Each gap needs an OIM entry
 Gaps without development could be described in chapter 5. This
description is used for the QG DoR. No further RS specification is
necessary.
 Other gaps containing developments need to be described in the RS
documentation
19
MPM DOCUMENTATION
You find the template for the MPD document

at:
https://argohytosgroup.sharepoint.com/sites/
oneAHgroup-ProjectPlanningRepository/Shared
%20Documents/General/1_ERP_Project/
30_ERP_Training/70_Training%20Documents/
30_SALES_Order-Mgmt/Template%20-%20MPM
%20Master%20Process%20Training-Manual.docx
20
RS DOCUMENTATION
03
OIM/NOMENCLATURE/ESTIMATIONS
 All existing WRICEF entries of the WRICEF list have been transferred to OIM with the old nomenclature
 New Gaps are just maintained within OIM and have the nomenclature:
 The related documentation is within the existing folder structure on the sharedrive
 Gaps with developments are described within the RS documentations
 Gaps without development could be described within chapter 5 of the respective BP
 The estimation of each gap need to be maintained within OIM
 If the gap contains a development the estimation need to be mentioned in the RS documentation as well
22
WORKING DOCUMENTS / RELATED FOLDERS
23
CHAPTERS
 Yellow marked fields need to be described

 Others are either optional or you need to
declare them as irrelevant
24
BASELINE
DOCUMENTATION
04
BASELINE DOCUMENTATION FOLDERS
26
CHAPTERS
27
BASELINE DOCUMENTATION AND QG
 Chapter 5.1. contains the description of a localization package and necessary OSS notes
 All Gaps for a country could be described in the baseline documentation
 For each gap an OIM entry needs to be created
 The baseline documentation need to be approved in the QGs
 Phoron products (Brazil) are described in the baseline documentation. An OIM entry
needs to be created for each product
 E-invoicing is described in the baseline documentation. One or more OIM entries need to
be created
 Exceptions are gaps, which contain developments (create a separate RS document)
28
THANK YOU FOR YOUR ATTENTION. IF YOU
HAVE QUESTIONS, JUST ASK

Untitled

Uploaded by

Copyright:

Available Formats

Untitled

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Untitled

Uploaded by

Copyright:

Available Formats

ONE AH GROUP: RS AND BPDD

DOCUMENTATIONS AND QGS

RS and BPDD documentations and QGs

(ü) = Order phase states reached by passing phase quality gate

 Describe the benefit for that

 Gernot reserves a timeslot each

 Unit Tests are conducted in the DoI phase

•Search for BP-Content (rapid.sap.com) – the example

•Extract and unpack ZIP File

•Right Click of the mouse on ZIP folder and extract

•Open webpage BPMN.IO and click „Try Online“

•Click open and choose extracted ZIP file

•BPNN is shown, could be adjusted and saved

 Yellow marked chapters need to be

 Gaps of the BP are listed in chapter 5

You find the template for the MPD document

 Yellow marked fields need to be described

You might also like