InfoQ Homepage Agile Content on InfoQ
-
QCon London March 9-11 Highlights, Registration Up 100%
QCon London, InfoQ's in-person conference is coming up March 8-11 and registration is double last year's at this time. This 4th annual event is a practitioner-driven conference designed for team leads, architects and project management. A lot of work went into the program this year for this event with usually has over 100 speakers, highlighted in this post.
-
Starting Test Automation for a Legacy Project
It is always a herculean task to write automated regression tests for a legacy application. The questions vary from where to start, how much to automate and deciding on the best strategy for automation.
-
Myths of Kanban
How has the Lean development practice of Kanban been misunderstood? Learn to separate fact from fiction when it comes to Kanban.
-
Predictions about Agile in 2011
As is normal at the beginning of a new year predictions about where industry and practice are heading abound. Mario Moreira and Scott Ambler predict the continued adoption of agile practices across more and more organisations, and the adaptation of agile techniques to larger and more distributed teams, with an emphasis on more structured implementations.
-
Stephen Walther on Integrating JavaScript Unit Tests
Automated testing frameworks need both a good test library and a good integration story. While most JavaScript testing frameworks have been focusing on the former, Stephen Walther has been working on a solution to the integration problem.
-
Characteristics of an Agile Organization
Jim Collins, in his famous book “Good to Great” talks about his teams five year research where they determined what it takes to change a good company into a great one. Can Agile help in the creation of great companies?
-
Should You Assign Story Points To Bugs?
When migrating an existing project to Scrum, one often faces a backlog of unfixed bugs from the pre-Scrum era. Is it effective to assign story points to these bugs and prioritize some along with the user stories in each sprint?
-
Comparing Apple, Google and Microsoft
A Gartner webinar (PDF) compares three major players in the software industry today - Apple, Google and Microsoft –, trying to see where they stand today, and how IT decisions will be affected by their competition with each other. TheOpenSourcery compared the same companies from a different perspective: agility and openness.
-
Swarming: What's the Point?
Agile teams are encouraged to focus all their effort, as much as possible, on one story at a time--a practice known as "swarming." But why do this? What are the benefits you can expect to see by swarming each story?
-
Hearing From Real Customers at Agile 2011
The Working with Customers stage at Agile 2011 is looking for stories and submissions from customers of agile teams. The stage explores the interactions between the customer community and Agile development teams, focusing on the non-technology functions as well as the Agile development teams themselves. In this item the stage producers answer questions and appeal to real world customers.
-
Scrum Project Estimation Beyond the Near-Term?
How can you estimate the effort required for an entire Scrum project when Scrum only recommends doing task breakdowns for the next one or two sprints? Should we even try to estimate project effort in the mid- to long-term?
-
Getting the Customer Involved
Agile methods place a strong emphasis on customer feedback and interaction. Projects with involved customers have much higher chances of success than projects which lack customer interaction. So, how do Agile teams keep the customer involved.
-
How To Complete Stories Without Leaving Bugs Behind
What can you do when unacceptable numbers of stories are "done" with development, but they still have many quality problems?
-
Does Agile Limit Financial Rewards for an Individual?
Tom Reynolds mentioned an interesting comment, that he had heard about the reluctance of people to move to Scrum. The reason quoted was that Scrum would have a direct impact on their financial rewards as it places a lot of emphasis on teams and not the individual.
-
Should We Move a Failed Story Back?
What should we do with a story on our task board when it fails testing?