InfoQ Homepage Agile Techniques Content on InfoQ
-
Introducing the ALT.NET Podcast
InfoQ learned about a new podcast recently called the ALT.NET Podcast. This podcast focusing on the community of developers brought together who represent what is ALT.NET. Folks should remember the ALT.NET term coined by David Laribee.
-
The Official RubySpec Website and Its Google Summer of Code Students
The RubySpec project aims to create a complete and executable specification for the Ruby language and recently got its own website. We also talked to two GSoC students who will help improve these specifications.
-
Presentation: Agile Project Lifecycle in User Stories and Release Planning
In this presentation recorded during QCon London 2007, Rachel Davies, director of Agile Alliance, talks about the Agile development cycle starting with user stories and planning the releases.
-
What Makes a Good Stand Up Meeting?
One of the most simple and yet most talked-about agile practices is the Daily Stand Up Meeting (a.k.a. Scrum). The most recent round of discussions around the subject is occurring right now on the scrumdevelopment Yahoo! group. This discussion has resulted in suggestions about what is important about a Daily Stand Up, how to perform one correctly, and several links to articles on the subject.
-
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".
-
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.
-
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.
-
Microsoft Embraces Dependency Injection in the Framework
Microsoft's new Application Framework Core team has started to embrace techniques Naming and Activation Services, Dependency Injection, and Duck Typing in .NET's core frameworks.
-
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.
-
Lessons for the Agile Community from 8aweek
InfoQ recently had the opportunity to ask 8aweek co-founders Dave Fowler and Zachary Garbow some questions about how they connect with users, prioritize work, and get things done.
-
Agile Version Control for Multi-Team Development
Many agree that the minimum set of Agile practices includes disciplined version control. In particular, when several development teams work in the same codebase, to ensure there's a clean, releasable version at the end of every iteration, they need a plan. Henrik Kniberg's proven scheme is a useful guide for teams. This detailed paper includes the entire method and even a cheatsheet.
-
First (Forgotten?) Rule Of The Retrospective: Follow Through
Even the very greenest of agile teams clearly recognize the word 'Retrospective'. But, alas, it is often overlooked that a retrospective may be a wasted effort if not used to initiate an actual improvement that the team follows through on. Jim Shore gives advice on how to make the most of your retrospective and reminds us of the activity's ultimate place in the agile heartbeat.
-
Do Extreme Programming Folks Care about Scrum?
Scrum and XP are considered to be natural allies and both are widely adopted in the industry. However, there seem to be some dark secrets behind the happy facade of using them together. A massive discussion on the Extreme Programming group tries to answer if Scrum is alienating extreme programming folks and whether Scrum would be as effective without XP.
-
InfoQ Video: Practices of an Agile Developer
At NFJS Venkat Subramaniam, co-author with Andy Hunt of "Practices of an Agile Developer," shared his pragmatic approach to some of the important technical and non-technical factors contributing to project success, including: coding, developer attitude, debugging, mentoring and feedback.