Requirement Management Flow

Requirement Understanding & Feasibility Planning & Implementation & Testing Closure
Bayer Business

Start

Update BR, if Needed Conduct customer Test Results &

3.11 Approve test; If required Update Defect
Business OK
Proposal? Supported by CG Log?
Requirement (BR) SPOC (QG6)
Development Cancelled
250-Development Cancelled
Cancelled Not OK

Provide Final
Acceptance for
Start Implementation Capgemini
Process by creating CRT in Complete Implementation
Prepare High Level 220-CRT in
Solman Activities, Close CRT & if
FDD Customer Test
140-Set-up CRT applicable, support Hyper-care
000- In Functional OK Period
Functional Expert

Analysis Create Proposal & 230-In Production under Hyper

FDD elaboration
WIP Send for Customer Care
XXX- FDD WIP if Outside Project Test Results
Present the requirement. Finalize the FDD with all Participate in regular
130-Proposed & Update Not OK
Explain open areas to be missing details along with Demos with Developers
Defect Log?
clarified with Bayer Business. Test Scenarios with Test to see progress and
(QG5)
Ensure team understand the Data ensure desired
Update High level FS & Hyper Care Period Completed,
requirement by providing 150-Finalize Estimations & functionalities are
Assign to BBS Dev Knowledge Transfer to RUN
sufficient business process Planning demonstrated
Coordinator for review Team Completed
070-FS in BBS Review explanation 240-Implementation Complete
Execute CRT Testing
(Q Box Testing)
OK

Carry out intake check Facilitate Handshake Meeting

and Agree on skill Support with Bayer context Confirm Review and
requirement with CG knowledge, Ensure Provide Customer
SPoC, if needed involve requirement understanding is Satisfaction rating
FIL correct and solution approach 210-
is consistent with requirement Implementation in
Bayer Dev Coordinator

& Bayer norms. Consider need Functional Review

Follow Bayer Review the rough
of joint FDD elaboration Yes
Assign to Onsite estimate and HLD
No Not OK OK
Capgemini development
process Estimation
Clearance
Yes Process Bayer
2.6 Assign Requirement D-Box Testing? Not OK
to Capgemini (BQG4)
080-FDD Assigned to 080-FDD Assigned No
Capgemini to Capgemini

Full Agile New Estimate Feedback on:

Process Approved Documentation
PARTICIPANTS - Functional Expert,
Yes Quality and
FIL consultant (if needed),
Development Code
Dev Coordinator, CG SPoC,
Quality
CG Developer, Cluster Manager
Agile Yes

Facilitate Handshake Meeting Finalize Outcome of Finalize Rough Is new

Waterfall FDD estimation and update Estimate out of the
Support with Bayer context the Handshake Approach Test Results & Update
elaboration HTS Accuracy % No Verify
knowledge, Ensure sufficient meeting for Decided Defect Log, Review
Organize needed 073 – Rough estimation Limits Technical Defect or
requirement understanding is proceeding with Checklist?
Yes Handshake in BBS Review CR?
achieved and reliable solution appropriate process 200-Implementation in
Meeting/s (QG7)
approach is agreed in meeting/s variant Technical Review CR
No Defect
Involve FIL consultant when 090 – HTS WIP with
Identify Suitable required Capgemini
Developer/s Handshake
085 – Awaiting meeting
No
Handshake Meeting needed? Small work, clear Estimations & Status
requirement & no Planning Agreed 175 – Status
Yes
challenges on tech 165 – Development Development 140-Set-up CRT
feasibility Planned in Progress
Handshake Meeting Outcome/
Pre-requisite for next steps
Capgemini Cluster SPoC

addressed No
OK
 Open Questions clarified
 Complexity, feasibility, alignment
needs and risk understood and PoC needed /
approach (agile/waterfall) for Innovation
development agreed Requirements
 Sufficient and reliable solution
visible to derive rough
estimations (<20,160<x >20,>160)
 Approach for next steps – PoC, Yes
further elaboration of FDD (jointly Yes
with developer/FIL or directly by
FE) agreed Ensure start of
Agree on PoC estimates development as per
 Initial planning (elaboration in PoC Prepare/Update (in SPOC Testing
with BBS and High level plan
OPM) can be made for indicative Results & Demo case of CR) Final Not to Verify Functionality &
Design No 170 – Development
purpose. meet objective Estimations & OK Review Documentation
040-PoC in in Progress;
of PoC Planning (QG3)
 Agree the planned estimation No Implementation 175 – Development
submission date in Rework
 Sufficient clarity on Testing
scenarios, data and approach is
visible

Develop POC in
Development
Prepare for Ask Questions, Coding & Demos to
Environment, do Update TS to
Handshake meeting Clarify Doubts, Prepare HTS & Functional Experts
regular demo to available details
with SPoC and Present draft rough estimations Update coding %
address expectations
Manager solution approach completion every
Capgemini Developer

from PoC
Identify open 050-POC in Testing day
questions, prepare
solution approach
Not OK Conduct
Developer Test &
Perform internal
Provide Knowledge Transfer (KT) to
reviews
Update TS & Developer RUN and Support hyper care period
180-Development
Test Results Document (1 month if not defined in the
In Capgemini
project timelines), If required
Review;
185 – Rework in
Review

Not OK
Capgemini Development Manager

Ask Questions, Review HTS, Rough Review

Clarify Doubts, Estimations and FDD details, Verify Code & Set Status
Assign Developer Support to reach estimation TS, Estimations & Planning ok 190-Implementation in
Identify Suitable update Internal
Provide guidance on reliable solution accuracy % 160 - Development Defect Log, Review OK Capgemini Review;
Developer/s 195 – Rework in
solution approach approach, discuss 072 – Rough Planning and Kick-off Checklist? (QG2)
needs of PoC if Estimation & HTS in (QG1) Implementation review
relevant Capgemini review