InfoQ Homepage Agile Content on InfoQ
-
Eclipse "Callisto" an Agile Success Story
Today will mark the "Callisto" release of 10 Eclipse toolsets simultaneously, remarkable in that it provides a synchronized set of releases to facilitate implementation of Eclipse for developers building their own tools and applications on top of it. A large, complex and risky undertaking, Callisto was reportedly delivered by open source developers using Agile methods.
-
Getting Agile with Eclipse Continuous Integration
The Eclipse "Callisto" release includes agility-enhancing features, including a new version of the testing tools developed in the "TPTP" project. In their online presentation, project committers Scott E. Schneider and Joe Toomey say that by using TPTP in the Continuous Integration cycle developers gain more powerful test types, better/more extensible reporting, and easy platform coverage.
-
An Experiment in Clear Communication
Rather than keeping customers and developers apart (to avoid "misunderstandings"), Agilists intentionally bring them together. Communication tends to improve faster than one might expect, and soon everyone is interacting constructively. But in a team or between teams, there is always room for improvement: Cory Foy blogged what happened when he tried a new idea in "The Dreyfus Model Experiment".
-
InfoQ Book Review: Agile Java Development with Spring, Hibernate and Eclipse
Matt Morton asked the question "Can Java be as Agile as the Dynamics (Ruby, Python, Groovy)?" and went to Anil Hemrajani's book to find out. He found a readable, useful book, and helps idenfity the right audience for this book.
-
Test Driven Development Has Become the Norm
In his June article "Test-driven development is the combination of test first development and refactoring" on Dr. Dobbs Portal, Scott Ambler cuts to the chase, as usual: TDD has become the norm. So, do you want to implement it now, or wait for competetive pressure to make it necessary? This article lays out the reasons to consider it, and debunks some widespread misconceptions.
-
Examining the Declaration of Interdependence
The Declaration of Interdependence emerged in 2004, when a group of experts met to discuss ways to extend the Agile Manifesto to non-software products and management. In this month's edition of Better Software Magazine, Alistair Cockburn details the DOI's six principles and how they can benefit any enterprise.
-
Personal Retrospective: How Did I Do?
Nynke Andering gives us an inside view of a process of self-retrospective, which she uses after a consulting engagement. She shares not only her questions, but her answers, in four categories: Collaboration, Learning, Consulting, Responsibility.
-
How Should We Teach Design Patterns?
Design patterns are a key to productive "refactoring", an Agile practice that keeps applications stable and maintainable, and a central aspect of Agile methodologies like XP. The 5th "Killer Examples" for Design Patterns and Objects workshop will take place at OOPSLA2006 in October, and will be looking at how to teach design patterns - apparently existing materials can be challenging for novices.
-
New Testing Tools Released
June has seen the release of CoView 2.0, an Eclipse plugin to assist with test coverage; Haven 1.2, for automated acceptance testing; and the new Pulse continuous integration server.
-
"Agile Practice" Patterns Wiki is Up
At XP2006, Amr Elssamadisy announced a new wiki site for collecting Agile Practice Patterns. Well, it's up and ready to go, already loaded with patterns from ChiliPlop 2006 and XP 2006 conferences.
-
Value-Driven Planning and Metrics
A stable Agile team can cost roughly the same each week, but value delivered changes over time. Agile planning takes into account the customer's view of value, allowing the team to deliver the most important business value right away, and allowing their customer to halt the work when cost exceeds value delivered. Why aren't all teams measuring Business Value? Dan Rawsthorne shows one way to do it.
-
Health Check: Has Your Team Got Rhythm?
Agile work keeps things simple by putting in place some basic patterns. Sometimes, when problems arise within the process, complex solutions can be averted by simply re-establishing a rhythm in the cycle of releases, iterations, days, stories/features. Agile Journal, in their Metrics edition, published three articles which mention the importance of rhythm as a diagnostic.
-
19 Pitfalls of Technical Leadership
Hacknot's list of Great Mistakes in Technical Leadership, while not particularly intended for an Agile audience, contains some sage advice - good leadership is not restricted to Agile teams. As always, Agile teams still need to balance advice from traditional sources against Agile values and principles.
-
Minimalism: Creating Manuals People Can Use
Yes, documentation is not "working software". That being said, a certain amount of documentation is often necessary. But where do we start, to lighten up our documentation processes? JoAnn Hackos' workshop on July 11/12 teaches a disiplined minimalism, allowing teams to leverage structured writing, etc. to create just enough documentation - the right documentation. Almost sounds agile :-)
-
FIT Acceptance Testing Primer
Do you think automated user acceptance testing is a cool idea, but impossible or not worth doing? Have you been bogged down by the traditional record/script/replay approaches and unable to automate until the code is complete? This article will show you how the Framework for Integrated Test (Fit) makes it easy to overcome these challenges and practice test-first design from the user perspective.