InfoQ Homepage Conferences Content on InfoQ
-
Scrum Boosts Effectiveness at the BBC
In 2002, BBC's New Media division decided to use Scrum to manage the change and uncertainty inherent in their emerging business domain. Three years later - Andrew Scotland tells us it was worthwhile.
-
Security Assertion Markup Language - SAML
The Security Assertion Markup Language has emerged as the gold standard for building Cross-Domain SSO solutions and is a key technology in the domain of federated identity management.
-
Case Study: Zero Calories J2EE
Case study of a successful project where the J2EE stack was abandoned in favour of a lightweight web architecture using Tapestry, Spring, Hibernate, and testing with JUnitWebTest.
-
Java + .NET, Integration Strategies Presentation
Ted Neward demonstrates using Microsoft Office to act as a rich client to Java, building a WPF gui on top of Java POJOs, and how to execute Java from within a Windows Workflow host.
-
How to Design a Good API & Why it Matters
Core Java language designer Joshua Bloch teaches how to design good APIs, with many examples of what good and bad APIs look like.
-
Agile Quality: A Canary in a Coal Mine
Scrum co-creator Ken Schwaber spoke at Agile2006 on code quality as a corporate asset. In this video Schwaber discussed how a degrading codebase paralyses teams and increases corporate risk.
-
Introduction to Domain Specific Languages
Martin Fowler introduces a simple example of DSL, bringing out the difference between external and internal DSLs, and talking through the trade-offs in using both forms.
-
The Role of the Enterprise Service Bus
Mark Richards shares a detailed, product-agnostic vision regarding the role of an ESB and the capabilities an ESB must provide.
-
The Roots of Scrum
For 60 minutes Jeff Sutherland covers Scrum from creation to its use at Xerox, Honda, WildCard, Lexus, Google. He looks at Scrum types A, B C, and confirms that Kent Beck used Scrum practices for XP.
-
AOP-Myths and Realities
Ramnivas Laddad tries to clear up the most common myths and misunderstandings that hinder the adoption of AOP discussing the reality [behind each myth] from an aspect-oriented-programming perspective.