Materiais sobre Métodos Ágeis
(→Scrum e Kanban) |
(→Refatoração) |
||
(29 edições intermediárias de um usuário não apresentadas) | |||
Linha 1: | Linha 1: | ||
− | + | = Métodos Ágeis em Geral = | |
+ | |||
+ | * [http://www.agilealliance.org/ Agile Alliance] | ||
+ | |||
+ | == Eventos == | ||
+ | |||
+ | * [http://www.agilebrazil.com/2010/pt/index.html Agile Brazil 2010] | ||
+ | * [http://www.agilebrazil.com/2010/pt/detalhes.html#wbma Workshop Brasileiro de Métodos Ágeis 2010] | ||
+ | |||
+ | |||
+ | == Blog posts == | ||
+ | |||
+ | * http://agileinaflash.blogspot.com/2010/06/only-agile-tools-youll-ever-need.html The only agile tools you'll ever need] | ||
+ | |||
+ | = Scrum e Kanban = | ||
* [http://agilemanagement.net/index.php/Blog/thoughts_on_how_kanban_differs_from_scrum/ THOUGHTS ON HOW KANBAN DIFFERS FROM SCRUM, DAVID J. ANDERSON] | * [http://agilemanagement.net/index.php/Blog/thoughts_on_how_kanban_differs_from_scrum/ THOUGHTS ON HOW KANBAN DIFFERS FROM SCRUM, DAVID J. ANDERSON] | ||
+ | * [http://www.agilitrix.com/2010/06/kanban-is-a-gateway-drug/ Kanban is a Gateway Drug] | ||
+ | |||
+ | |||
+ | = Extreme Programming (XP) = | ||
+ | |||
+ | * [http://www.extremeprogramming.org/ Site Oficial sobre Extreme Programming] | ||
+ | * [http://www.threeriversinstitute.org/ Site do Three Rivers Institute, empresa do Kent Beck, o criador do Extreme Programming] | ||
+ | * [http://tech.groups.yahoo.com/group/extremeprogramming/ Grupo de discussão sobre Extreme Programming] | ||
+ | * [http://www.threeriversinstitute.org/AppreciatingYourWayToXP.htm Appreciating Your Way to XP, Kent Beck] | ||
+ | |||
+ | == Kent Beck == | ||
+ | |||
+ | * [http://twitter.com/KentBeck Kent Beck no Twitter] | ||
+ | * [http://en.wikipedia.org/wiki/Kent_Beck Artigo na Wikipedia sobre Kent Beck] | ||
+ | |||
+ | == Vídeos == | ||
+ | |||
+ | * [http://www.viddler.com/explore/vinicius/videos/2/ Palestra de Vinícius Teles sobre XP] | ||
+ | * [http://vimeo.com/10437623 Palestra de Vinícius Teles sobre XP] | ||
= Test-driven development (TDD) = | = Test-driven development (TDD) = | ||
Linha 16: | Linha 49: | ||
== Scientific papers == | == Scientific papers == | ||
+ | |||
+ | * [http://portal.acm.org/citation.cfm?id=1810295.1810359 A flexible tool suite for change-aware test-driven development of web applications] | ||
== Tutorials == | == Tutorials == | ||
Linha 25: | Linha 60: | ||
* [http://sites.google.com/site/tddproblems/ TDD problems] | * [http://sites.google.com/site/tddproblems/ TDD problems] | ||
− | == JUnit == | + | == Frameworks == |
+ | === JUnit === | ||
* [http://andrefaria.com/2008/08/22/junit-4-em-60-segundos/ JUnit 4 em 60 segundos] | * [http://andrefaria.com/2008/08/22/junit-4-em-60-segundos/ JUnit 4 em 60 segundos] | ||
Linha 32: | Linha 68: | ||
* [http://www.devmedia.com.br/articles/viewcomp.asp?comp=4798 Criando Testes de Unidades com o Junit 4 usando anotações] | * [http://www.devmedia.com.br/articles/viewcomp.asp?comp=4798 Criando Testes de Unidades com o Junit 4 usando anotações] | ||
* [http://junit.sourceforge.net/doc/cookbook/cookbook.htm JUnit Cookbook] | * [http://junit.sourceforge.net/doc/cookbook/cookbook.htm JUnit Cookbook] | ||
+ | |||
+ | === JavaScript === | ||
+ | |||
+ | * [http://www.infoq.com/articles/javascript-tdd JavaScript Test Driven Development with JsUnit and JSMock] | ||
== Some references == | == Some references == | ||
Linha 56: | Linha 96: | ||
R. Glass, “The State of the Practice of Software Engineering”, IEEE Software, p. 21, | R. Glass, “The State of the Practice of Software Engineering”, IEEE Software, p. 21, | ||
Nov-Dic 2003. | Nov-Dic 2003. | ||
+ | |||
+ | == Behaviour-driven development == | ||
+ | |||
+ | Behaviour-Driven Development (BDD) is an evolution in the thinking behind TestDrivenDevelopment and AcceptanceTestDrivenPlanning. | ||
+ | |||
+ | * [http://behaviour-driven.org/ Behaviour-Driven Development] | ||
+ | * [http://wiki.github.com/arnaudbrejeon/cspec/ CSpec : Behavior-driven development in C] | ||
+ | |||
+ | |||
+ | = Pair Programming = | ||
+ | |||
+ | == Scientific papers == | ||
+ | |||
+ | * [http://portal.acm.org/citation.cfm?id=1244776&dl=ACM&coll=ACM&CFID=93725070&CFTOKEN=32138210 Evaluating performances of pair designing in industry] | ||
+ | * [http://portal.acm.org/citation.cfm?id=1062455.1062545&coll=ACM&dl=ACM&CFID=93725070&CFTOKEN=32138210 A multiple case study on the impact of pair programming on product quality] | ||
+ | |||
+ | = Against Agile Methods = | ||
+ | |||
+ | == Blog posts == | ||
+ | |||
+ | * [http://thegreatthree.blogspot.com/2009/03/why-agile-sucks-my-take-on-agile.html Why Agile sucks.. My take on Agile Software Development (ASD)] | ||
+ | * [http://foohack.com/2007/11/agile-scrum-sucks-but-so-do-the-alternatives/ Agile Scrum Sucks (but so do the alternatives)] | ||
+ | * [http://nform.ca/blog/2008/03/why-agile-sucks-most-of-the-ti Why Agile sucks (most of the time)] | ||
+ | * [http://www.softwaremetrics.com/Agile/Agile%20Method%20and%20Other%20Fairy%20Tales.pdf Agile Methods and Other Fairy Tales] | ||
+ | ** Fonte: http://www.softwaremetrics.com/Agile/ | ||
+ | |||
+ | = Refatoração = | ||
+ | |||
+ | |||
+ | |||
+ | * [http://www.refactoring.com/ Refactoring Home Page] | ||
+ | ** [http://books.google.com.br/books?id=1MsETFPD3I0C&dq=refactoring&printsec=frontcover&source=bn&hl=pt-BR&ei=DLQfTIKPOIH98Ab50NmJDA&sa=X&oi=book_result&ct=result&resnum=4&ved=0CDYQ6AEwAw#v=onepage&q&f=false Refactoring, Martin Fowler (Google Books)] | ||
+ | |||
+ | * [http://en.wikipedia.org/wiki/Code_refactoring Code refactoring (Wikipedia)] | ||
+ | * [http://pt.wikipedia.org/wiki/Refatora%C3%A7%C3%A3o Refatoração (Wikipédia)] | ||
+ | |||
+ | * [http://improveit.com.br/xp/praticas/refatoracao Refatoração (ImproveIt)] | ||
+ | |||
+ | == Vídeos == | ||
+ | |||
+ | * [http://agilblog.locaweb.com.br/2008/12/04/refatoracao-refactoring-videos Apresentação sobre Refatoração] | ||
+ | |||
+ | = Assuntos relacionados = | ||
+ | |||
+ | == Source code version control == | ||
+ | |||
+ | * [[GIT]] | ||
+ | |||
+ | == Técnica Pomodoro == | ||
+ | |||
+ | === Artigos relacionados === | ||
+ | |||
+ | * [http://www.nytimes.com/2010/06/07/technology/07brain.html?ref=matt_richtel Hooked on Gadgets, and Paying a Mental Price] | ||
+ | * [http://www.nytimes.com/2010/04/27/world/27powerpoint.html?hp We Have Met the Enemy and He Is PowerPoint] | ||
+ | * [http://www.nytimes.com/2010/06/11/opinion/11Pinker.html?scp=1&sq=mind%20over%20mass%20media&st=cse Mind Over Mass Media] |
Edição atual tal como 11h56min de 28 de junho de 2010
Tabela de conteúdo |
Métodos Ágeis em Geral
Eventos
Blog posts
- http://agileinaflash.blogspot.com/2010/06/only-agile-tools-youll-ever-need.html The only agile tools you'll ever need]
Scrum e Kanban
Extreme Programming (XP)
- Site Oficial sobre Extreme Programming
- Site do Three Rivers Institute, empresa do Kent Beck, o criador do Extreme Programming
- Grupo de discussão sobre Extreme Programming
- Appreciating Your Way to XP, Kent Beck
Kent Beck
Vídeos
Test-driven development (TDD)
Wikipedia
Blog posts
Books
Scientific papers
Tutorials
Sites
Frameworks
JUnit
- JUnit 4 em 60 segundos
- JUnit 4 you
- Suítes de testes no JUnit 4
- Criando Testes de Unidades com o Junit 4 usando anotações
- JUnit Cookbook
JavaScript
Some references
C. Larman and V. Basili, “A History of Iterative and Incremental Development”, IEEE Computer, 36(6), pp. 47-56, June 2003.
C. Desai, D. Janzen, and K. Savage, “A Survey of Evidence for Test-Driven Development in Academia”, ACM SIGCSE Bulletin, 40(2), pp. 97-101, June 2008.
B. George, L. Williams, “An Initial Investigation of Test Driven Development in Industry”, Proceedings of the 2003 ACM symposium on Applied computing, pp. 1135-1139, 2003.
K. Beck, “Test Driven Development: By Example”, Addison Wesley, November 2002.
T. Bhat and N. Nagappan, “Evaluating the Ecacy of Test-Driven Development: Industrial Case Studies”, Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering, pp. 356-363, 2006.
G. Canfora, A. Cimitile, F. Garcia, M. Piattini, C. A.Visaggio, “Evaluating Advantages of Test Driven Development: a Controlled Experiment with Professionals”, Proceedings Professionals of the 2006 ACM/IEEE international symposium on Empirical software engineering, pp. 364-371, 2006.
R. Glass, “The State of the Practice of Software Engineering”, IEEE Software, p. 21, Nov-Dic 2003.
Behaviour-driven development
Behaviour-Driven Development (BDD) is an evolution in the thinking behind TestDrivenDevelopment and AcceptanceTestDrivenPlanning.
Pair Programming
Scientific papers
- Evaluating performances of pair designing in industry
- A multiple case study on the impact of pair programming on product quality
Against Agile Methods
Blog posts
- Why Agile sucks.. My take on Agile Software Development (ASD)
- Agile Scrum Sucks (but so do the alternatives)
- Why Agile sucks (most of the time)
- Agile Methods and Other Fairy Tales