OUM
RD.01 MoSCoW List
Company Name
Business Requirements - Finance Track
Author: KASP
Creation Date: 9/1/2022
Last Updated: 9/27/2022
Document Ref:
Version: V3.0
Approvals
Approver Signature
File Ref: 878006157.xlsx Title Page
RD.01 MoSCoW List
Document Control
Change Record
Date Author Version Change Reference
1/15/2025 KASP V1.0 First Version
Reviewers
No Name Position Note
File Ref: 878006157.xlsx Document Control
S. No Column
1 MOSCOW.ID
2 Source
MOSCOW Classification
3
4 Requirement Description
5 Requirement Owner
FIT/GAP
6
7 Category
8 Complexity
9 Priority
10 Module
11 High Level Approach
CEMLI ID
12
13 Test Case ID
14 RAID ID
15 Status
16 Comments
Guidelines to fill
Unique Identifier for each line of requirement. Advised to be kept in multiples of 10 (10, 20, 30)
When was the requirement presented by client, for eg. Explore session, CRP1/CRP2, UAT, Milestone Review etc.
M - MUST: Describes a requirement that must be satisfied in the final solution for the solution to be considered a success
S - SHOULD: Represents a high-priority item that should be included in the solution if it is possible
C - COULD: Describes a requirement which is considered desirable but not necessary. This will be included if time and resources permit
W - WON'T: Represents a requirement that stakeholders have agreed will not be implemented in a given release, but may be
considered for the future
Details of requirement
Client side person who raised the requirement and hence will be involved in all sessions inclusing validations and testing
FIT - Standard Functionality
GAP - Not a standard functionality. Will need a custom object
Process this requirement belongs to. For eg, invoice creation, approvals, supplier creation etc
High, Low, Medium
High, Low, Medium
Rise Cloud module
Proposed solution
Fill in case of gaps. ID of the CEMLI component being developed to address the requirement
(Configuration, Extension, Modification, Localization, and Integration)
CEMLI is Oracle's published guidelines for developing and implementing custom extensions to Oracle Applications.
Test script which can be used to test the MOSCOW ID
Issues related to this requirement
Status
Comments
M - MUST: Describes a requirement that must be satisfie
S - SHOULD: Represents a high-priority item
C - COULD: Describes a requirement which is considered desira
W - WON'T: Represents a requirement that stakeholders have agreed w
MOSCOW
MOSCOW.ID Source Classification Requirement Description
10 Explore Session M Coding Mask
20 Explore Session M Breakdown Structure (WBS Elements)
30 Explore Session M Assign Budget
40 Explore Session M Assign Materials to the project
50 Explore Session C Assign Labor to the Project
60 Explore Session M
70 Explore Session M
80 Explore Session M
90 Explore Session M
ST: Describes a requirement that must be satisfied in the final solution for the solution to be considered a success
S - SHOULD: Represents a high-priority item that should be included in the solution if it is possible
scribes a requirement which is considered desirable but not necessary. This will be included if time and resources permit
ts a requirement that stakeholders have agreed will not be implemented in a given release, but may be considered for the future
Requirement Owner FIT/GAP Category Complexity Priority Module High Level Approach
FIT Project Process High PS High
FIT Project Process High PS High
FIT Project Process High PS High
FIT Execution Process High PS High
FIT Project Process Meduim High PS High
FIT Project Process High PS High
FIT Project Process High PS High
FIT Project Process High PS High
FIT Project Process High PS High
ture
Test Case ID RAID ID Status Comments
