Cultural Issues Faced While Adopting Agile by Avinash Garg


Published on

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

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Cultural Issues Faced While Adopting Agile by Avinash Garg

  1. 1. Cultural Issues faced while Adopting Agile<br />Avinash Garg<br /><br />91-9818642207<br />1<br />
  2. 2. Brief Update about myself<br />Started my carrier as a Test engineer<br />Software Quality manager<br />Six Sigma Black Belt <br />Got Role of development manager (by accident) and my journey started towards Agile and still….. <br />2<br />
  3. 3. Agenda<br />Before Agile <br />How I met with Agile and got hooked<br />Pilot Project (Agile and Dev team only)<br />Agile at Organization level(other functions got involved)<br />How to save Agile, need help ??<br />3<br />
  4. 4. Before Agile<br />Done all the QA work using traditional waterfall model<br />Things worked fine though question was asked why QA takes 4-5 months after Dev is done, used Six Sigma to bring it to 3 months and also reduced number of bugs reported by customer by 25%.<br />Continued my journey applying waterfall model in Dev process<br /><ul><li>Contd..</li></ul>4<br />
  5. 5. Before Agile<br />Broken development in different pieces (Requirement, Analysis and Design, Coding and Dev Testing)<br />Plan worked fine till coding phase and started getting surprises during coding phase, delivery was always late and schedule variance was about 20% to 25%, while effort variance was as high as 50%. Team always worked very long hours and on weekends to complete development work during end of Project. <br /><ul><li>Contd..</li></ul>5<br />
  6. 6. Before Agile<br />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 ??<br />Started doing more task level breakdown, more emphasis put on requirement and design phase however results were same<br />6<br />
  7. 7. How I met with Agile and fell in Love<br />Met with Agile on net, while searching better methods for Software project management<br />Got impressed and started reading more material and purchased some books<br />Presented my idea to my manager and he gave his go ahead for pilot project… <br />7<br />
  8. 8. Pilot Project implementation<br />Dev team adopted Agile (Scrum)<br />Team motivation was high and things worked great, with no schedule variance and not much quality issues<br />News got spread and senior management started discussion regarding it.<br />Management gave go ahead to implement it at Organization level.<br />8<br />
  9. 9. Agile Adoption at Organization Level<br />Product Owners saw immediate benefit of Agile on cycle time reduction. Previously it was taking minimum 6 months to respond even if development work was 2 to 4 weeks.<br />Dev team was already motivated to implement it<br />QA (Software Testing) and TP (Technical Writers) were not at all enthusiastic with this new change. <br />Dev manager became scrum master. QA and TP continued to work as a separate team with their manager respectively. <br /><ul><li>Contd..</li></ul>9<br />
  10. 10. Agile Adoption at Organization Level<br />Product Owners started raising stories<br />Dev team started with 4 week sprint (Dev only)<br />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)<br />Same thing happened with Technical writers team<br />10<br />
  11. 11. Issues which started coming<br />Priorities getting changed very frequently<br />Release planning activity became adhoc<br />One of the epic feature for a release got dropped after 80% work is done.<br />QA became more and more away from actual dev sprints. QA is testing features which are developed by dev team 2 sprints back.<br />Code being sent to customer without QA testing.<br /><ul><li>Contd..</li></ul>11<br />
  12. 12. Issues which started coming<br />Dev team started working in fire fighting situation to resolve customer issues, which came due to no QA testing.<br />Lot more pressure on dev team to work long hours to meet sprint commitment, while fixing reported customer issues.<br />Confidence of customer is low due to quality issues and slippage on dates<br />12<br />
  13. 13. Where we are heading towards..<br />Customer is not happy<br />Dev team is de-motivated<br />QA team is not happy as release is sent to customer without QA testing<br />Senior management is concerned, as this is getting impact on company financials<br />13<br />
  14. 14. How to get back to Happy days, few areas we are working on<br />QA Testing is happening in parallel with Dev. QA now more involved with development team, no code will be sent to customer without QA testing. Lot more formal/informal communication is happening between QA and Dev. <br />Improving communication to senior management preparing a master project plan, which will act as a data point, to show any change in priority what impact it will have on schedule and cost.<br /><ul><li>Contd..</li></ul>14<br />
  15. 15. How to get back to Happy days, few areas we are working on<br />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.<br />More close co-ordination happening between different teams (marketing, dev, testing, writers, field and support ). Collaboration between different teams.<br />15<br />
  16. 16. Any suggestions you Have<br />16<br />
  17. 17. Things I learned from Day 1 Session<br />Shu, the student copies techniques without adapting them.<br />Ha, the student reflects on what has been learned and breaks free from traditions.<br />Ri, the student is now a practitioner extending the art.<br />17<br /><ul><li>Contd..</li></li></ul><li>Things I learned from Day 1 Session<br />Personal mindset is crucial<br />What did I do wrong?<br />What can I do different?<br />What can I do to help?<br />18<br />
  18. 18. Thanks<br />19<br />