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
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
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
ails

odel.
 Demand (PIC) Estimation Summary
 SAPTP-3052 Update / add the EBS
Project Name (Electronic Bank Statment) Configuration 
Version 0.5
Date 8/24/2020

Story Point Summary

Required Engineering Effort 39
Actual Engineering Effort 30
%Effort Savings 23%
OFL 93%
Cost Before Savings £9,075
Cost after Savings £4,790
% Cost Savings 47%

Additional Costs:
Release Management Cost £3,621
TDCS Cost £1,100
Total SAP Cost After Savings £9,511

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

Excludes
SIT, Non SAP PT / OAT and NPEMS Costs

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

0 £ -
0 £ 1,100.00

Estimator 3.0 to be inserted as an object

  SAPTP-3052 Update / add the EBS
Title (Electronic Bank Statment) Configuration 
Version 0.5
Date 8/24/2020

Scope - SAP Development

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

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

1 SAP ECC

Scope - SAP PT
S. No Application/Interface/NFR/Testing
1 Performance testing not considered in scope as the standard configuration is being used

Scope - OAT
S. No Scope
1 OAT not in scope as there are no CONTROL M Changes
- SAP Development
Scope
Create a new account symbol for charges
Assign Account
Posting key definition
Search String definition - 88 new search strings

cope - SAP ST
Scope

Validations on Search Strings configured for EBS.

Around 88 new search strings configuration in SAP as part of this change.

System: SAP ECC

cope - SAP PT
Scope
ard configuration is being used

Scope - OAT
System
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

27

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

12

S. No
1

S. No
1

S.No
  SAPTP-3052 Update / add the EBS
(Electronic Bank Statment) Configuration 
0.5
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 a

Estimates are based on the current information provided – should further or different information or documentation be provided then the estimate w
Estimates provided are only for SAP component changes – estimates for other areas should be requested from relevant parties
Configuration set up for any new charges are considered i.e. bank charges or any other fee. Depends on the bank statement further
configuraiton / coding requirement to be ascertained
Bank statement will be obtained and shared by business for testing purposes

The changes are limited to only those 88 changes mentioned in the requirement document. If any additional config requirement for bank statement it
Changes are limited to SAP ECC. No changes in SAP PO or any other systems
No Data Cutover and data reconciliation activities are considered in scope
Warranty will be completed within 2 weeks from technical drop. Any further overrun of timelines will be accomodated via CR process
No history data replay in scope
Estimate for TDCS is only for indicative purpose, will be charged based on actuals. Request to provision accordingly.
In case of technical deployment, if business go-live happens beyond 2 weeks of technical go-live then warranty support should be with
No reconciliation or validation included for downstream systems or Reporting systems.
Any change in the scope will need to be re-estimated
Any ad-hoc data trigger from SAP is not considered in scope.
No data reconciliation activities are considered in scope for SAP
No roles and authorization changes are involved
No Scrum Master or Project Management cost considered in scope
End to end cutover plan execution and management not considered in scope
Downstream or end consumer impact to be mitigated by business portfolio team
Any history data correction is not considered in scope
No Recovery activities are considered in scope
UAT approvals and Business co-ordinations will be facilitated by Corporate portfolio team
Any dependencies on payment run, IT & Business SLAs, Business KPIs, 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
Estimate for release cost is only for indicative purpose. Request to provision for the amount as the feature/epic could be charged upto
feature pulls out fully or partially then they would be charged for the release cost.

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 88 new search strings configuration 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 o
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 andPOS 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
No changes to output determination routines in SAP ECC, hence no code changes are involved
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 provid
applicable). These efforts are not considered in this estimation.

Assumptions - PT
Performance testing not considered in scope as the standard configuration is being used

Assumptions - OAT
No control M Job is required manual upload of Bank statement

Exclusions