Most organizations hire Agile coaches to carry out an organization wide Agile transformation. The intention is to have a lean and fit organization by the time coaches walk out of the building. However, it is very difficult to achieve transformation that improves the end-to-end delivery process and is sustainable if the transformation just begins at the team level.
Pair Programming continues to be one of the most debated and controversial practices of recent years. Most proponents don't falter in their praise of the benefits, but many of even these same people will admit they struggle to get pairing really going in their shops. Why? Obie Fernandez opinions 10 reasons why this might be so.
Allan Kelly sites an article from MIT's Sloan Management Review about why it is important to get a team's technical competence and ability improved before focusing on business-IT alignment. This, he claims, is one of the reasons Agile software development has been so successful. Allan's point indirectly touches on a recent community debate about successful, valuable, Agile adoption.
In this interview from QCon San Francisco 2008, Ian Robinson discusses REST vs. WS-*, REST contracts, WADL, how to approach company-wide SOA initiatives, how an SOA changes a company, SOA and Agile, tool support for REST, reuse and foreseeing client needs, versioning and the future of REST-based services in enterprise SOA development.
Recently InfoQ reported on Jim Shore's 'The Decline and Fall of Agile', which highlighted a trend for organizations to adopt "Agile" (in name) but fail to adopt what it means to be Agile (in practice). Community leaders such as Joshua Kerievsky, Martin Fowler, and Ron Jeffries have taken Shore's post a few steps further recently, posting their own thoughts on what's going on with this situation.
Many important challenges faced by a software architect for a large company have as much to do with the organization as technology. In a recent blog entry, Dan Greenblog drew parallels between the principals behind software architecture and effective organizational structures.
As organizations continue to grow their IT investments (bought, borrowed, or built) and concepts like Business Process Management and Service Oriented Architecture become more common, the role of Enterprise Architecture (EA) has become more common. Recently, several people in the EA community have spoken about its current state.
In this article Stefan Tilkov, innoQ SOA consultant and InfoQ SOA Community editor, introduces a potential set of roles for successful SOA Governance. He describes the individual roles as well as the tasks assigned to each independent of any tool, vendor, or technology.
In this article, MomentumSI's Ed Vazquez explains the basics of SOA governance, with an explicit focus on the need for a holistic SOA governance model and shared governance principles.
Seasoned practitioners packed a small room at Agile2006 to hear Linda Rising's "Are Agilists the Bonobos of the Software Community?" where she shared her thoughts on the evolutionary roots of teamwork. In this InfoQ interview, Linda talked with editor Deborah Hartmann about how writing her book "Fearless Change" led her to read on the science of the human brain and the social rituals of apes.
The fit between Agile teams and traditional enterprises can be challenging. Agile may highlight or exacerbate pre-existent dysfunctions, in areas a project manager may not be well-placed to address, so those involved in Agile roll-outs are thinking about alternate ways to organize the enterprise. Holacracy, created at Ternary Software, suggests that self-organization can extend outside IT.
At XP2006, Amr Elssamadisy announced a new wiki site for collecting Agile Practice Patterns. Well, it's up and ready to go, already loaded with patterns from ChiliPlop 2006 and XP 2006 conferences.