What does "just enough architecture" mean? Can we agree on this? The answers from FDD and XP seem divergent. Michael Nygard, author of Release It! unravels the story of a production problem which typical Agile approaches would not have prevented, asserting that Agile teams may need to attend more to architecture, if they want to sleep through the night once it's deployed in the real world.
Martin Fowler has questioned Microsoft's grip on leading-edge developers. MS has threatened one developer with legal action over his TestDriven.Net extension for VisualStudio Express, and MS development of an incompatible rival to NUnit has alienated many developers. Is there a widening divide between MS and the Agile community, as each pursues different a vision? Now's the time to speak up.
On CIO.com, Thomas Wailgum wrote about why, despite the evidence, Agile adoption remains at a steady, rather than explosive growth. He posde questions to CIO's of a number of Fortune 500 organisations in his article "How Agile Development Can Lead to Better Results and Technology-Business Alignment."
An old post on "The Physics of Passion" resonates today, as the methodology argument continues: is Agile an approach worth embracing? Or just the latest flavour of corporate Kool-Aid? Kathy Sierra wrote that being accused of "drinking the Kool-Aid" can be a good thing: a sign that we're developing passionate proponents - and opponents.
At the start of each New Year, some of us stop to look backward, and actively resolve to move forward wiser than before. Scott Ambler, Liz Barnett and Kirk Knoernschild have shared with us their recommendations for working smarter in 2007, including: take a hard look at at your business objectives; equip your teams properly to maximize agility; and above all - behave yourselves!
A lively debate is underway among the folks at ThoughtWorks... Starting with Dr. Jim Webber, noted author and ThoughtWorks' top SOA consultant, coining the term: Agile athiest. Does the rise of "Agile religion" signal that the moment has arrived to retire the "Agile" label?
SOA expert John Harby proposes an alternative structure for the ESB which is more distributed, federated, registry centric and solves some of the concerns raised about the bus topology for SOA including vendor lock-in, ESB feature overkill and the emergence of a new architectural stovepipe.
As adoption of Agile methodologies grows, challenges abound, including the possibility of dilution as teams copy practices rather than growing them, implementing them without understanding. InfoQ's own Deb Hartmann gives us a frank discussion about how failure to teach the basics puts much at risk: the integrity and engagement of team members, and the trust of their customers.
Yesterday Steve Yegge blogged about development practices under the title "Good Agile, Bad Agile". He wrote about "Good Agile" at Google, "Bad Agile" almost everywhere else, and offered consultants and job hunters some professional advice: drop the name.
Kevin Brady, self-declared Agile critic, has a problem with Agile software development approaches: he feels that while they look great on paper. they fail to work in reality because they forget the human factor. Commenters on his blog entry question whether Agile or poor implementation lie at fault.
Event Driven Architecture (EDA) is a term promoted by Gartner to describe an evolved state of Enterprise software characterized by real time events. EDA has been associated to its detriment with SOA 2.0, however, there may be technical legitimacy to some of the EDA ideas.