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

M&S Agile Estimation Model V4.0 Mar-2020 Updated with 20/21 rate tables
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

with 20/21 rate tables

ails

odel.
 Demand (PIC) Estimation Summary
SAPTP-4045 Access to ZP12, E-Pod Missing, Trading
Project Name Hour changes_SAP Estimate
Version 0.5
Date 8/24/2020

Story Point Summary

Required Engineering Effort 32
Actual Engineering Effort 24
%Effort Savings 25%
OFL 100%
Cost Before Savings £6,685
Cost after Savings £3,168
% Cost Savings 53%

Additional Costs:
Release Management Cost £0
TDCS Cost £0
Total SAP Cost After Savings £3,168

Includes
SAP Support, SAP NPEMS

Excludes
SAP Dev, ST, PT, SIT [SAP and 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 0 £ - Design Assurance

0 £ -
0 £ -

Estimator 4.0 to be inserted as an object

Title SAPTP-4045 Access to ZP12, E-Pod Missing, Trading Hour changes_SAP Estimate
Version 0.5
Date 8/24/2020

Scope - SAP Development

S.No Application/Interface/NFR/Testing
1 No SAP functional development activites are considered in scope

Scope - SAP Support [GRC, Test and Functional]

S. No Application/Interface/NFR/Testing

1 BOT ID additional access to ZP12

2 Foods E-Pod Missing

3 Foods Trading Hour changes

Scope - SAP PT
S. No Application/Interface/NFR/Testing
1 SAP PT is not considered in scope as there are no changes involved in SAP

Scope - SAP OAT

S. No Application/Interface/NFR/Testing
1 No job changes are involved, hence OAT is not considered in scope
ges_SAP Estimate

SAP Development
Scope

rt [GRC, Test and Functional]

Scope
• Addition of Authorization in Roles
• To provide Test ID in FCJ.
• Production deployment of the BOT Role
• GRC Clarifications support

• Analysing trace file for the required authorization in FCJ

• GRC Clarifications support
• Creation of 2 new Single role for EPOD process
• To review the change and results. SAP Functional Support.
• Production deployment of the BOT Role

• Analysing trace file for the required authorization in FCJ

• GRC Clarifications support
• Creation of 1 new Single role for Trading hours
• To provide Test Data/Test ID for UAT and Analysis.
• Production deployment of the BOT Role (CAB Support)
• Post Go live Support

ope - SAP PT
Scope

pe - SAP OAT
Scope
Title
Version
Date

S.No
1

3
4
5
6
7
8
9
10
11
12
13

S.No
1
2
3
4
5
6

S. No
1

S. No
1
 SAPTP-4045 Access to ZP12, E-Pod Missing, Trading Hour changes_SAP Estimate
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 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
No data reconciliation activities are considered in scope
Any ad-hoc Dev / Support activites are not considered in scope.
No SAP development activites are considered in scope except the role changes
No Warranty support is considered in scope
No Scrum Master or Project Management cost considered in scope
Scope is limited to BOT ID additional access to ZP12, Foods E-Pod Missing and Foods Trading Hour changes. Any additional scope to be esti
Required approvals will be in place to create the test ID for Bot in Non-Prod environment (FCJ)
SAP Release costs are not included in the estimate, however changes will be assessed case by case and will incur release costs if applicable
Post go live support is considered only for Foods Trading Hour changes for 2 weeks. Any futher extension of timelines will be accomodated

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
Estiamte is provided to share the test data with required parameters in FCJ
All pre-requisite required in test data will be shared upfront to SAP team in order to identify / create the required data in FCJ
Any changes to the existing data will need to be agreed by requesting portfolio team with all other BU portfolios using SAP and data in FCJ
No System test activities or validation steps are considered in scope

Assumptions - PT
SAP PT is not considered in scope as there are no changes involved in SAP

Assumptions - OAT
No job changes are involved, hence OAT is not considered in scope