InfoQ Homepage Agile Content on InfoQ
-
Stabilization Sprints, A Necessary Evil or Pure Waste?
Stabilization sprints are an additional number of sprints added to the end of the normal development cycle before shipping the product. As the name suggests, they’re usually added to shake down the product one last time and drive the last of the bugs. Do they belong in Agile environment or should "Done" be enough.
-
Five Benefits of Feature Teams
Mike Cohn and others present their case to why you should consider structuring your teams around software "features" rather than software "components".
-
When ScrumMaster Becomes the Impediment ...
A ScrumMaster as the name suggests is the guardian of the scrum process. He is a change agent supporting his team and socializing Scrum throughout the organization. He ensures smooth functioning of the team by eradicating impediments and keeping the team shielded from distractions. However, in certain scenarios, Agile teams feel that the Scrum Master is the biggest impediment.
-
QCon London March 10-12 Announced
The 4th annual QCon London (March 10-12) has been announced and registration is open! QCon London has become a mainstay conference for the UK and European software development community. This year continues in our tradition of practitioner-driven high quality content with over 15 tracks and 100 speakers including keynotes from GoF author Ralph Johnson and Smalltalk Guru Dan Ingalls and more.
-
Social Contracts Facilitate Team Commitment
Formalised social contracts provide a structure to help reduce the fear, uncertainty and doubt associated with organisational change, and can enable an Agile transition to go more smoothly. Israel Gat provides an example of the social contract he used at BMP Software.
-
Teaching Games - Fun or Serious Business?
Michael McCullough and Don McGreal, creators of the Tasty Cupcakes teaching games website, have published an article on "Fun Driven Development." The economic downturn hasn't squeezed these games out of our training programs - in fact, they've become a staple where Agilists gather to exchange ideas. Here's a little history and some starting points for using games with your teams.
-
What do you do, Testing or Checking?
Software testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test. However, this definition does not talk about sapience which brings about a subtle difference between testing and checking. Michael Bolton talked about this difference and the reason why there should be a difference between the two.
-
Maintainable Automated Acceptance Tests
Automated tests that are brittle and expensive to maintain have led to companies abandoning test automation initiatives, according to Dale Emery. In a newly published paper, Dale shares some practical ways to avoid common problems with test automation. He starts with some typical automation code and evolves in ways that make it more robust, and less expensive to maintain.
-
Do We Need an "Agile Team Lead" Role?
Patrick Wilson-Welsh, Chris Beale, Gary Baker, John Huston, Daryl Kulak, and others are attempting to popularize the idea of a new role, the "Agile Team Lead", to supplant many of the existing leadership roles found in and around agile teams.
-
When Agile Success is Eventually a Failure
It is often assumed that once the pilot Agile teams are successful, the process of Agile adoption is on the right track. Dave Nicolette shares very intriguing insights into situations where the adoption failed even after very successful pilot implementations.
-
Individual Rewards on a Scrum Team
In a recent LinkedIn discussion the question was asked "Should we have an individual recognition reward on a Scrum team". This prompted some intense debate with points both for and against.
-
Software Katas - Practice in Public Makes Perfect
Thought leaders in the agile community are talking about software katas - where one practices specific exercises until they are memorized. Robert Martin has calls them "performance art". Lately there has been an increase in blog posts and sites devoted to katas. The latest addition: weekly screencasts at katas.softwarecraftsmanship.org.
-
System/Acceptance Testing with Time and Dates
Unit Testing Time and Dates is an often talked about problem with relatively simple solutions. More difficult is the acceptance/system testing with Time. What strategies are used?
-
Refactor or Rewrite?
The goal of refactoring and rewriting is to improve the sanity of the system by improving the code readability, structure and clarity. A clean code would be easier to maintain and enhance. However, on many occasions Agile teams have a tough time deciding between the two.
-
Test Driven Development and the Trouble with Legacy Code
Alan Baljeu was trying to use TDD with his large, legacy C++ code base. He found that the principle of the simplest thing that could possibly work was causing him trouble with the amount of rework.