2. www.scrumindia.in
Agenda
Agile in IT Software Services Organization
PUSH or PULL - Adoption
Does it really gain by adopting Agile?
Reasons Uncovered for Agile Transformation
Practical Situations
Date
Name
ScrumIndia.In
Proprietary Information
2
3. www.scrumindia.in
Software IT Service Organizations Scenario
Varied Inflow
of business
services
portfolio to
cater to
Varied business
execution approach
based on customer
culture
Varied business
operations of
customers to cater
to
Adoption of Agile Perceived not Beneficial in Software Business Services Portfolio??
Date
Name
ScrumIndia.In
Proprietary Information
3
4. www.scrumindia.in
Agile Adoption - PUSH or PULL??
Best Practice Adoption through external PULL or internal PUSH??
2005 – 2008
70%
Date
Name
2008 – 2010
30%
60%
ScrumIndia.In
2010 Onwards
40%
50%
Proprietary Information
4
50%
5. www.scrumindia.in
Does it Really Benefit by Adopting Agile?
Adopting Agile is to align to
customer demands and
gain business!
Business as usual by
providing core delivery
service irrespective of the
execution mechanism!
ARE WE MISSING THE BIG
PICTURE???
NEED BASED Agile ADOPTION to PROACTIVE STRATEGIC Agile TRASFORMATION
Date
Name
ScrumIndia.In
Proprietary Information
5
6. www.scrumindia.in
Agile Adoption - Various Scenarios
CUSTOMER PULL
Maturity of customer in Agile Adoption?
Highly Mature and requesting vendors to align to realized stated benefits of Agile
New Comers and requesting vendors to align without any commitment from them!
INTERNAL PUSH
Alignment of Internal Stakeholders
How does it help their topline or bottom line growth!
Does it matter if existing execution mechanism is already achieving high CSAT
Agile adoption translating all the benefits to customer, how does it benefit internal teams
Alignment of External Customers
Maturity of Customer in Agile adoption
Readiness to provide the given commitment from business and other stakeholders
Multi Vendor scenario
Date
Name
ScrumIndia.In
Proprietary Information
6
7. www.scrumindia.in
Reasons Uncovered for Agile Transformation
Move from Just Being Vendor to Client Partner
Collaborative Approach, Increased Customer Confidence
Early On
Uncovering Technical and Business Risks Early On and
Effective Risk Sharing
Shift from T&M/FPP to Fixed Capacity/Out Come Based
Value Driven Model
Do it Right First Time[DRFT] : Sustained Quality & Minimized
Overruns
Engineering Rigor & Business Focus Practices
Date
Name
ScrumIndia.In
Proprietary Information
7
8. www.scrumindia.in
Situation 1 : Multi Vendor Scenario (Development)
Vendor A
Backlog
Master
Backlog
Vendor B
Backlog
Vendor C
Backlog
Slicing of Backlog to minimize dependencies amongst team
Consensus on Common Estimation Approach
Consensus on Velocity based Pricing Schedule
Integration amongst various modules and regression
Participation as active strategist for the customer
Date
Name
ScrumIndia.In
Proprietary Information
8
9. www.scrumindia.in
Situation 2 : Multi Vendor Scenario (Development & Test)
Dev. team
Vendor
Dev Vendor: Hey
Customer, Test team
has to be co-located
in Agile, I can take up
the testing job also!
Master
Backlog
Test Vendor: Hey Customer,
Test team not involved on
day to day basis with the Dev
vendor, we do not have
clarity
Test Vendor: Hey Customer,
I get the build on the last day,
how do you expect signoff of
the sprint on last day!
Test team
Vendor
Test Vendor: Code keeps on
changing daily,& our defects
considered as feedback until
end of iteration!
Only those feedback not
address until end of sprint is
considered defect, how do
we measure our test
effectiveness!
Dev Vendor: Test team
efforts should be part of the
overall velocity of the team
WHAT IF We have Separate UAT, Sys.Test, Ops, Release Management teams ???
Date
Name
ScrumIndia.In
Proprietary Information
9
11. www.scrumindia.in
• Zaheer Abbas S. Contractor
• Sr. Manager – Agile COE
• zaheerabbas.contractor@wipro.com
Date
Name
ScrumIndia.In
Proprietary Information
11