Aidas pasilis. Oh my Agile!
•Descargar como PPTX, PDF•
0 recomendaciones•476 vistas
Over years of work I’ve found that often people know a lot of theory and stick to cliché terms, but don’t necessarily know what it actually means in practice. So in this session I will look at practical side of delivery with a grain of humour - Agile theory versus practice, failure versus success, will talk about different things that make teams tick and some, sometimes even small things, that can change the outcome of the project.
Recomendados
Recomendados
Más contenido relacionado
Similar a Aidas pasilis. Oh my Agile!
Similar a Aidas pasilis. Oh my Agile! (20)
Más de Agile Lietuva
Más de Agile Lietuva (20)
Último
Último (20)
Aidas pasilis. Oh my Agile!
- 1. Oh my AGILE! Aidas Pasilis 09/10/2014
- 2. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
- 3. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
- 12. Fu©k1ng developers (a.k.a. it works on my pc…)
- 14. …collaboration over contract negotiation Responding to change over following a plan ITIL over Agile Careful planning, processes and tools, comprehensive documentation and contract negotiation
- 15. DevOps is a concept of solving IT challenges by means of communication, collaboration, and integration between software developers and information technology (IT) operations personnel.
- 19. Metaphors
- 20. White boards
- 26. There will always be walls…
- 29. Expanding your own circle of influence 5 1 2 1
- 30. Expanding your own circle of influence 5 1 2 1
- 31. Expanding your own circle of influence 5 1 2 2
- 32. Expanding your own circle of influence 5 1 2 4
- 33. Expanding your own circle of influence 5 1 2 4
- 34. Is two weeks sprint long?
- 35. Communication and associative thinking
- 36. Fluffy
- 37. Fluffy Julie
- 38. Fluffy Julie
- 39. Fluffy Julie Tom
- 40. Fluffy Julie Tom
- 41. Fluffy Julie Tom
- 43. Is two weeks sprint long?
- 46. Tools of Communication • Empathy • Metaphors • Circle of influence • Creative thinking
- 48. Tribes, our history and our heroes
Notas del editor
- Brick by brick, mistake by mistake. With careful planning and good intentions… Someone needed to control the chaos, creativity, inspiration, protect the investment
- Tribe, with it’s own traditions, that would not easily accept outsiders and would just trade goods – “tell us what you need and we’ll provide it”. And who look ridiculous and unnatural in costumes and most of the time don’t even know how to communicate with other tribes. But things change and when they change, but you don’t, you go extinct or get eliminated
- And here came the breaking of the great wall… Agile worked because of initiative and talented developers (yes – there are untalented developers) who weren’t afraid of changing and breaking down the walls. Who saw flaws of the wall and found ways to break it without endangering
- And here came the age of Agile and Scrum and Kanban and XP and many others… We may not have broken the wall completely, but we’ve definitely created a huge hole. There are governmental and some other more conservative companies still are trying to hold on to their tribal regimes
- Iteration by iteration,
- Remember the brick wall that was build so carefully and with so much planning in mind
- Because while developers were saying…. Infrastructure where saying processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
- DevOps is a concept of solving IT challenges by means of communication, collaboration, and integration between software developers and information technology (IT) operations personnel.
- Empathy Designers + engineers + empathy = greatness IMIS – doctors for doctors
- What was good, what was bad is same as gathering feedback about people with the classic 3 questions Fun fact – despite the fact that we know that we do retros for continuously and iteratively improve our ways Go for questions that give unique personal reflection on the subject e.g. if you had to compare our last deployment with a notable event in human history, what would it be and why Use brainstorming and other techniques
- What was good, what was bad is same as gathering feedback about people with the classic 3 questions Fun fact – despite the fact that we know that we do retros for continuously and iteratively improve our ways Go for questions that give unique personal reflection on the subject e.g. if you had to compare our last deployment with a notable event in human history, what would it be and why Use brainstorming and other techniques Sprint Names – The bucket list, Now you see me
- Circle of Influence when talking about team… or the origins of DevOps
- Example with expectations vs specifications