InfoQ Homepage Agile Techniques Content on InfoQ
-
A Good Velocity
Buddha Buck recently asked the Extreme Programming list if there were a velocity range that could be considered 'good' for a team of about seven people doing two-week iterations. He felt that a velocity of eight or below indicated that the team's stories might be too big. The resulting discussion provided some answers to the question, and the questions behind the question.
-
Feature Injection Comics
Chris Matts, well known in the Agile community for his work in bringing option theory to software development, has been writing about feature injection in a comic-book format on the Agile Journal. He explains how, by changing the way information flows through your software development process, you can significantly improve performance.
-
Article: Where To Now With Build Automation
Most developers nowadays are familiar with the basic tenets of Continuous Integration, but arguably only a small proportion of these are fully benefiting from an optimized CI set up. This article, by John Smart of Atlassian, discusses Continuous Integration practices that can take CI beyond merely being a glorified cron job and make it an effective, productivity-enhancing hub for development.
-
Interview: Jeff Patton on Embracing Uncertainty
In this interview with Jeff Patton at Agile 2008, he talks about three strategies that can help product owners do their job more effectively by embracing the inherent uncertainty in all software development. Namely they are understanding the ultimate goals of the project, delaying decisions until the last responsible moment, and scaling up by building quality.
-
Comparing Kanban To Scrum
Kanban has been gaining serious interest as a valid approach to implementing agile for your development organization. As such, many people are asking the question "how does Kanban compare to Scrum?". Henrik Kniberg has taken a stab at answering this question
-
Presentation: Born to Cycle
Agile development is not about doing a set of practices, it's about a way of "being," it's about learning. How is this learning accomplished? By taking brief pauses after small experiments, even large problems can be solved. In a recent Harvard Business Review interview of Toyota's president, he observed, "...when 70 years of very small improvements accumulate, they become a revolution."
-
Presentation: Agile Mashups
It is rare to come across a team that are following an agile software method such as Scrum or XP by the book. Most teams create their own "mashup" of agile practices to suit their unique situation. This talk highlights what's on offer in the different agile methods, where different agile practices add value and how to go about blending them into your current approach.
-
Recommended Lean Books
Are you interested in reading up on Lean theory? The latest discussion on the leanagile Yahoo! group lists many good reads and even a work-in-progress.
-
Presentation: Agility - Possibilities at a Personal Level
Linda Rising talks about the industrial revolution, caffeine, agility and happiness at QCon 2008 in San Francisco: Some observers of historical trends have suggested that the Industrial Revolution could not have happened without coffee and tea. Control of working and waking is what the Industrial Age was all about. Is it time for a truly agile approach to how we work and live our lives?
-
Do Stand-ups Stand Up for Larger Teams?
The daily stand-up meeting helps the team members make a commitment to each other about what they aim to achieve in the day and identify obstacles to progress, if any. However, many Agilists believe that the conventional stand-ups break down quickly as the team size increases.
-
Virtual Panel: Is the Backlog a Vital Artifact and Practice or Waste?
Mary Poppendieck, Ron Jeffries, Jeff Patton, David West, Steve Freeman, and Jason Yip give us their take on backlogs and their importance to successful Agile teams.
-
Lean 'Standard Work' Applied to Software Development
One component of the Toyota Production System is the concept of standard (or standardized) work. A recent post on the Kanban Development list asked if this concept carries over when TPS and lean are applied to software projects. Despite the fact that software development is not manufacturing, respondents did find value in applying the 'standard work' concept to development.
-
What Practices Make Up YOUR Agile Development?
'Agile' is an umbrella term. As the community matures, we are going beyond specific methodologies towards each team and/or organization having a tailored set of practices. Jurgen Appelo is running a survey that could give us insight into the current state of practice.
-
Transparency: A Great Leap Forward or Exposed Artery?
Agile propagandists make great claims about the advantages of being transparent about the state of their projects. They claim that this how mature relationships work and that "Honesty is the best policy". But is this true? Many of us work in dysfunctional organizations where honesty is the best way to get cheated. Surely Transparency is just not pragmatic?
-
Does a Distributed Agile Team Need Heroes?
This month's issue of the Agile Journal has a case study that suggests that if you do not have a technical wizard on your team, then distributed/offshore Agile development will fail. This goes against the grain of self-organizing teams and getting away from heroes of the traditional Agile mindset.