InfoQ Homepage Agile Techniques Content on InfoQ
-
Presentation: A Kanban System for Software Engineering
David Anderson presents a brief history of the kanban system through case study reports from teams at Microsoft and Corbis. Kanban acts to limit work-in-progress and focus the team on achieving a continuous flow of value to the customer and innovates on accepted agile management practices by providing an iteration-less process with a regular release cadence.
-
Models of Apprenticeship
Uncle Bob Martin recently wrote about his experience with apprentices and what he considers key to progressing from apprentice to journeyman. He describes two hypothetical apprentices: Sam, a developer who has apprenticed with the same master and had the same year fifteen years in a row. Jasmine has changed jobs (and therefore masters) a number of times - growing her skills along the way.
-
Book Excerpt: Agile Testing
InfoQ brings you an excerpt from Agile Testing, a book is for testers on an agile team, test and quality assurance managers transitioning to agile development, and agile teams learning how to approach testing.
-
Story Mapping Gives Context to User Stories
The Scrum notion of 'backlog' is a single, prioritized list of user stories for the team to implement. This works well for organizing what the team should work on in the near term, e.g. during sprint planning. At the Orlando Scrum Gathering, Jeff Patton described story mapping. This is a way of organizing stories that provides richer context and can help with release planning.
-
Interview: Tim Bray on the Future of the Web
In this interview made during QCon SF 2008, Tim Bray talks about why he is not convinced with the buzz surrounding Rich Internet Applications and shares his ideas on Cloud Computing. He also expresses his opinion regarding the debate REST vs. WS-* and the future directions web technologies will be taking.
-
How Do You Get a Hyper-Productive Team?
Some of us have been lucky enough to be on hyper-productive teams, others think this is a myth. Joanna Zweig and Cesar Idrovo have been discussing Group Coherence - a search for hyper productivity with some insightful information for everyone trying to produce a hyper-productive team. Their research gives a possible model of how and why some Agile teams excel and others do not.
-
Annotated Burn-Down Charts Help During Retrospectives
A sprint burn-down chart tracks the size of the sprint backlog over the course of the sprint. During the sprint retrospective, the burn-down chart can provide valuable data about how the sprint went. Mike Sutton uses annotations to capture more data on the burn-down chart, making it even more useful during the retrospective.
-
Software Craftsmanship Manifesto: A Call to Arms
A movement to promote Software Craftsmanship has been brewing for a few years. Since Agile 2008 last year they found a focal point with Uncle Bob Martin's claim that the Agile Manifesto needed amending with a new value: "Software Craftsmanship over Crap". Recently a group has created the Software Craftmanship Manifesto.
-
Article: Successfully Adopting Pair Programming
Jay Fields presents several concrete strategies to go from "I think pair programming is a good idea" to "our team is successfully practicing pair programming and loving it!" He covers everything from pairing stations (the physical layout of your office space), to coaching tips, to common mistakes that those new to pair programming make.
-
RFactor: Ruby Refactoring Support for Text Editors
RFactor is a Ruby refactoring tool that aims to bring automated refactoring support to text editors. We talked to its developer Fabio Kung to learn how it works and what's planned for the future.
-
Story Driven Development Recipes with Cucumber
Behavior Driven Development's (BDD) popularity cannot be denied. By simplifying DSL writing, Ruby allowed the birth of many BDD frameworks. Cucumber is one of them and can also be used to test Java, .NET and Flex and more.
-
Empirical Studies Show Test Driven Development Improves Quality
A paper first published in the Empirical Software Engineering journal reports: "TDD seems to be applicable in various domains and can significantly reduce the defect density of developed software without significant productivity reduction of the development team." The study compared 4 projects, at Microsoft and IBM that used TDD with similar projects that did not use TDD.
-
Agile Is a Culture Not a Process
Jeff Patton explains why thinking of agile as culture and not just process explains resistance and difficulty in teaching and learning the approach. Furthermore he suggests that culture generates process, and therefore we should focus on culture first before process and techniques
-
Interview with Brian Marick at Agile 2008
Brian Marick discusses what he means by micro-scale-retro-futurist-anachro-syndicalism and why we should go back to the roots of Agile. He talks about what he thinks were the mistakes in the Agile Manifesto, how it has lead to the state of the Agile community today, and how we can build better systems by making them so that they are much more easily tested.
-
Spolsky vs Uncle Bob
The last few weeks, a public dispute has been going on between Joel Spolsky and Robert C Martin (Uncle Bob) about Test-Driven Development and about the SOLID principles of OO design. Here is a summary and review of the match.