AgileNCR 2010 conference was held in Gurgaon on 17th & 18th July 2010. This largest community driven conference was the Fourth edition of Agile NCR and was organized in collaboration with ASCI. This time the event was based on four major themes : 'Agile for newbies', ' Agile Adoption Challenges', 'Workshops and Software Craftsmanship', and ' Post Agile'.

1. Cultural Issues faced while Adopting Agile Avinash Garg av_garg@yahoo.com 91-9818642207 1

2. Brief Update about myself Started my carrier as a Test engineer Software Quality manager Six Sigma Black Belt Got Role of development manager (by accident) and my journey started towards Agile and still….. 2

3. Agenda Before Agile How I met with Agile and got hooked Pilot Project (Agile and Dev team only) Agile at Organization level(other functions got involved) How to save Agile, need help ?? 3

6. Before Agile And after all the hard work, when delivery goes to QA, there were so many bugs reported which raises questions has Dev team done any testing ?? Started doing more task level breakdown, more emphasis put on requirement and design phase however results were same 6

7. How I met with Agile and fell in Love Met with Agile on net, while searching better methods for Software project management Got impressed and started reading more material and purchased some books Presented my idea to my manager and he gave his go ahead for pilot project… 7

8. Pilot Project implementation Dev team adopted Agile (Scrum) Team motivation was high and things worked great, with no schedule variance and not much quality issues News got spread and senior management started discussion regarding it. Management gave go ahead to implement it at Organization level. 8

10. Agile Adoption at Organization Level Product Owners started raising stories Dev team started with 4 week sprint (Dev only) QA said they will not get involved with Dev in same sprint, once the code will be delivered they will test it, however not along with development (I think this was one of the biggest deviation which led to many issues later) Same thing happened with Technical writers team 10

12. Issues which started coming Dev team started working in fire fighting situation to resolve customer issues, which came due to no QA testing. Lot more pressure on dev team to work long hours to meet sprint commitment, while fixing reported customer issues. Confidence of customer is low due to quality issues and slippage on dates 12

13. Where we are heading towards.. Customer is not happy Dev team is de-motivated QA team is not happy as release is sent to customer without QA testing Senior management is concerned, as this is getting impact on company financials 13

15. How to get back to Happy days, few areas we are working on Dev team will put more emphasis on dev testing. I think one of the area which we missed was not much focus on automated unit testing and using XP practices. More close co-ordination happening between different teams (marketing, dev, testing, writers, field and support ). Collaboration between different teams. 15

16. Any suggestions you Have 16

18. Thanks 19