• Like
Cultural Issues Faced While Adopting Agile by Avinash Garg
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Cultural Issues Faced While Adopting Agile by Avinash Garg

  • 855 views
Published

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 …

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
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
855
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
24
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 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
  • 4. Before Agile
    Done all the QA work using traditional waterfall model
    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%.
    Continued my journey applying waterfall model in Dev process
    • Contd..
    4
  • 5. Before Agile
    Broken development in different pieces (Requirement, Analysis and Design, Coding and Dev Testing)
    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.
    • Contd..
    5
  • 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
  • 9. Agile Adoption at Organization Level
    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.
    Dev team was already motivated to implement it
    QA (Software Testing) and TP (Technical Writers) were not at all enthusiastic with this new change.
    Dev manager became scrum master. QA and TP continued to work as a separate team with their manager respectively.
    • Contd..
    9
  • 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
  • 11. Issues which started coming
    Priorities getting changed very frequently
    Release planning activity became adhoc
    One of the epic feature for a release got dropped after 80% work is done.
    QA became more and more away from actual dev sprints. QA is testing features which are developed by dev team 2 sprints back.
    Code being sent to customer without QA testing.
    • Contd..
    11
  • 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
  • 14. How to get back to Happy days, few areas we are working on
    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.
    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.
    • Contd..
    14
  • 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
  • 17. Things I learned from Day 1 Session
    Shu, the student copies techniques without adapting them.
    Ha, the student reflects on what has been learned and breaks free from traditions.
    Ri, the student is now a practitioner extending the art.
    17
    • Contd..
  • Things I learned from Day 1 Session
    Personal mindset is crucial
    What did I do wrong?
    What can I do different?
    What can I do to help?
    18
  • 18. Thanks
    19