The Latest
Fighting Temptation[magazine] Programmers must balance time, business needs, and a long-term maintenance profile while producing code. Are you willing to accept the easy path now, even if it means trouble down the road? Tod Golding explains that the fastest way may not always be the right way. |
||
Software Is a Service[magazine] According to Brian Marick, software is little more than a service that has been made into an easily mass-produced form. Because of that, software may be attractive only to its creators—but it still should serve its users faithfully. |
Brian Marick
July 25, 2006 |
|
![]() |
Old School Meets New Wave[magazine] Decades of testing practices are available to today's testers, but sometimes the "old school" approaches are just as powerful as newer tools with evolved frills and features. Chris McMahon offers tips on how you can combine test techniques to improve your agile integration project. |
|
|
Static Electricity: Power Up Your Build Process with a Static Analysis Tool[magazine] Keeping source code functional in the midst of ongoing changes can be tricky, but there are tools available to help you keep bad code under control. In his article, Tom Copeland puts the spotlight on PMD, an open source static analysis tool that can illuminate source code problems and help power up your build process. |
Tom Copeland
July 25, 2006 |
The Declaration of Interdependence[magazine] In an effort to extend the Agile Manifesto to non-software products and management, experts at the 2004 Agile Development Conference developed The Declaration of Interdependence. Alistair Cockburn details the DOI’s six principles and how they can benefit your organization. |
||
Boris Gloger at Agile 2006[article]
Podcast
Boris Gloger talks about his work with Product Owner Teams and the state of Agile in Europe, as well as several strategies to unify multiple customers into a single voice. |
||
Agile 2006 - Open Space Kickoff - Diana Larsen[article]
Podcast
Diana Larsen kicks off OpenSpace at the Agile 2006 conference. |
||
Agile 2006 Keynote - Peter Coffee[article]
Podcast
Peter Coffee delivered a keynote that was both informative and inspiring, tying four of his favorite books back to the Agile Manifesto. |
||
Agile 2006 Kick Off with Todd Little[article]
Podcast
Todd Little kicks off the Agile 2006 conference with a Top 10 List and the news that the conference has nearly doubled since last year. |
||
Approaching a Conflict in Style[article] Conflict is inevitable at work. Sooner or later, you will disagree about what to test, when to test, or how long to test software. How you and the person you disagree with approach the conflict affects both the outcome and how you feel about the exchange. In this column, Esther Derby explains some of the ways people approach conflict and how they affect solutions and relationships. |
||
|
Piecing Together an Agile Organization[magazine] Implementing agile processes can be like putting together a puzzle. But what happens when the pieces don't fall into the right place? Alicia Yanik tells the story of Daniel, who is wound up about his company's new agile elements, and Meg, who sees things from a more enlightened angle. |
Alicia Yanik
July 12, 2006 |
SOA and Agile Development: Continuous Integration And Testing[article] IT organizations view the adoption of agile development methods as a way of bringing an "integrated team" approach to the product development lifecycle where everyone is focused on early, frequent demonstrated results. The second shared goal is service-oriented architecture (SOA). SOA is an approach to deliver integrated component-based ecosystems that are assembled to efficiently execute critical business processes. The goal of SOA is to be flexible and adaptive to the constantly changing business climate. These two productive approaches, when applied concurrently, are setting the stage for the next evolution in the deployment of technology to enhance business performance and results. |
||
![]() |
A Pony in the Pile - A Curmudgeon's View of SOA Adoption[article] I have been in and around Web Services and Service Oriented Architecture (SOA) for a long time. I have built distributed systems for fifteen or more years. I have scars from the Great Web Service Euphoria of '99 to '01. I have gray hair from dealing with the security and management problems of building real services in real networks. I have followed the standards as they have matured. I have observed and worked with clients as they considered and confronted SOA. Here is my conclusion: real SOA is so complex and organizations are so far from ready for it, that the only sound SOA adoption strategy demands agile program management techniques. Nothing less will suffice to guide and sustain an organization through the SOA evolution. |
|
Agile Services In An (SO)Architected World[article] Because one of the core stated objectives of Service Oriented Architecture (SOA) is to increase business and IT alignment and IT's flexibility in meeting changing business needs, on the surface it would seem that SOA and agile methods are a natural fit. And within the SOA model of service production, distribution and consumption, use of agile development methods clearly has great opportunity for effectiveness on the consumption side of the equation. However, the approach by which a suite of generally reusable services within an SOA are defined and produced requires a cross-project perspective that could be viewed as running counter to a typical agile development approach. Some amount of up-front architectural thought must go into initial service definition to prevent those services being developed from becoming solely project-centric. |
||
Improve Service-Oriented Architecture Development with Agile QA Testing Practices[article] Service-oriented architectures (SOA) promise to address many technical challenges by allowing developers to incrementally deliver new business capability while leveraging existing assets. By using agile practices during QA testing, SOA development teams can turn potential roadblocks into opportunities. |