InfoQ Homepage Agile in the Enterprise Content on InfoQ
-
Inducting Newbies On Large Agile Projects
Anand Vishwanath suggests for large agile projects that using a small scale "simulation project" might be the best approach to getting the newbies into the groove, and provides a recipe for how to go about doing this.
-
Book Excerpt: Agile Testing
InfoQ brings you an excerpt from Agile Testing, a book is for testers on an agile team, test and quality assurance managers transitioning to agile development, and agile teams learning how to approach testing.
-
Agile Governance: The Bridge Between Management and IT
Traditional project governance is used to describe the rules and processes that need to exist to ensure a successful project. At first glance the concept of governance and Agile seem to be incompatible however, most Agilists would agree that just enough governance might do more good than bad for the Agile project.
-
How Do You Get a Hyper-Productive Team?
Some of us have been lucky enough to be on hyper-productive teams, others think this is a myth. Joanna Zweig and Cesar Idrovo have been discussing Group Coherence - a search for hyper productivity with some insightful information for everyone trying to produce a hyper-productive team. Their research gives a possible model of how and why some Agile teams excel and others do not.
-
Interview with Pollyanna Pixton at Agile 2008
Pollyanna Pixton tells us that within a culture of trust leaders must stand back and if they don't then they are hampering and restricting the productivity and the creativity and the innovation of teams. She discusses how leaders can foster a culture of trust and what they must do to get the most out of Agile teams.
-
Software Craftsmanship Manifesto: A Call to Arms
A movement to promote Software Craftsmanship has been brewing for a few years. Since Agile 2008 last year they found a focal point with Uncle Bob Martin's claim that the Agile Manifesto needed amending with a new value: "Software Craftsmanship over Crap". Recently a group has created the Software Craftmanship Manifesto.
-
3 Pillars Of Executive Support For Agile Adoption
An executives job is not over once they've justified agile to their teams and paid for training. To make a transition successful, its required this executive provide sustained support. Esther Derby takes a moment to describe what she believes to be the 3 most important aspects of this ongoing support.
-
Presentation: Joshua Kerievsky Presents 10 Important Points for Agile Transitions
Joshua Kerievsky has distilled his company's years of experience helping their clients transition to Agile software development into 10 points. This presentation puts this advice in context with war stories and a Q&A session.
-
Opinion: It is Time for a New Paradigm Shift in Business-IT Alignment
Fred Cummins, an EDS fellow, offers his vision on how SOA is changing business-IT alignment. He dismisses some proposal which recommend fusing and diffusing IT with and within the business and explains how Services boundaries offer a natural boundary to foster collaboration between the business and IT.
-
Requirements Come Second - What Comes First?
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.
-
Interview: Ian Robinson discusses REST, WS-* and Implementing an SOA
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.
-
Should the Product Owner Be One Person Only?
Is the role of product owner a role that should be satisfied by only one person? There are those who say that there must be one person accountable - a single wringable neck. There are those that say that the expertise needed for a product owner cannot be satisfied by one person. There are many ideas in between about what and who a product owner should be.
-
Adopting The Whole Enchilada
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.
-
Agile Risk Management
Risk management is an activity directed towards the assessing, mitigating and monitoring of risks. Agilists suggest ways to effectively manage risk and use it to make better commitments to the stakeholders.
-
Example Driven Acceptance Testing
Unit and Integration testing often get more importance in Agile teams as compared to acceptance testing. Gojko Adzic and Lisa Crispin suggest approaches to efficiently include acceptance tests as a part of development.