Introduction
Purpose
Demand management is the supply chain management process that balances the customers’ requirements with the capabilities of the supply chain. With the right process in place, management can match supply with demand proactively and execute the plan with minimal disruptions. The process is not limited to forecasting. It includes synchronizing supply and demand, increasing flexibility, and reducing variability.
Scope
This document describes Demand Management process, individual stages, key roles and their responsibilities.
Demand Management Process
Demand management is the supply chain management process that balances the customers’ requirements with the capabilities of the supply chain. With the right process in place, management can match supply with demand proactively and execute the plan with minimal disruptions. The process is not limited to forecasting. It includes synchronizing supply and demand, increasing flexibility, and reducing variability.
Demand Management Stages overview
Process of demand management is divided into several stages which helps identify demand, describe it precisely, propose solution, estimate effort and deliver it. Delivery is not part of this document.
Identifying demand
Demand identification is a first step in the process. Correctly identified demand may be processed efficiently. There is no strict guide, how to identify demand, each Product Owner should be able to work with their counter parts and end-users to identify needs and propose ways to address them.
Once need is clarified by Product Owner it needs to send to the PMO to further process it. Key information that are required:
Requestor name / e-mail
Additional contacts who may help with demand review and delivery at later stages
Business case description – brief description of the problem we’re trying to address and what is expected end result
Is this a new use case or lift and shift of existing functionality?
Expected delivery date?
Priority (1 – Critical, 2 – High, 3 – Medium, 4 – Low)
Sponsor
Impact, if not delivered?
Is this a Global Function, Capability Center or GBU requirement?
Preferred way to provide this information is through JIRA Story in Enterprise Data project. Other accepted method is via e-mail: Adam Kaszuba (Unlicensed)
Initial Assessment
At this stage PMO should receive basic information about demand and should be able to review its content. During Initial Assessment PMO is verifying content of demand, if all basic information has been provided. If need be, PMO will contact requestor for clarifying or adding missing information before moving it another stage.
During Initial Assessment PMO is also setting up communication model so key actors can participate and contribute during further stages.
Review and Design
During Review and Design stage, team is gathering detailed information about the demand, collects necessary inputs and documents requirements. Based on gathered information, solution is being designed and presented to Architecture Review Board.
Gathering detailed information should always be documented in Questionnaire file and any other documents team see necessary.
Workshop
As part of Review and Design stage it may be necessary to setup a Workshop session to go through Questionnaire and present relevant information and requirements. If team decides so, Workshop session may be skipped.
Workshop session is an activity requiring participation from both Requestor, key users and Solutioning team. Expected is presentation of the problem
Design
Once all information has been provided, team is designs solution suited for the requirements. Solution should consist of architecture diagram along with description and service description. Design phase is not limited only to producing documentation, but also requires estimating effort required to build solution and propose plan of execution which can be handed over to delivery in later stages.
Plan should be precise enough to give requestor understanding on when actual delivery may be expected.
Effort estimation should include information about roles required to deliver project and time required at each step of the project.
Architecture Review Board
TBD
Cost Estimation
Based on design documents prepared during earlier stages PMO prepares cost estimation. Estimation has to include license cost, resource cost to build solution and run costs once solution is already delivered. Calculation is a ROM estimate which may differ from actual costs.
Separately to cost estimation at this stage resource availability has to be align for delivery activities once PMR approval is gathered.
Portfolio Management Review
Review meeting is conducted every 4th Thursday of the month.
Template of Project OnePager and Finance Sheet can be found here:
Handover to Delivery
TBD
Roles & Responsibilities
Product Owner
Accountable for defining and communication of user stories
Provide correct interpretations/ clarification on user stories whenever required
Accountable for prioritization of project/sprint backlogs on an ongoing basis
Oversee build and deployment of user stories
Participate in iterative retrospective meets to provide inputs to improve processe
PMO
Feasibility of Demand during Demand Identification phase and understand business user requirements
Overall accountability for Demand Management process and it’s efficiency
Scrum Master
Accountable of overall planning and execution and adherence to project timelines for delivery of each user stories
Responsible for overall delivery of sprint backlogs
Platform Architect
Data Engineering Lead
Data Governance Lead
RACI Table
| Product Owner | Data Engineering | Data Governance | PMO | Scrum Master | Data Integration |
Identify | R |
|
| C |
|
|
Initial Assessment | C | I | I | R | I | I |
Technical Review |
| R | R |
|
| R |
Architecture Review Board | C | R | C | I |
| C |
Cost Estimation | C | C | C | R | C | C |
PMR Approval (only for new Products) | R |
|
| C |
|
|
Handover to execution | C | C |
| A | C |
|