Agile Adoption: Making it Successful<br />
Agile Adoption: Making it Successful<br />For a successful adoption, it is important to be clear about <br />“Why" the mov...
Introduction<br />Ambreesh Bangur<br />Development / Project Manager / Agile Enthusiast<br />11 years of s/w industry expe...
Agenda<br />Introduction<br />The “Why”<br />The “What”<br />The “Who”<br />The “How”<br />Questions<br />
The “Why”<br />Be clear about "why" the move to agile? <br />What are the key pain points today?<br />What are the improve...
The “What”<br />Which practices of agile make sense for the organization/team to adopt? <br />What customizations to the p...
The “Who”<br />This is the most important piece<br />“Individuals and interactions over processes and tools”<br />It is im...
The “Who”<br />Who all will be affected? And “how”<br />Dev, QA, Documentation, Localization, Product Management, Steering...
The “Who”<br />Agile Teams need specific behaviors<br />Adaptable<br />Self organizing & self-disciplined<br /> Collaborat...
The “How”<br />Just following superficial practices will not help<br />Doing a daily stand up, iterative development is “e...
The “How”<br />Like any change in an organization, this needs to be planned, managed and dealt with <br />There will be re...
Summary<br />Adoption itself could be "agile" <br />Done in an iterative way with regular feedback<br />Begin a “Pilot”?<b...
Questions<br />Resources<br />http://alistair.cockburn.us/Is+the+failure+in+agile+adoption+due+to+cargo+cult,+shu+actions,...
Agile Adoption Case Study<br />“Why”<br />Developing a new product, needed something for adaptable and quick in terms of d...
Agile Adoption Case Study<br />“What”<br />Dev and QA team in different sites, co-located them<br />Product Manager, Busin...
Upcoming SlideShare
Loading in …5
×

Agile Adoption: Making it Successful by Ambreesh Bangur

1,118 views

Published on

AgileNCR 2010 conference was held in Gurgaon on 17th &amp; 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
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,118
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
43
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • About the SpeakerOver the last 5 years, has been instrumental in adoption of agile in 2-3 teams ranging from a services firm to a startup where a more traditional “waterfallish” model was in place. 
  • Agile Adoption: Making it Successful by Ambreesh Bangur

    1. 1. Agile Adoption: Making it Successful<br />
    2. 2. Agile Adoption: Making it Successful<br />For a successful adoption, it is important to be clear about <br />“Why" the move to agile? <br />“What” are the benefits that adopting agile will bring? <br />“Which” practices of agile make sense for the organization to adopt? <br />“Who” all will be affected?<br />“How” should we adopt agile and bring about the “change”?<br />This presentation aims to highlight some of the key considerations for a successful agile adoption.<br />
    3. 3. Introduction<br />Ambreesh Bangur<br />Development / Project Manager / Agile Enthusiast<br />11 years of s/w industry experience as developer and manager<br />Involved with adopting agile in 3 teams over the last 4 years ranging from a services firm to a startup, where a more traditional, “waterfallish” model was in place. <br />Intended Audience<br />People planning to adopt agile – Can consider the ideas presented to help define a strategy for trying agile<br />People who are/have adopted agile – May be some of the issues discussed here are applicable to them<br />
    4. 4. Agenda<br />Introduction<br />The “Why”<br />The “What”<br />The “Who”<br />The “How”<br />Questions<br />
    5. 5. The “Why”<br />Be clear about "why" the move to agile? <br />What are the key pain points today?<br />What are the improvements that agile can bring?<br />Is this the latest “trend”?<br />Share the “why”<br />Acceptance vs Imposition<br />
    6. 6. The “What”<br />Which practices of agile make sense for the organization/team to adopt? <br />What customizations to the practices should be done to adapt them to our context?<br />Large Team, Distributed team across time zones<br />
    7. 7. The “Who”<br />This is the most important piece<br />“Individuals and interactions over processes and tools”<br />It is important that people are “trained” in agile “principles” & “values” not just “practices”<br />“We have lots of bits of paper on the walls, and we ask the 3 Scrum questions at stand-up every day, and we don’t do any planning, design, or documentation, but software still isn’t coming out!”<br />
    8. 8. The “Who”<br />Who all will be affected? And “how”<br />Dev, QA, Documentation, Localization, Product Management, Steering Team etc.. <br />Business and stakeholder buy-in is important and the right expectations need to be set.  <br />
    9. 9. The “Who”<br />Agile Teams need specific behaviors<br />Adaptable<br />Self organizing & self-disciplined<br /> Collaborative and collective ownership<br />Interaction<br />Simplicity, “Do what makes sense” attitude<br />
    10. 10. The “How”<br />Just following superficial practices will not help<br />Doing a daily stand up, iterative development is “easy” but not enough<br />Cross functional involvement, customer or customer representation, feedback is important<br />
    11. 11. The “How”<br />Like any change in an organization, this needs to be planned, managed and dealt with <br />There will be resistance<br />Agile “Coach” / “Mentor” can help teams<br />
    12. 12. Summary<br />Adoption itself could be "agile" <br />Done in an iterative way with regular feedback<br />Begin a “Pilot”?<br />Guiding principles are more important than practices<br />Collaborative and evolutionary rather than prescriptive<br />
    13. 13. Questions<br />Resources<br />http://alistair.cockburn.us/Is+the+failure+in+agile+adoption+due+to+cargo+cult,+shu+actions,+or+just+laziness<br />http://martinfowler.com/articles/agileOffshore.html<br />http://martinfowler.com/articles/newMethodology.html<br />
    14. 14. Agile Adoption Case Study<br />“Why”<br />Developing a new product, needed something for adaptable and quick in terms of delivering a working system<br />I had experience with Agile and SCRUM and thought it would work<br />“Who”<br />Discussed with all involved about the “change”, got buy-in<br />Checked the impact with each team – Dev, QA, Documentation, Product Management and Business.<br />
    15. 15. Agile Adoption Case Study<br />“What”<br />Dev and QA team in different sites, co-located them<br />Product Manager, Business in the US<br />Daily Scrum, reduced frequency later<br />System Metaphor, Minimal Design documents<br />Wiki <br />User centric design, frequent showcases, prototyping<br />No Burndown, Weekly feature based milestones<br />Regular review of Product Backlog and Feedback<br />No Test Driven Development, No Automation of System Tests for v1.<br />No Pair Programming, Peer Review<br />“How”<br />Date and people were “fixed”, Scope was managed<br />Introduced people to the key concepts of “Agile”<br />Checked for feedback every 3-4 weeks<br />

    ×