1 / 11

Agile In Outsourced Environment – A Perspective Zaheer Abbas S. Contractor

Agile In Outsourced Environment – A Perspective Zaheer Abbas S. Contractor . 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.

hawa
Télécharger la présentation

Agile In Outsourced Environment – A Perspective Zaheer Abbas S. Contractor

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agile In Outsourced Environment – A Perspective Zaheer Abbas S. Contractor

  2. 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

  3. Software IT Service Organizations Scenario Varied business execution approach based on customer culture Varied business operations of customers to cater to Varied Inflow of business services portfolio to cater to Adoption of Agile Perceived not Beneficial in Software Business Services Portfolio??

  4. Agile Adoption - PUSH or PULL?? Best Practice Adoption through external PULL or internal PUSH?? 2005 – 2008 2008 – 2010 2010 Onwards 70% 60% 50% 30% 40% 50%

  5. 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 AgileADOPTION to PROACTIVE STRATEGIC Agile TRASFORMATION

  6. 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

  7. 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

  8. 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

  9. Situation2 : Multi Vendor Scenario (Development & Test) Dev Vendor: Hey Customer, Test team has to be co-located in Agile, I can take up the testing job also! Dev. team Vendor Test Vendor: Hey Customer, I get the build on the last day, how do you expect signoff of the sprint on last day! Master Backlog Test team Vendor Test Vendor: Hey Customer, Test team not involved on day to day basis with the Dev vendor, we do not have clarity 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 ???

  10. Q & A Lets Share our thoughts!

  11. Zaheer Abbas S. Contractor • Sr. Manager – Agile COE • zaheerabbas.contractor@wipro.com

More Related