Agile reluctancy in india anju gahlawat
•
1 like•603 views
The document summarizes a presentation given on adopting Agile practices in India. The presenter discusses two main reasons for the reluctance to adopt Agile in India: assumptions and myths about Agile practices, and traditional habits that conflict with Agile. Some specific myths addressed include beliefs that Agile means no guidelines, plans or documentation; compromises quality; and is only for new projects. Traditional habits discussed include command-and-control management styles, non-constructive retrospectives, overly detailed user stories, and planning too far in advance. The presenter advocates moving past these myths and habits to successfully implement Agile.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Agile reluctancy in india anju gahlawat
Similar to Agile reluctancy in india anju gahlawat (20)
Recently uploaded
Recently uploaded (20)
Agile reluctancy in india anju gahlawat
- 1. Agile Convention 2013 1st Agile and Scrum Event in Noida Presenter’s Picture Agile Reluctancy in India Anju Gahlawat Data Engineer at TCS www.agilenoida.wordpress.com
- 2. Before we start…. • Laptops/ mobiles are more dearer when they are inactive • All thoughts specified here are my viewpoint and experience and may differ from person to person. • Please shout on the spot in case you have any query rather than waiting for the Q&A slide.
- 3. Agile has less popularity in India? The Basis of analyzing the popularity of Agile in my talk revolves around two things: • Assumptions/Myths with Agile • Habits
- 4. Undisciplined Agile Assumptions/Myths with Agile No Guidelines, No processes and No Plans
- 6. Compromise in Quality Assumptions/Myths with Agile • There is a compromise in quality due to early delivery and less documentation
- 7. No Separate Testing Phase Assumptions/Myths with Agile
- 8. Fear of Senior Management Assumptions/Myths with Agile • Ahh….there is no project manager in Agile…What to do now? Will I lose my job?
- 9. Difficulty in scaling distributed team Assumptions/Myths with Agile • How can I scale my team? • How can I collaborate with my team scattered in different locations at different time zones?
- 10. More Freedom To Team Assumptions/Myths with Agile • Independent and self-organized team can do whatever they want leading to Indiscipline
- 11. Welcome changes anytime Assumptions/Myths with Agile
- 12. Defining Milestones Assumptions/Myths with Agile • In the fast paced agile development methodology, determining the milestones would pose challenges.
- 13. I know all Agile Assumptions/Myths with Agile
- 14. Pair Programming Assumptions/Myths with Agile • Why should I waste one of my resource keep sitting and looking on the partners computer when he can also code?
- 15. Agile is for new development only? Assumptions/Myths with Agile • I am working in a support and maintenance project. Do I need Agile?
- 16. Everything in my plate in one go Habitual of
- 17. Command Control Habitual of living in BOSS is always right. How can I take decisions? I will follow his orders only.
- 18. Retrospectives Bl am eG am e OR Sil e nt R et ro sp e ct ive s Habitual of • Communication leads to valuable feedback which encourages simplicity allowing the courage to change
- 19. Decorative and fancy user stories Habitual of • Gold plating • Too Many Details (not INVEST)
- 20. Thinking Too Far Ahead Habitual of I know we are only in iteration 1, but I did story 3 and knew that story 322 is depended on it, so I did that one too! Cool huh! www.agilenoida.wordpress.com
- 21. So leave all myths and Habits to • Text G A e B E IL www.agilenoida.wordpress.com
- 22. Thank You. Agile Noida India www.agilenoida.wordpress.com
Editor's Notes
- <number>
- No guidelines and processes and No plans <number>
- Make a cross in this <number>
- Due to early delivery and Less documentation <number>
- testing is not a phase. It is integrated into Development & Testing. QA is not the last line of defense but involved at the beginning of the project. Agile testing focuses on testing iteratively, as often as stable code base is available, until quality is achieved from end customer‘s perspective. <number>
- We can have scrums of scrum of scrum <number>
- Self organized team is left unsupervised so they can enjoy their freedom and do whatever they want <number>
- How to define completion of phase for billing ? How to bill them? Where to define the milestone? Completion of sprint will be too short for billing? <number>
- You don’t let the team make decisions, to allow them to learn by making mistakes and to trust them to get the job done <number>
- Finger pointing to others is not allowed in our culture <number>
- Decorative gift items <number>