InfoQ Homepage Agile Content on InfoQ
-
Pair Programming vs. Code Review
Pair programming and code review are each practices that improve the quality of software, as well as promote knowledge sharing. When the agile vs. lean, XP vs. Scrum, and vi vs. Emacs debates get slow, developers have been known to debate the merits of pair programming vs. code review. Theodore Nguyen-Cao described code reviewers as chickens, and paired programmers as pigs.
-
Presentation: Kent Beck: Trends in Agile Development
In this presentation, Kent Beck, the father of eXtreme Programming, shows the synergies between business and Agile development. The reason Agile is becoming more popular every day is because it responds to the business needs as they evolve.
-
Presentation: Testing is Overrated
In this talk from RubyFringe, Luke Francl asks: is developer-driven testing really the best way to find software defects? Or is the emphasis on testing and test coverage barking up the wrong tree?
-
First Kanban Conference
First annual Lean Kanban Process and Practices will be held in Miami, Florida, May 6-8th and featuring keynotes from Dean Leffingwell, Alan Shalloway and David Anderson. The other speakers include most of the players in Kanban movement (Corey Ladas, Karl Scotland, Eric Landes et al.).
-
Agile For Embedded Systems
Some might say that agile development and embedded software (ie. "software supporting a hardware device") do not mix well. Mark Levison has taken some time to assemble and writeup a resource reference of people, experiences, and advice that help to show otherwise.
-
Over-Commitment Versus Over-Delivery
A major goal of sprint planning is to make a commitment to what is intended to be delivered by the end of the sprint. However, many teams either over-commit or over-deliver. Both situations are considered as smells and lead to lack of predictability along with other related pitfalls. The team is required to walk a fine line between the two.
-
Burn Stories Not Tasks
Developers commonly break user stories into tasks to facilitate distributing the implementation work across the team, and allow tracking of progress at a finer level of granularity. Unfortunately, a story can explode into a list of non-trivial tasks so large that the story is not deliverable by the end of the iteration. Ron Jeffries suggests: "Do stories as a unit, not broken into tasks."
-
Panel: BayAPLN Agile Expert Panel
During QCon San Francisco 2008, InfoQ and BayAPLN, a local group of Agile Project Leadership Network (APLN), organized a panel comprised of Agile experts which answered questions from the audience. The panelists were: David Chilcott, Moderator, Polyanna Pixton, David Hussman, Sue Mckinney, Pat Reed.
-
QCon London 2 Months Away; Special Discounts by Jan 15th
InfoQ's 3rd QCon London (March 11-13) is a couple of months away and will again feature 15 tracks, 100 speakers, and excellent learning and networking opportunities. The last chance to save £295 expires next week January 15th!
-
Handling Your Team's "Rotten Apple"
Recently there has been an active discussion in the Scrum Development Yahoo Group about handling an "under-performing" team member. In the 130+ response thread, "Rotten apple in Scrum team", talk ranged from advice for the primary question, to talk of team morale and who manages it, to the classic debate of measuring individuals, to distinguishing whether a team is really a "team", and more.
-
Doing Agile After Layoffs
Part of a development team has been laid off, the team is down to four developers with a part time Scrum Master and no dedicated Product Owner. Is Scrum still applicable? What options are there? How does one adapt?
-
Article: Making TDD Stick: Problems and Solutions for Adopters
In this article, Mark Levison addresses the difficulties encountered by developers willing to adopt TDD, the reasons why many start using TDD but give up after a short period of time, and what could be done to help developers make TDD a habit.
-
Difference Between Internal and External Release
Traditionally, software release is considered to be a handshake between engineering and business where a release made by engineering is passed on to the external world by business. In an interesting article, Israel Gat suggested the reason to split the software release into 'internal' and 'external' release, for the benefit of both engineering and business.
-
Code2Plan, a Free Visual Studio Agile Project Management Add-in
Jesse Johnston and Denis Morozov created code2plan, an Agile software project management tool, as a beta Visual Studio add-in and released it for free. The tool also runs as a stand-alone application that can be used to track projects, iterations, user stories, features, tests, defects and builds.
-
The Correct Ratio of Agile Testers to Developers? It Depends.
An long-standing question in the software development world is: what is the correct ratio of testers to developers? A recent thread on the Scrum Development list asked how agile impacts this ratio. The answer to the first question seems to be 'It depends'. The answer to the second question, according to Elisabeth Hendrickson, is that agile teams can do more testing, with fewer testers.