Why agile?
•Download as KEY, PDF•
11 likes•1,119 views
The document provides dates from March 2010 to June 2011, suggesting it contains information over a period of time spanning more than a year. No other contextual details are available within the limited information given.
Recommended
More Related Content
More from Henrique Imbertti Jr.
More from Henrique Imbertti Jr. (8)
Recently uploaded
Recently uploaded (20)
Why agile?
- 22. March 2010
- 23. June 2011
Editor's Notes
- Intro: my name is Henrique, I work for Y! as a Agile/Lean Coach... bla bla bla\n
- \n
- Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.\nI will not explain scrum or XP, they are simple... #lean is a destination, #kanban is a means to get there. @agilemanager\n
- Lots of people had negative experiences with agile. \nMainly due to a wrong or weak adoption of the process. \n
- Trendy methods... \nIt depends on the context. Making the most of them!\nAgile development is no silver bullet, but it is useful. Focus on principles and values!!!\n
- http://www.ultrasaurus.com/sarahblog/2010/04/beyond-agile-development/\nhttp://swik.net/Eclipse/Planet+Eclipse/Julius+Shaw:+Kent+Beck+Revises+the+Agile+Manifesto+(for+startups)/d056n\nA team lives the principles and values!\nAgile = Admission that we don’t know the solution.\nLean Startup = Admission that we don’t know the problem. \n
- 1) we\n2) without coding\n3) there is no customer yet\n4) you need to build momentum\n
- \n
- Talking about teams... why a team exists?\n
- \n
- Create a team mission & values!\n
- Still talking about teams...\n
- \n
- \n
- \n
- \n
- \n
- \n
- I know that baby.com.br is going to do a great job!\nSustainable pace\n
- Every delivery is a MVP (minimum viable product) \nValidate hypothesis & delight customers! :) \n
- Our team at Y! got attention from the company because we deliver earlier and often!\n
- \n
- Deixar o processo evoluir identificando e retirando um gargalo após o outro (baby steps).\nKanban foi utilizado para mudar incrementalmente um processo que já estava em funcionamento (de forma que o processo possa se adequar ao contexto do time). David Anderson: a’ a’’ a’’’ b\n
- Time mais atento para as filas/gargalos. Menos falhas.\nCFD por iteração, fica legal também plotar em um período de tempo maior.\nEstes são de sucesso, fazer de fracasso? Fazer um de stories tb?\n
- Começamos a trazer métricas para as retrospectivas para evoluir continuamente.\nIdentificando filas e gargalos. Outras métricas tb?\n
- Cada daily meeting é uma oportunidade para fazer uma retrospectiva.\nMeça o sistema, faça retrospectivas periódicas e evolua continuamente.\n
- Our main focus as an organization is to delight customers!\n
- \n
- \n