Agile
Seu SlideShare está sendo baixado.
×
Confira estes a seguir
Mais Conteúdo rRelacionado
Diapositivos para si (20)
Semelhante a Ten Pitfalls in the Agile Journey (20)
Mais recentes (20)
Ten Pitfalls in the Agile Journey
- 1. Ten pitfalls on the Agile Journey Gabriel Gavasso Project Manager and Business Analyst ASEAN expansion ggavasso@thoughtworks.com Mar 2014 Created in collaboration with Preethi Madhu and Umar Akhter. This presentation is licensed under Creative Commons CC BY-SA 4.0.
- 2. Gabriel Gavasso 9+ formally employed in IT Project Manager, Business Analyst, Trainer, Coach Worked in Brazil, USA and Singapore
- 3. overloaded release cycles 1
- 4. New requirement comes in something should go out1
- 5. certifcations are ALL you need to change the game 2
- 6. Practice and experience across various projects. Failing and learning. 2
- 7. Engineering Practices are not for me 3
- 8. Engineering Practices are not for me 3 Have a holistic approach across process & engineering
- 9. anything can change anytime 4
- 10. Process of negotiation is involved for change.4
- 11. Agile means no documentation 5
- 12. Doc when needed and to the extent needed. Living docs helps! 5
- 13. empowered teams means indiscipline 6
- 14. Teams still require guidance and support, sometimes oversight 6
- 15. never know when it will be over 7
- 16. Adaptive Planning 7
- 17. 8 you Scrum so you're Agile
- 18. There is no “one size fts all” here. What is your own favor? 8
- 19. Agile means micromanagement 9
- 20. The earlier to know, the cheaper and the better chances to fx are9
- 21. always streched on projects
- 22. always streched on projects Sustainable pace and self-organizing teams
- 23. New requirement comes in something should go out too New requirement comes in something should go out New requirement comes in something should go out too Practice and experience across various projects. Failing and learning. New requirement comes in something should go out too Have a holistic approach across process & engineering New requirement comes in something should go out too Process of negotiation is involved for change. New requirement comes in something should go out too Doc when needed and to the extent needed. Living docs helps! 1 3 2 4 5 New requirement comes in something should go out too Teams still require guidance and support, sometimes oversight New requirement comes in something should go out too Adaptive Planning New requirement comes in something should go out too There is no “one size fts all” here. What is your own favor? New requirement comes in something should go out too The earlier to know, the cheaper and the better chances to fx are New requirement comes in something should go out too Sustainable pace and self-organizing teams 6 8 7 9 01
- 24. 26 Thank you! Questions? Comments? (all pictures are license-free or licensed on Creative Commons at time of use – March 24th , 2014) [1] http://www.fickr.com/photos/tokyogoat/2936378536 [2] http://www.fickr.com/photos/irvotheturbo/3973939419 [4] http://good-wallpapers.com/misc/12188 [5] http://www.fickr.com/photos/dfucs/2715460622 [6] http://www.fickr.com/photos/anthonybaker/196630774 [7] http://www.fickr.com/photos/racecarphotos/535337722 [8] http://www.fickr.com/photos/royskeane/413103429 [9] http://www.fickr.com/photos/andercismo/2349098787 [10] http://commons.wikimedia.org/wiki/File:Open_24_Hrs_-_Money_Change_ %284039347263%29.jpg Gabriel Gavasso Project Manager and Business Analyst ASEAN expansion ggavasso@thoughtworks.com
