InfoQ Homepage Agile Content on InfoQ
-
The Personal Retrospective – Improving Your "Wetware"
Andy Hunt's interview last month talks about his progression from pragmatic programmer to Agile development to his latest interest – Pragmatic Wetware. "Wetware is the stuff in your head. That's the thing between your ears that's really where all the action is – that's where all the software development actually takes place."
-
Presentation: Agile Project Management: Lessons Learned at Google
In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum. He tells how Google started with no engineering management, then gradually introduced Scrum without spoiling the development culture formed over the years.
-
Rewards to Improve Team Habits?
Sometimes teams have trouble starting new habits: writing unit tests, fix compiler warnings, not breaking the build. How do we help the team change these habits? Clint Shank designed a game to help people transition.
-
'State of Agile' Survey Open for Participation
VersionOne, a maker of agile project management tools, has announced that the third annual 'State of Agile Development' survey is open for participation. The online survey is intended to gauge the value of agile development practices in the field. Results will be announced on August 4th, at the Agile 2008 conference in Toronto.
-
The Complexity Around Simplicity
Almost all Agile techniques focus on simplicity. Understanding simplicity could itself be a complex task. Many Agile community members believe that simplicity is often misunderstood and this often results in unwanted complexity.
-
TDD Opinion: Quality Is a Function of Thought and Reflection, Not Bug Prevention
In a recent post, Michael Feathers argues against the widely held idea that unit testing, by itself, improves code quality. Michael talks about unit testing, integration tests, TDD and Clean Room Software Development, concluding that code quality is a function of thought and reflection, not bug prevention.
-
Voting Someone Off the Island on an Agile Team
On Agile teams there is a definite possibility of having a team member who is not a good fit. Members of the Agile community discuss the reasons and possible ways of voting someone off the island.
-
My "Unit Test" Aint Your "Unit Test"
Mike Hill, well-known XP contributor, came forth to make a few interesting assertions about the misunderstanding often surrounding how a TDD "unit test" differs from the "unit test" of traditional lore, and how he uses the term 'microtesting' to clear the air for new TDD'ers.
-
Subversion 1.5 released
Subversion, a mature open source version control system used by many open source projects, has just released version 1.5. New features include: merge tracking, sparse checkouts, and conflict resolution in the command line client.
-
Agile Smells: Don't Let This Happen To You!
Mark Levison wrote an interesting blog summarizing some of the work that has been done to catalog Agile smells. We summarize some of those smells and point to other intersting work that documents the Agile community's experience in adoption.
-
New User Story Format Emphasizes Business Value
User stories, a common format for capturing agile requirements, could be more focused on business value. A traditional format for stating a user story is: "As a <type of user> I want <some functionality> so that <some benefit>." A value-centric replacement would be: "In order to <achieve some value>, as a <type of user>, I want <some functionality>."
-
Agile Practices with the Highest Return on Investment
Return on Investment is a critical factor for decision making pertaining to following a particular software development practice. The post summarizes the ROI benefits of Agile and the inexpensive practices which lead to highest return on investment.
-
FIT/Fitnesse Fixture Gallery 2.0 Released
Gojko's Fixture Gallery is a cookbook for FIT/Fitnesse fixtures and version 2.0 has been released with Java, C# and Python code samples.
-
Agile Business Intelligence
Large centrally designed BI systems often don't meet the expectations of their end users. In this article at Cutter IT journal Scott Ambler has written about using Agile methods to help meet the user's expectations and deliver business value quickly.
-
Do Specialists Outperform Generalists on an Agile Team?
An Agile team is mostly a cross functional team comprising of generalists and specialists. Jurgen Appelo, challenges this concept and suggests that having just specialists on an Agile team adds more value. The post tries to correlate various view points on team composition by other members of the Agile community.