Process at INFOSYS

Projects at Infosys are classified as:

Development()Projects
Maintenance()Projects
Re- Engineering () Projects
The course describe the processes for
Development Projects at Infosys.
 Important Aspect of Infosys

Organization plays an important role in the nature of process

& the way process change.
The following at Infosys help Infosys in deploying() ,
changing process & implementing CMM.
Senior managers are software professionals
Understand need for process initiatives()

Process orientation() & Early adoption() of ISO

Process is not only used for s/w project but also for Human

Resource() , Finance, Travel..etc & Audited.

Early adoption of ISO, build process culture()
 Cont..

Strong commitment() to measurement &

transparency ()
Has high degree of transparency in all its operations
It has strong desire to measure all important factors
(E.g.. Ext. Customer survey, employee satisfaction,
Internal customer satisfaction) & introduce metrics
Training program
New recruits() have rigorous() training
program, Skill upgrading program on New Tech,
project Mgmt, Soft skill, team building &
so..on( KPA of level 3)
 Cont..

Use of Technology
Uses technology for its own operation
Employs integrated system for enterprise
Management via SAP ( for Finance, HRD, project
& personnel activity)
Every employee has personal workstation &
various platform
Audio & Video conferencing() facility for
interacting with customers
 PROJECT INITIATION()

PROPOSAL() & CONTRACT()

 Proposal & Contract

Customer & Vendor Interaction

The Proposal

The Contract
 Proposal & Contract

These two documents are the starting point for

business transaction().
In a business setup, understanding between
Customer & vendor are formalized in a contract
that forms the basis of transaction & has legal()
implication.
The vendor normally proceeds with the project only
when the proposal has been accepted & contract
signed.
 Proposal & Contract

It satisfies a part of RM KPA.

A clearly agreed on contract & proposal help

immensely() in building a good
working relationship() between the
customer & vendor
 Customer & vendor Interaction

By customer itself
By Marketing staff of vendor
After initial contact, the customer requests RIF
(Request for Information)
Strengths, Experience, background, past project,
past & current customer.
After short listing vendor, Customer sends a
Request () for proposal(RFP)
 Customer & vendor Interaction

Request For Proposal(RFP):

Customer Specifies the scope ()of the project
In response, The vendor prepares & sends a proposal to customer
There are two Model : 1) Fixed price 2) T & M
Fixed price model
If requirement has sufficient details, then the vendor
analyses the RFP
Roughly estimates the efforts & schedule & gives the
price.
The price is fixed unless requirement changes.
 Cont

Time & Material model (T & M):

If no sufficient details available, the the project has two parts
First part T & M model for Requirement Analysis & Second
part Fixed price model for developing software
Or the Whole project can be based on T & M model
After accepting & agreeing upon the RFP, customer sends
purchase order (PO) & work commences.
 The Proposal

Has two parts

Technical()
Describes issues relating to project execution
Commercial()
Issues relating to payments for the execution of
project
 The Proposal(Technical)

Technical Description
Describes requirement of the project
Methodology, tools, Technology that is to be used
Assumption
Assumptions made during technical proposal
Assumptions may form the basis for contention, hence it is better to
explicitly specify.
Proposed Solution
planning, strategy,software Architecture, team ..etc
Effort () Estimate
An estimation of the effort required as per requirement
 Cont

Project schedule()
Schedule of the project & schedule of milestones in project
Customer Responsibility
All input required to be provided by Customer in a timely and
coordinated manner are specified here.
Such as input data, manual, contact person, access to customer sites,
hardware/software as per requirement...etc
Penalty / Reward for timely delivery
Penalties for slippage & reward for meeting milestones if any are
specified in this section
 Cont

Risk() Management
The risk assignable to customer & vendor are specified.
Also the risk mitigation plan of the vendor is specified.
Requirement Changes
How to handle requirement changes & how to bill
customer etc is specified in this section.
Other issues
Escalation mechanism, security issues, SPMP issues etc..
 The Proposal(Commercial)

Deals with monetary() benefits

Usually done by PM in consultation with sales team
Pricing() details
Rates for man power()
Special hardware cost
Data communication cost
Consultancy () cost
Payment schedule()
 The Contract

Contract is a Legal Document and not related

to software development
A contract has the following clause:
Scope() of services()
Estimates()
Rates & Payment
Hardware & software
Confidentiality()
 Cont

Security ()
Rights on Data
Nonsolicitation( )
Warranty()
Limitation() of liability ()
Indemnity(): Client & Vendor not responsible
for illegal act affected by a third party
Service level Agreements