Despite increased adoption, many of the SOA projects are still failing Things are often getting so bad that in a recent SOA was called "Dead on Arrival". One of the ways to improve this situation is proper SOA governance.
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.
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.
MomentumSI released yesterday its SOA Framework -Harmony. It contains 5 perspectives which include Lifecycle, Governance, Technology, Maturity Model and Information Model. A SOA Framework is typically used to structure the organization, processes, activities, metadata... deployed for service construction.
What is an iteration in the Agile world? How is it different than previous ways the software community has performed iterations? Are there different types of iterations, and does it matter? The ScrumDevelopment list has been recently discussing type A, B, and C sprints (sprint = iteration in Scrum terminology) as defined by Jeff Sutherland and the ideas are relevant the the wider Agile community.
Carrying on from last year's survey, Scott Ambler published the 2007 Agile Adoption survey this month. InfoQ provides some analysis of his findings and asks readers how they would approach getting a single view of Agile trends from across the community.
Using Agile methods with large teams is a reality - the old Agile = Small Team equation is no longer valid. Nonetheless, team size is still an issue. How important is team size and what, if anything, should we do about it?
In Harvard Business Online this week, Donald L Sull and Charles Spinosa wrote about the practice Promise Based Management - using promised commitments in the organisation to enable organisational agiity, encourage entrepreneurship and stimulate collaboration.
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."
The Agile Manifesto is six years old. Many have become disillusioned with Agile as it has spread and (inevitably?) been diluted. Post-agilism has been discussed even before Agile has become truly mainstream. Some have suggested that we have learned much over these years and the Agile Manifesto needs to be updated.
Per Kroll is a director at Rational Software Corporation, where he's responsible for the development and management of the Rational Unified Process. In this interview, Per shares insights from his book 'Agility and Discipline', Agile practices for distributed development, how RUP is changing to support teams that want to customize it, and RUP vs. Agile.
The Agile Journal's April issue examined how tools are being used in Agile projects. There are articles that are pro-tools, anti-tools, and a debate between Ron Jeffries and Ryan Martens.
It's always interesting to check out what's at the top of your colleagues' reading pile... This week, it's a selection from the reading list of InfoQ's architect and co-founder, Alexander Popescu. Alex thought so much of this book, he recommends it to all team participants.
A long and complex thread on the ScrumDevelopment list, set off by the phrase "Agile 2.0," has been exploring the past and future of Agile methodologies (for good or ill) including so-called "next generations" approaches like AUP, MSF Agile, and AMDD. Ron Jeffries, Ken Schwaber and Scott Ambler are just a few of the serious agilists who participated in this lively conversation.
Miko Matsumura interviews John Harby, an independent consultant, OASIS Techican Committee member and SOA practitioner on popular SOA implementation methodologies.