Applicability

This model is applicable for Agile based bespoke development/enhancement projects.

Non Applicability
This model is not applicable for estimating Epic/ feature level when sufficient implementation details are not availa
Mode of Use
This model should be used by Product Owners ,Scrum Masters and SMEs from different portfolios who has the tho
Assumptions
Analysis of the requirements, breaking them down into user stories, and prioritisation of stories into sprints are do

Version History
Version No. Date Description

M&S Agile Estimation Model V1.0 Jan-2018 Initial Draft

M&S Agile Estimation Model V1.1 May-2018 Cost and Benefit Calculations added

M&S Agile Estimation Model V2.0
M&S Agile Estimation Model V2.4
M&S Agile Estimation Model V3.0
M&S Agile Estimation Model V3.1
Aug-2018 Formatted the fields in the cost & savings sheets
Nov-2018
Provided options to distribute the total efforts across resources
and across location
Jun-2019 Rebase lined Technology factors and added new Technologies.
Updated the Capacity Based Cost and Savings calculation sheet
Nov-2019 Added Power BI and Service Design

M&S Agile Estimation Model V4.0 Mar-2020 Updated with 20/21 rate tables
 nt/enhancement projects.

el when sufficient implementation details are not available.

ers and SMEs from different portfolios who has the thorough understanding of the story implementation details

stories, and prioritisation of stories into sprints are done before the start of estimating their size using this model.

History
Description

ft

enefit Calculations added

the fields in the cost & savings sheets

ptions to distribute the total efforts across resources
location
ed Technology factors and added new Technologies.
he Capacity Based Cost and Savings calculation sheet
wer BI and Service Design

with 20/21 rate tables

l.
 Demand (PIC) Estimation Summary
Project Name SAPTP-4058 -CnH Brand Vendor Consignment Process
Version 0.4
Date 9/11/2020

Story Point Summary

Required Engineering Effort 303
Actual Engineering Effort 230
%Effort Savings 24%
OFL 83%
Cost Before Savings £74,895
Cost after Savings £44,735
% Cost Savings 40%

Additional Costs:
Release Management Cost £3,621
TDCS Cost £5,500
Total SAP Cost After Savings £53,856

Includes
SAP Dev, SAP ST, SAP PT, OAT, SAP NPEMS and Release Costs

Excludes
SIT [Non-SAP], Non-SAP PT, Non-SAP NPEMS

Version 4.0
3/4/2020
TDCS Cost
Level Resources PD's Value Comments
D Core Services System Specialist 10 £ 5,500.00 Design Assurance

0 £ -
0 £ 5,500.00

Estimator 4.0 to be inserted as an object

Title SAPTP-4058 -CnH Brand Vendor Consignment Process
Version 0.4
Date 9/11/2020

Scope - SAP Development

S.No Application/Interface/NFR/Testing

1 SAP ECC

2 SAP ECC

3 SAP ECC

4 SAP ECC

5 SAP ECC

6 SAP ECC

7 SAP ECC

8 SAP ECC

9 SAP ECC

10 SAP ECC

11 SAP ECC

12 SAP ECC

13 SAP ECC

14 SAP ECC
 Scope - SAP ST
S. No Application/Interface/NFR/Testing
1 SAP ECC - I0011, I0012, I0016
2 SAP ECC - I0077
3 SAP ECC - Manual PO, I1001, I1003, I0808/I0181
4 SAP ECC - I0185, I0807, I1001, I1003, I0808, I0809, I0812
5 SAP ECC - POS Sales I0060
6 SAP ECC - ecom process I058, I0586
7 SAP ECC - regression of Stock hub JDA and EDW interface

8 SAP ECC - regression of GMOR/BW

9 SAP ECC - Vendor Settlement

10 SAP ECC - Adjustment
11 SAP ECC - RTW

12 SAP ECC - Regression

Scope - SAP PT
S. No Application/Interface/NFR/Testing
1 I0011 Article Master
2 I0807 Dispatch
3 I0809 Adjustment
4 I0586 Dispatch
5 I060 Sales Interface
6 Vendor Settlement
7 Rxxx ECC Report
8 1 GMOR report
9 1 Stock Hub Model

Scope - SAP OAT

S. No Application/Interface/NFR/Testing
1 2 New CONTROL M Jobs
Scope - SAP Development
Scope
1. Setup Consignment Article Setup Process -
New article type config, Merchandise category, I0011/I0012 modification to create consignment info record, UPC
auto generation and additional attributes

2. Setup Consignment related configuration, material master migration (LSMW), New GL and account determiantion

3. Procurement flow
- Manual PO creation using ZP1 PO type, rest of the process will follow BAU with an exception that no invoice
possible for consignment PO

4. Stock Transfer from DC to Store:

- JDA will generate replan order and interface to SAP, as similar to M&S product, rest of the process will fallow BAU
- Change is required in Goods issue process (I0807) to issue consignment stock, intead of unrestricted stock based on
article type- its a change

5. POS Sales:
- Change is required in sales process (I0060) to issue consignment stock, intead of unrestricted stock based on article
type- its a change
6. Ecom Sales:
- Change is required in sales process (I0586) to issue consignment stock, intead of unrestricted stock based on article
type- its a change
7. Vendor Settelment:
- setup standard consignment settlement - using credit memo
- New smartform with itemwise sales data

8. Adjustment:
- Change is required in DC adjustment (I0809) to adjust consignment stock, intead of unrestricted stock based on
article type- its a change
- This will only reduce the stock, but no accounting adjustment
- All financial/settlement process related to this to be manually managed
- Return Center process are out-of scope

9. Return (RTW):
- As is business process to be used, no change is planned in Q3
10. Vendor Return (RTM):
- No change is planned in Q3, it has to follow manual process

11. Reporting Impact:

- No new reports planned in Q3
- However Stockhub and GMOR systems to be analysed for impact to BAU process and change to mitigate impact

12. GRC
- Access to ME21N, MASS_MEAN
13. Finance:
- New GL
- Common field in assignment for account clearinig (during Issue and vendor settlement)
- account clearing process

Out of Scope for Q3:

'-. New PO type for consignment , configuration related to stock determination ( Not in Q3 scope, may be for Q4, for
now manual)
-. Change in Contract I0077 to create consignmewnt info record and price update
-. Change in I0083/I2696 PO to create consignment PO ( Not in Q3 scope, may be for Q4, for now manual)
-. EDW discussion with reporting change (** No Chnage in EDW, Out-of scope for Q3)
-. Ability of DC and Store to write-off stock for Damage and lost. Financial liability with vendor and credit memo
process to be defined ( Not in Q3 scope, may be for Q4, for now manual)
-, RTM and RTW ( Not in Q3 scope, may be for Q4, for now manual)
Scope - SAP ST
Scope
Test brand article creation/update from range planner and consignment infor record.
Test Brand vendor contract and consignment info record creation/update
Consignment PO creation process, No Invoice.
Consignment stock STO transfer from DC to store like any regular product.
POS sales accounting verification and Vendor settlement, including return.
E-COM sales accounting verification and Vendor settlement, including return.
Provision for stock hub metrics and interface testing for Consignment PO.
Provision for GMOR and BW chnages related to Consignment PO and Consignment Stock and
Consignment Sales.
Vendor Settlement process and Smartform and intrerface to vendor.
Test I0809 and I0149 adjustment process.
test RTW (reverse logistics).
Consider interface for regression - I0111 and all interfaced changes (listed above).
I0185, I0807, I1001, I1003, I0808, I0809, I0812.

Scope - SAP PT
Scope
SAP ECC
SAP ECC
SAP ECC
SAP ECC
SAP ECC
SAP ECC
SAP ECC
GMOR
HANA

Scope - SAP OAT

Scope
SAP ECC
Title
Version
Date

S.No
1

3
4
5
6
7
8

10
11

12
13
14
15

16
17
18
19
20
21
22
23
24
25
26

27

28
29
30
31
32
33
 34
35
36
37
38

39
40
41

S.No
1
2
3

4
5
6
7
8

S. No
1
2
3
4
5
6
7
8
9
10

S.No
1
 SAPTP-4058 -CnH Brand Vendor Consignment Process
0.4
9/11/2020

Assumptions - Development
The estimate provide will only be valid for 4 weeks / 20 days from date of email

Feasibility studies/RoM estimates could vary by up to +50% and are solely for indicative purposes only and should not be used for budget or funding appro

Estimates are based on the current information provided – should further or different information or documentation be provided then the estimate will be
Estimates provided are only for SAP component changes – estimates for other areas should be requested from relevant parties
Any change in the scope will need to be re-estimated
No Scrum Master or Project Management cost considered in scope
Warranty support is considered for 2 weeks from go live. Any delays or further extension will be considered through CR process
Estimate for TDCS is only for indicative purpose, will be charged based on actuals. Request to provision accordingly.
Estimate for release cost is only for indicative purpose. Request to provision for the amount as the feature/epic could be charged up to the
feature pulls out fully or partially then they would be charged for the release cost.

Release cost (indicative) is estimated with an assumption that the change will be part of PI planning and deployment will be aligned to one
Brand vendor consignment PO will be created manually in SAP, no systematic interface like I2696/I083
BAU process and existing interface will be used to receive the goods, ASN, adjustments, etc. No change in procurement process considered. Any deviation
CR
No pricing during consignment PO creation
No Vendor invoice will be expected for the consignment PO, I0112 is out of scope
No Account posting happens for consignment PO goods recipt
No new reporting requirement in SAP (ECC, StockHub and GMOR), however the metrics and models to be analysed for impact of Consignm
accounting for not to impact current BAU process
StockHub inventory usecase (UC7, UC10, UC15) are out of scope, Any change to be considered as CR
Retro PO, that is Warehouse receiving without a valid PO created in SAP and create the document later in SAP based on GR, is out of scope
Vendor delivering RDC process is not followed in C&H, if brand vendor follows direct RDC delivery, end-to-end analysis or testing to be per
JDA A&R will be used to create replan order from DC to Store , this will be interfaced to SAP via I0185
JDA order may contine both brand and non-brand mixed together
No Change is expected in rest of the Store logistics process, BAU process and interface will be used. Any deviation identified in later stage
Both POS and E-Com sales is considered in scope
Intercompany (IE) and Franchisee are out of scope
MTO Furniture is out of scope
Vendor settlement based on condition contract to be considered as separate estimate
Existing I0011/I0012 Article master interface from RP will be reused and few changes are considered for estimation
- Generate UPC internally in SAP
- Create Consignment infor record with vendor price
No other change in I0012 other than the one stated in previous point,
- adding any few additional attribute to I011/I0012/I0016 are Out of scope
Return process will reduce the consignment stock based on article type.
No Change in RTW (Store to DC return) process, existing BAU process and interface will be used. Any deviation identified in later stage to b
No change in Contract I0077 interface
Warehouse will only dispatch brands products based on order interfaced from SAP, retro dispatch is not considered in scope
Stock adjustment (damage, lost) and related vendor settlement are not in thie estimation scope.
Return for Manaufacturer (RTM) is not in scope
Exiting direct vendor PO type ZP1 will be used, no new PO type
Sales (POS/Ecom) billing document will have mixed product (both Brand & non-brand in same document)
Decision on GL account (balance sheet or P/l) to be decided.
Effort for account clearing activity and profit center sunstitution considered in scope
COGS posting will only consider the purchase price maintained in purchase info record. No other pricing condition can be added in COGS. If anything to be
record price
RTM Center process change are out of scope
Data migration or maintenance is required for Article master. New set of brand articles will be created by Rangeplanner after solution is implemented

Assumptions - ST
Estimates has been provided based on the change description present on demand
Any change in the scope will need to be re-estimated
System testing considered for I011, I0077, I0083, I0185, I0807, I0808, I0060, E-Com process, Stock Hub, GMOR and BW
Testing scope is limited to SAP ECC and PO. No upstream / downstream systems are considered in testing scope. Testing will be carried out within four wal

Regression testing is considered only for existing functionalities

No change / impact to any existing business processes in Master data, Buying, Finance and Sales areas
Test management efforts are not considered separately
UAT support efforts are not considered in scope
SIT (SAP, MS and upstream/downstream systems), Non-SAP PT, Non-SAP OAT and Non-SAP NPEMS estimates will require to be provided s
applicable). These efforts are not considered in this estimation.

Assumptions - PT
Performance test is not considered in scope, as it is interim solution
Testing scope is limited to SAP ECC and PO
NFR will be provided by support teams
PT scope will be revised upon any change in scope
Slots will be booked for projects and testing will be carried out in isolation.
PT approach will be amended to SIT or ST Test approach document - no separate approach document will be produced
Existing workstations will be available for execution
No other SAP / Non-SAP Systems are impacted from performance front - except SAP ECC and PO
GMOR/reporting systems is not considered in PT scope as no impact to performance is foreseen
1 round of baseline testing and 1 rounds of actual performance testing are conisdered in scope. Any additional iterations due to performance issue / optim
process
Exclusions
NA