InfoQ Homepage Adopting Agile Content on InfoQ
-
Agile Smells: Don't Let This Happen To You!
Mark Levison wrote an interesting blog summarizing some of the work that has been done to catalog Agile smells. We summarize some of those smells and point to other intersting work that documents the Agile community's experience in adoption.
-
Presentation: Dealing With the Organizational Challenges of Agile Adoption
In this presentation filmed during QCon London 2007, Joseph Pelrine talks about the challenges faced by organizations trying to adopt Agile methods.
-
Presentation: Agile Architecture Is Not Fragile Architecture
In this presentation filmed during QCon 2007, Coplien and Henney describe how to start with enough architecture to ensure long term success of an Agile developed project.
-
Interview: Rachel Davies on Generic Agile
In this interview taken during Agile 2007, Rachel Davies, director of Agile Alliance, talks about Generic Agile, about the necessity to understand what is the essence of a development process.
-
Results of Agile Adoption Survey 2008
In February 2008, Dr. Dobb's conducted a survey on Agile adoption and the success rate of Agile software development. The survey revealed some interesting results on various parameters, including: adoption, scalability, iteration length, and team location.
-
Presentation: Agile Project Lifecycle in User Stories and Release Planning
In this presentation recorded during QCon London 2007, Rachel Davies, director of Agile Alliance, talks about the Agile development cycle starting with user stories and planning the releases.
-
How Long Should You Sprint For?
What factors influence the length of your sprint? When you're trying to pick a length, between two days and six weeks, what factors should you take into consideration? One coach has taken a stab at identifying shortening and lengthening factors.
-
Interview: James Shore on “The Art of Agile Development”
In this interview taken by InfoQ's Deborah Hartmann during the Agile 2007 conference, James Shore, a prominent figure of the Agile community, talks about the book "The Art of Agile Development".
-
Integrating Testers on to the Agile Team
What is the role of testers on an Agile team? What is their day to day experience like? What lessons have they learned
-
Don't Worry About Scaling Scrum
Most Scrum adopters have their first doubt in terms of its scalability. Tobias Mayer suggests that before looking into quick solutions for complex problems, adopters should focus on understanding the principles of Scrum. Once the foundation is correctly laid, Scrum will take care of scaling itself.
-
Stories of Scrum Adoption in China
This recent inquiry, by InfoQ China editor Jacky Li, looked at five very different cases of Scrum adoption in China, which got different results. He asked: Why did you use Scrum? How did you adopt it? What problems did you encounter, and why did it succeed or fail? Despite the small sample size, it's an interesting comparison, pointing out that improvement doesn't ensure success.
-
Creating The Culture For An Agile Environment
Greg Smith offers an in-depth practical perspective on making your agile transition just as much about culture change as it is about process change.
-
Debate: Agile Transition Success Rates, Help or Harm?
Many of the Agile community have chimed in on a recent popular discussion regarding success rates of Agile transitions. Responding to Niraj Khanna's question on the subject, Kent Beck, Ron Jeffries, Alistair Cockburn, Chet Hendrickson, and many more debate the value and risk of establishing such statistics.
-
Common Questions when Adopting TDD
If you are new to TDD you may be struggling with some common questions such as: How much upfront design should I tolerate? Or, when writing a test you have to build interfaces and some classes to get it to even compile - how far do you let that go?
-
Is the ScrumMaster-as-Blocker a Pattern to Follow or a Smell to Avoid?
So, you are on a development team that is adopting Agile or thinking of going in that direction. If you are adopting Agile by starting small, you probably are working against-the-grain in your organization. You may have heard that there should be a role that protects the team from the rest of the non-Agile world that might be useful