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 don

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
ent/enhancement projects.

vel when sufficient implementation details are not available.

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

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

History
Description

ft

Benefit Calculations added

d the fields in the cost & savings sheets

options to distribute the total efforts across resources
s location
ned Technology factors and added new Technologies.
the Capacity Based Cost and Savings calculation sheet
wer BI and Service Design
ails

odel.
 Demand (PIC) Estimation Summary
SAPTP-4041 PRGX - Extract Code
Project Name Optimization
Version 0.3
Date 8/24/2020

Story Point Summary

Required Engineering Effort 36
Actual Engineering Effort 27
%Effort Savings 25%
OFL 93%
Cost Before Savings £8,397
Cost after Savings £4,373
% Cost Savings 48%

Additional Costs:
Release Management Cost £3,621
TDCS Cost £550
Total SAP Cost After Savings £8,544

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

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

Version 3.0
6/26/2019
TDCS Cost
Level Resources PD's Value Comments
D Core Services System Specialist 1 £ 550.00 Solution and Design Assurance

0 £ -
0 £ 550.00

Estimator 3.1 to be inserted as an object

 SAPTP-4041 PRGX - Extract Code
Title Optimization
Version 0.3
Date 8/24/2020

Scope - SAP Development

S.No Application/Interface/NFR/Testing
1 SAP ECC
2 SAP ECC

Scope - SAP ST
S. No Application/Interface/NFR/Testing

1 PRGX Table Extraction Program /PRGX/GET_STE

2 Program ZGFI_SET_POSTING_DATE

3 Parameter value in BSIK selection criteria

Scope - SAP PT
S. No Application/Interface/NFR/Testing

1 PRGX Table Extraction Program /PRGX/GET_STE

Scope - SAP OAT

S. No Application/Interface/NFR/Testing
1 OAT not in scope as there are no CONTROL M Changes
AP Development
Scope
PRGX Extract program fix
Variant change and variant update program change

pe - SAP ST
Scope
Validations on the PRGX Table Extraction program for Key tables.
System: SAP ECC

Validations on the updated by the program for First period, the Fiscal year
needs to be previous fiscal year instead of current fiscal year.
System: SAP ECC
Validations on the variant changes for BSIK table extract.

System: SAP ECC

pe - SAP PT
Scope

Performance testing for below tables. Baseline testing (before fix) and
Actual testing (post fix).
1. EKBE
2. BKPF
3. BSAD
4. BSIS
5. BSAK

System: SAP ECC

e - SAP OAT
Scope
Title
Version
Date

S.No
1

3
4

5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

24
25
26

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

12

S.No
1
2
3
4
5
6

7
8

S.No
1
 SAPTP-4041 PRGX - Extract Code
Optimization
0.3
8/24/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
Scope includes program fix (program given by PRGX). This is based on the discussions had with PRGX. However, if PRGX will do the code change, the eff
from the estimate (9 SP)
Testing of the code fix and deployment coordination will be in scope even the code fix will be done by PRGX
The scope includes variant update program fix as well.
Any change in the scope will need to be re-estimated
Any ad-hoc data trigger from SAP is not considered in scope.
No Scrum Master or Project Management cost considered in scope
End to end execution and management not considered in scope
No roles and authorization changes are involved
Any business impact due to reduction of columns or data is to be mitigated by business.
Downstream or end consumer impact to be mitigated by corporate and business team.
Warranty Support is not considered in this estimate. Any hypercare or warranty support requriements to be estimate separately
UAT approvals and Business co-ordinations will be facilitated by Corporate portfolio team
NFR for PT will be co-ordinated by Corporate portfolio team with business
Business approvals on PT NFR will be available as pre-requisite for Test prep and Test execution
Any Infra uplifts are not considered in this estimate. If required, Corporate team to provision the same
Any dependencies on payment run, IT & Business SLAs, Business KPIs, PRGX SLAs to be co-ordinated by Corporate team
M&S to help with any infrastructure requirements and capacity uplifts considering that kit is end of life
Any history data correction is not considered in scope
No Recovery activities are considered in scope
Estimate for release cost is only for indicative purpose. Request to provision for the amount as the feature/epic could be charged upto the
feature pulls out fully or partially then they would be charged for the release cost.
No data reconciliation activities are considered in scope for SAP
M&S is owning the IP for the PRGX programs and TCS is eligible to make any changes for M&S on the third party code

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
Changes are limited to PRGX Extraction program performance optimization and variant changes in SAP
Changes are limited to SAP ECC systems. No other SAP Systems are changed.
Testing scope is limited to SAP ECC. No upstream / downstream systems are considered in testing scope. Testing will be carried out within four walls of SAP
No changes to any existing functionalities in SAP ECC - so no regression testing is considered for existing functionalities
No change / impact to any existing business processes in Master data, Buying, Supply chain UK and POS Sales areas
No impact to any SAP reporting systems due to the change like SAP HANA, SAP BW, POSDM, GMOR - these have not been considered in te
No changes to integration mechanism for file transfers
Management efforts are not considered seperately
UAT support efforts are 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
Testing scope is limited to SAP ECC
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.
Existing workstations will be available for execution
No other SAP / Non-SAP Systems are impacted from performance front - except SAP ECC

1 round be baseline and 1 round of actual testing are considered in scope. Any further iterations due to changes or optimization will be ac

GMOR/reporting systems is not considered in PT scope as no impact to performance is foreseen

Assumptions - OAT
OAT not in scope as there are no CONTROL M Changes