Articles

Agile at 10 – A State of Contradiction

Mike Beedle states that agile is in a state of contradiction, the agile of 10 years ago is now passé and we run the disk of diluting the real meaning of being agile through lip service implementations without focusing on quality. He echoes the call in the 10 Year Reunion meeting for a concerted focus on quality, and asks what an Agile Manifesto 2.0 should contain.

Agile Architecture Interactions

James Madison shows how architects can bring agile and architecture practices together to pragmatically balance business and architectural priorities while delivering both with agility.

Patterns-Based Engineering: Successfully Delivering Solutions via Patterns

InfoQ spoke with Lee and Celso about the Patterns-Based Engineering: Successfully Delivering Solutions via Patterns book, discussing patterns for working with patterns, MDD and the promise of reuse. The book focuses on how to improve efforts in identifying, producing, managing and consuming patterns – leading to better software delivered more quickly with fewer resources.

Bridging Internal and External Software Quality with Sonar and JaCoCo

In this article, author Olivier Gaudin discusses the differences between internal and external software quality and how to perform the software quality assessment using tools like Sonar and its new extension JaCoCo.

Key Takeaway Points and Lessons Learned from QCon London 2011

This article presents the main takeway points as seen by the many attendees who blogged or tweeted about QCon. Comments are organized by tracks and sessions: Keynotes, Tutorials, Architectures You've Always Wondered About, Building Systems With REST, Design and Objects 2011, Enterprise Agile Transformation, Functional Web, HTML5, the Platform, iOS4 and Android, NoSQL: Where and How, and many more!

How ALM Drives Business/IT Alignment, Competitive Advantage

ALM and Business Processes

Large-Scale Agile Design & Architecture: Ways of Working

During my 2011 QCon London keynote on "Scaling Lean & Agile: Large, Multisite or Offshore Delivery", I mentioned — as an aside — that, "Architecture is a bad metaphor. We don't construct our software like a building, we grow it like a garden." This prompted many a tweet, and some people were interested in clarification or elaboration.

The Art of Creating Whole Teams: how agile has changed the way we work with our customers

Angela Martin earned her PhD examining how agile methods work in practice and what is different about this way of working. She shares some of the key practices which organisations can implement to increase their likelihood of successful cultural change through creating Whole Teams - truly cross functional collaborative teams working well together to deliver products which meet customer's needs

The Top Five Challenges of Building Software Platforms in the Agile World

When scaling Agile to the enterprise new concerns arise that require revisiting the values and practices of Agile software development. One such concern relates to a common strategy to achieve reuse at the enterprise level - building software platforms. This article lists the top five challenges that an Agile organization should expect to face when deciding to adopt a software platform strategy.

The Accidental Agilist: A Personal Look Back at 10 Years of the Agile Manifesto

Johanna Rothman reflects on her journey to pragmatic agility. She discusses the way in which agile practices work together to improve project outcomes, and how this is not restricted to software development. She challenges teams to embrace the transparency that agile brings and stop talking about becoming agile and start doing it properly.

Implementation Decision Rationales – Program Comprehension in Agile

Given the fact that the bulk of a developer's work is maintaining and enhancing existing code, Fabian Kiss makes the case for a lightweight approach to documenting the rationale and decision process behind design decisions to help later developers tie the source code syntax to its meaning in the application domain. Using simple tags and clearly thought out rationale to provide just-enough value.