InfoQ Homepage Agile Techniques Content on InfoQ
-
Does the Agile Community Need a Maturity Model?
Periodically an Agile Maturity Model or a Framework for Agile Adoption shows up on the radar. There are also several consulting companies performing Agile 'readiness assessments' as a precursor to helping their clients 'become' Agile. Are these indications of an unfulfilled need in the community?
-
Is Pipelined Continous Integration a Good Idea?
Sometimes, when the team and/or code-base get large, the CI server starts to slow down. The cycle between builds grows and the feedback degrades – a build may take an hour or more to respond with a pass/fail, and by that time several people may have checked in their code into an already broken build. To address this issue, many teams “pipeline” their CI - but is this a good strategy?
-
xUnit.net - Next Generation of Unit Testing Frameworks?
Jim Newkirk, creator of NUnit, has announced a new Unit Testing Framework called xUnit.net. The proclaimed successor to NUnit is supposed to get rid of NUnit's mistakes and shortcomings and add some best practices and extensibility to the framework.
-
Agile Bibliography Wiki
George Dinwiddie announces the Agile Bibliography Wiki to track readings on the subject of agile, particularly those that are useful to back up a point, or which are useful references, and invites the community to help fill out the reading list.
-
Are Automated Agile Tools Tactile Enough?
Can the bonding that takes place when a developer picks a story card off the task board and takes it over to her desk ever be replicated in a system? InfoQ delves into social informatics, and addresses the effects it has on the Agile way.
-
Why do Agile Adoptions Fail?
Although agilists focus much of their energy on helping their agile projects succeed, it is helpful to periodically stop and consider what causes some agile projects and agile adoptions to fail. Armed with this knowledge, perhaps one can avoid these same pitfalls.
-
InfoQ Article: Lean Kanban Boards for Agile Tracking
"Big Visible Charts" aren't unique to Agile - Lean manufacturing also has its Kanban Boards. "Kanban" roughly means "card or sign," and each Kanban card is "pulled" onto the board only when the work represented by an "in progress" card is retired. In this InfoQ article, Kenji Hiranabe proposes using Kanban Boards to track Agile project status (Time, Task, and Team) to enhance collaboration.
-
Failure to Learn Stifles Productivity
Amr Elssamadisy and Deborah Hartmann have written an article asking us to consider that there may be one common attribute to all software development projects that, if focused upon and improved, can make productivity soar.
-
Blocking: Useful? Dangerous? Ethical?
George Dinwiddie commented on a discussion that took place in the eXtreme Programming yahoogroup about "blocking" as described by Scott Ambler: "This is a great example of something that I call blocking, where you produce the paperwork, attend the meetings, pretend to care, ... to make it look as if you're following the 'official process'".
-
Is Selenium worth the pain?
Is Selenium worth the pain? Atlassian developer Nick Menere has asked that very question on the Atlassian Developer Blog. In his blog post Menere looks at the roadblocks found while trying to use Selenium to test two new Ajax features of JIRA 3.10.
-
Presentation: Applying Agile to Ruby
In this presentation, Fred George talks about the application of agile practices in the enterprise and how they can help with the adoption of Ruby.
-
Iteration Types
What is an iteration in the Agile world? How is it different than previous ways the software community has performed iterations? Are there different types of iterations, and does it matter? The ScrumDevelopment list has been recently discussing type A, B, and C sprints (sprint = iteration in Scrum terminology) as defined by Jeff Sutherland and the ideas are relevant the the wider Agile community.
-
Book Excerpt: How to Improve your Continuous Testing
Continuous Integration has become a standard development best practice - but it's not always done well. Tests take up much of an application's build time, and poorly constructed test suites can cause long builds, whereupon teams start to circumvent agreed-upon CI practices just get the time to code. InfoQ presents advice and examples in Chapter 6: Continuous Testing from a new CI book.
-
InfoQ Interview: Experiences with Planning Poker
In this fourteen-minute interview, Nils Haugen described "Planning Poker," a simple mechanism for arriving at estimates collaboratively, which has additional team building benefits and improves team estimates over time. Haugen shared his views on why this technique is an important tool for Agile teams in this InfoQ interview.
-
Has Agile Crossed the Chasm?
Carrying on from last year's survey, Scott Ambler published the 2007 Agile Adoption survey this month. InfoQ provides some analysis of his findings and asks readers how they would approach getting a single view of Agile trends from across the community.