InfoQ Homepage Agile Content on InfoQ
-
Case study: A new approach to integrating architectures post-merger at Lawson
The merger of Lawson and Intentia in 2006 left developers with an important problem to solve - the integration and presentation of legacy applications and business services that are constructed in Java, .NET, and other technologies. This case study looks under the hood at the new architecture at Lawson and how they got there.
-
InfoQ Changelog
InfoQ maintains a version number tied to new features developed for the site as a means to communicate progress to its audience. v1.1.5 is the latest version. InfoQ initially launced at 0.6 last year.
-
Book Excerpt: Scaling Software Agility
"But does Agile scale?" Emerging stories and case studies indicate that it certainly does. InfoQ brings you two excerpts from Dean Leffingwell's book "Scaling Software Agility: Best Practices for Large Enterprises". Chapter 1 presents how Agile methods respond to the need for competitive advantage, and Chapter 2 revisits "Why the Waterfall Model Doesn’t Work".
-
SOA and Agile: Friends or Foes?
SOA aims at making the entire enterprise agile by using services as the building blocks for applications. Agile software development aims at making organizations agile by introducing practices that increase communication and feedback. Which is right? Which is better? Are we comparing apples and oranges? Can they be used together, and if so, how? Join us in the discussion!
-
Ruby on Rails case study: ChangingThePresent.org
Bruce Tate, author and CTO of ChangingThePresent.org gives a glimpse inside the day to day operations of ChangeThePresent.org with a broad overview of how his team works, the technology trusted for production environments, tools, and most important Rails frameworks.
-
Key Takeaway Points and Lessons Learned from QCon London 2007
This article presents the main takeway points and further reading as seen by the many attendees who blogged about QCon. Comments are organized by tracks and sessions: Case studies (amazon, eBay, Yahoo!) Java, Agile, the Agile Open Space, Qualities in Architecture, Ajax and Browser Apps, .NET, Ruby, SOA, Usability, Banking Architectures followed by a summary of peoples over all opinions of QCon.
-
Paul Oldfield on Doing Agile Right
In a new InfoQ interview, Agile thought-leader Paul Oldfield shares his ideas on what it means for organizations to do Agile "right".
-
TDD with Selenium and Castle
Dan Bunea shows developers how TDD can be applied in .NET using Selenium RC and Castle. Test first principals provide architects a way to quickly jump into active development early in the application development lifecycle. The benefits of TDD are a drastic reduction in defects as well as increased flexibility in the code base since the application evolves quickly through an iterative process.
-
Agile User Interface Development
The wider adoption of Agile software development has raised questions about how an approach that shuns up-front design and analysis can coexist with the emerging practice of user-centered design, which has a detailed user research and modeling phase before development begins. In this article Dave Churchville explores how the disciplines can be used together for an effective development process.
-
Kent Beck on Agile Adoption & Values
In an interview with InfoQ editor Kurt Christensen, Kent Beck shares his thoughts on a range of topics, from the challenges associated with adopting and applying agile values and practices within a large organization, to the future of agile as it gains mainstream acceptance.
-
Case Study: Targeted Practice Adoption using Patterns
It's easy to forget what originally motivated us, once we're implementing Agile. Teams spin, trying to figure out which practices to start with, unsure which will have the biggest impact, or how they fit together. Amr Elssamadisy and John Mufarrige propose a customized adoption approach to help teams decide where to focus first - an alternative to adoption of pre-packaged methodologies.
-
Good Agile Karma
Agile relies heavily on discipline, rather than genius. We're told that average teams, even in the early stages, can achieve dramatic performance improvement if they are disciplined. As we do these things, the effects of our words and actions actively create, and re-create over time, the environment in which our teams and projects operate - for good or ill.