InfoQ Homepage Agile Content on InfoQ
-
How Long Should You Sprint For?
What factors influence the length of your sprint? When you're trying to pick a length, between two days and six weeks, what factors should you take into consideration? One coach has taken a stab at identifying shortening and lengthening factors.
-
Interview: James Shore on “The Art of Agile Development”
In this interview taken by InfoQ's Deborah Hartmann during the Agile 2007 conference, James Shore, a prominent figure of the Agile community, talks about the book "The Art of Agile Development".
-
Adopting Simple Design
A discussion about simple design is taking place on the extremeprogramming Yahoo! group that has already resulted in several useful recommendations. The discussion started off with a request for references concerning incremental design and quickly morphed into one about successfully adopting incremental design.
-
Integrating Testers on to the Agile Team
What is the role of testers on an Agile team? What is their day to day experience like? What lessons have they learned
-
What Might Happen if You Asked a Powerful Question?
Too often leaders, pressed for time, throw the easiest question at a team. But a moment's reflection, followed by a wise open-ended question can generate new possibilities when a team is stuck. This centuries-old educational technique, sometimes called "Powerful Questions," is a great tool for all team members, to transform "stuck" situations into learning opportunities.
-
Article: Distributed Version Control Systems - a guide
Since Linus Torvalds presentation at Google about git in May 2007, the adoption and interest for Distributed Version Control Systems has been constantly rising. In this article, Sebastien Auvray introduces the concept of Distributed Version Control, see when to use it, why it may be better than what you're currently using, and have a look at three actors in the area: git, Mercurial and Bazaar.
-
Seniority, Respect, Authority and an Agile Team
Senior members, who have been working in traditional teams, can face issues related to respect and authority when they come to an Agile team. An interesting discussion on Scrum Development group and Agile India group tries to uncover answers that Agile might have for the situation.
-
Interview: Segundo Velasquez and Agile as Seen Through the Customer's Eyes
In an interview taken during the Agile 2007 conference, Deborah Hartmann interviewed Segundo Velasquez, co-founder of Mano a Mano Medical Resources, about his experience as customer with an Agile team during the initial phase of software design of a product.
-
Are there weaknesses with Collective Code Ownership?
The Agile development community has been practicing Collective Code Ownership for long enough now that we had enough time to find some of the faults.
-
Why Traditional Test-Automation Tools Stifle Agility
In recent times, much excitement has circulated about the direction of "next generation functional testing" tools. Alas, many agile organizations still struggle to make their traditional record-and-playback automated testing tools work for them. Elisabeth Hendrickson, aka "test Obsessed", tells them why to stop.
-
Article: Software Development Lessons Learned from Poker
There is no silver bullet. We know it, but don't act like it. Your language, tool or process is better, right? In this article, Jay Fields says: "It depends". The right choices varies with context, people, and more. This article touches upon how a lot of things must impact a choice; learning culture, skill levels, teamwork, incomplete information, metrics - and context.
-
Does Sustainable Pace mean a 40 hour week?
Sustainable Pace is a well known XP practice however, different people relate to it in different ways. Could an Agile team increase its sustainable pace by working longer? An interesting discussion on the Scrum Development group tries to debate the correlation between the number of work hours per week and sustainable pace.
-
Presentation: David Hussman on Automating Business Value with FIT and Fitnesse
In this presentation, David Hussman, founder of DevJam, discusses about user stories, the origin and authoring of story tests, focusing on how FIT and Fitnesse (FIT living within a Wiki) can be used to automate acceptance tests.
-
Does Your Team Have a Mission Statement?
Is your team juggling conflicting requests? Is your Product Owner struggling to decide which customer's to serve and which to ignore for now? Does it seem that everyone has a different agenda? Perhaps you need a mission statement
-
Impediments To Your Value-Stream
Scrum defines an impediment as "anything keeping the team from being more productive" and clearly stresses that teams establish means to remove them as continuously as possible. Joe Little proposes an impediment's scope may be better established as being anything keeping the organization from delivering value.