Materiais sobre Métodos Ágeis
(→Source code version control) |
(→Scrum e Kanban) |
||
| Linha 3: | Linha 3: | ||
* [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] | * [http://www.agilitrix.com/2010/06/kanban-is-a-gateway-drug/ Kanban is a Gateway Drug] | ||
| + | |||
| + | |||
| + | = Extreme Programming (XP) = | ||
| + | |||
| + | * http://www.extremeprogramming.org/ | ||
= Test-driven development (TDD) = | = Test-driven development (TDD) = | ||
Edição de 10h41min de 21 de junho de 2010
Tabela de conteúdo |
Scrum e Kanban
Extreme Programming (XP)
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
