The Latest

	Silly Assumptions[magazine] Software development requires a variety of skills, but organizations shouldn’t assume that a worker can move to a new position—be it analyst, manager, or tester—without task-specific education or assistance.	Karl E. Wiegers July 25, 2006
	A Look at QuickBuild[magazine] Career software assembler Greg Kubaczkowski takes a look at QuickBuild, a Web-based, multi-platform, build management system that facilitates and automates builds with an intuitive user interface and a rich set of features.	Greg Kubaczkowski July 25, 2006
	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.	Tod Golding July 25, 2006
	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.	Chris McMahon July 25, 2006
	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.	Alistair Cockburn July 25, 2006
	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.	Bob Payne July 24, 2006
	Agile 2006 - Open Space Kickoff - Diana Larsen[article] Podcast Diana Larsen kicks off OpenSpace at the Agile 2006 conference.	Bob Payne July 24, 2006
	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.	Bob Payne July 24, 2006
	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.	Bob Payne July 24, 2006
	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.	Esther Derby July 18, 2006
	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.	TechWell Contributor July 9, 2006
	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.	TechWell Contributor July 6, 2006

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.