Bayer Development Factory

Requirement Delivery Process

Improvements

December, 2014

Delivering Excellence Together

Copyright © Capgemini 2014. All Rights Reserved 1
Objective

 Current delivery process is a key concern area which needs to be improved by simplifying and addressing
requirements especially in case of for smaller size work or bigger packages or project related participations

 This document intends to provide an understanding of the pain areas, appropriate alternatives to some of the
process steps and guidance on usage procedure for each step

 The issues/pain areas for process is dependent on type of work. A broader classification has been made
based on the estimation duration and following categories have been identified to begin with:

• Small size work - Less than 20 Hrs.

• Moderate size work - 20 Hrs. or more but less than 160 Hrs.
• Big packages – Typically Major enhancements, more than 160 Hrs
• Agile Work (typically size is bigger than 160 though individual feature may be smaller in size to
address)

 Considering that there are more than 1 process options possible, a guideline to select appropriate process
variant is hence essential

Copyright © Capgemini 2014. All Rights Reserved 2

Process Variants

Initial
Require Technical
Process *Guesstimate
ment Feasibility / Process
Variant (X hrs) of Work
Clarity Alignment Needs
Size
1 Clear 20< X< 160 Known Process in current form

2 Clear 20< X< 160 Unknown PoC first and then current process

3 Unclear 20< X< 160 Unknown Joint Development of FDD + PoC +Process in current form

4 Clear X < 20 Known Small Work Process

5 Clear X < 20 Unknown PoC + Small Work Process

6 Unclear X < 20 Unknown Joint Development of FDD + PoC + Small Process

7 Clear 160 < X Mostly Known Regular Process + Project Management + Demo

8 Clear 160 < X Mostly Unknown PoC First for Tech Feasibility, then follow Process 6
PoC first for unclear business
Mostly Unknown Waterfall -
9 Unclear 160 < X requirements then follow process 6
(Feature List Must)
Agile - Full agile approach and PoC

* Initial guesstimate is the size of the development work which is fully reusable e.g. even if the development is
done in sandbox environment

Copyright © Capgemini 2014. All Rights Reserved 3

Practical Hints for Technical Feasibility & Alignment Needs

Need for
User Overall
Type of Technical
Technical feasibility and Alignment needs alignment Complexit
development Feasibility
needs y Indicator
Check
• Technical feasibility in application
development work is essential aspect to User Interface High High Unknown
consider before actual start of work and (Module pool,
hence even while selecting the process for Webdynpro)
delivery.
• Feasibility check can be decided based on New Functionality High High Unknown
expert input where expert is someone with or Processes (also
relevant content knowledge. includes workflows)
• Even if requirement is found to be
technically feasible, the speed and accuracy Forms & Outputs Medium High Mostly
of product may vary if the necessary Smartform, Adobe Unknown
interaction and alignments have not taken form
place as part of the process.
• Table beside, is providing guidance/ Interfaces Medium Medium Mostly
practical hint on how the overall complexity Unknown
of work can be interpreted considering this
topic. Most of the other Mostly
development Known
objects

Copyright © Capgemini 2014. All Rights Reserved 4

Current Process - High-level Process View

Delivery Phases 
Roles
Feasibility Analysis & Approval Planning, Implementation & Testing Closure
Bayer 1. Business 7b. Approve
13. UAT (QG6)
Business Requirement Proposal
8a. Create CRT in 12. Functional
14. Release,
Functional 5. Handshake 5c. Test PoC (if 7a. Create Solution Manager + Testing (CRT
2. Prepare high Hyper Care &
Expert (FE) Meeting PoC needed) Proposal Finalize FDD, TS Testing) in Q-Box
level FDD + Closure
and Test Data (QG5)
Update high Clarify open
11. Bayer D-Box
level FS + questions +
6d. Review Testing, review
Review + Intake
Bayer Dev Decide the rough testing + quality
check + Analyze
Coordinator approach for estimate and 8b. Clarification check of coding &
skill requirement
next steps – HLD Meeting to prepare documentation
Joint FDD, PoC final estimation and (QG4)
+ 5a. 5b. Agree on 6c. Finalize planning
Capgemini 3. Identify 15. Hyper Care
Prepare PoC estimates rough 10b. SPoC (D-Box)
Cluster SPoC + suitable Rough High support & KT to
Joint FDD with BBS & HLD estimate and Testing (QG3)
FIL (if required) developer/s + Level Technical run
(if (if PoC needed) update HTS
Provide Design +
needed) 10a. Code Review,
Capgemini guidance on Plan Milestones 6b. Review 8c. Planning
Developer Test,
Development solution Dates + HTS & rough Development & Kick-
Internal Review
Manager approach estimations off (QG1)
Decide if FIL 5c. Develop PoC (QG2)
4. Prepare for needed? + in Development
Handshake Environment +
Lead
Meeting + Test PoC (if PoC 6a. Prepare 9. Coding +
Capgemini Identification +
Identify open needed) HTS & rough Developer test +
Developer Assignment of
questions + estimations Documentation
Prepare solution resources DRAFT 1
approach

Copyright © Capgemini 2014. All Rights Reserved 5