The Latest

The Trouble With Retrospectives[article]

Within the Agile community retrospectives are widely seen as the mechanism for promoting learning and change. But many teams fail to hold retrospectives, or fail to act on the findings, thus they fail to learn and improve. If we are going to fix this we need to change our approach to retrospectives, and find new ways to learn and create change.

Allan Kelly's picture Allan Kelly
Architectural Envisioning on Agile Projects[article]

One of the common misperceptions with agile software development is that agilists don't "do architecture." This completely ignores the 11th principle of the Agile Manifesto which states that the best architectures evolve over time. In this article Scott Ambler overviews an agile practice called "architecture envisioning" which enables you to gain the value from modeling without the cost of needless documentation.

Scott W. Ambler's picture Scott W. Ambler
Retrospectives: A Case Study on Techniques for Incremental Improvement[article]

In this article we describe our work with teams that were spread between the US and India, and with the unavoidable cultural difference. We used a facilitated retrospective to discover the most challenging issues in the process and, just as important, to build a team and increase trust between team members. In later work with the teams, we noticed the immediate positive impacts on the people and the process.

Software Architecture Challenges and Significance in an Agile World[article]

At the core of all software solutions are underlying software architectures. The architectures reflect initial assumptions about how products fit together, which features are of value to customers, what are the expected integration points, with which related technologies. As software products find acceptance among customers, and technologies continue to evolve, the creators (vendors) of these solutions eventually find the need to adapt underlying architectures. Agile provides a means of doing this early in the product lifecycle and with continual review that provides the creator with the ability to adapt quickly and effectively to changes is the marketplace.

TechWell Contributor's picture TechWell Contributor
Opening the Door to Better Open Door Policies[article]

Many managers claim to have an open-door policy. They want to be available to their employees. But do they really have an open-door policy, or is it a handy name for a commendable intention? Naomi Karten describes the flaws in open-door policies and offers suggestions for making them work.

Naomi Karten's picture Naomi Karten
Software Quality and the Prisoner's Dilemma[magazine]

This industry spin on the classical dilemma illustrates the games we play when software quality is at stake and gives insight into why software managers who forego quality in order to reach a short-term marketing advantage are actually acting rationally.

Paco Hope's picture Paco Hope
A ''D'' in Programming[magazine]

In certain company, the topic of favorite programming languages can elicit the same response as other taboo subjects, such as religion and politics. But, Chuck's going out on a limb to discuss his new favorite language, D, and some of its best features, such as its being strongly typed and compiling to native code, yet it is garbage collected.

Chuck Allison's picture Chuck Allison
A Change Would Do You Good[magazine]

Visit any bookstore these days, and you will be faced with shelves of books whose titles claim they can make everything—from cooking to exercise—more interesting. In our industry, boredom is a problem that can affect your ability to solve complex technical problems. Discover how change can spice up your software processes.

Jonathan Kohl's picture Jonathan Kohl
Where Do I Go From Here?—Professional Growth for Software Testers[magazine]

Most professionals have a detailed career ladder upon which to climb and grow their careers. But in many test organizations that ladder has only one rung—and it leads to management. If management isn't your path of choice, these tips can help you market yourself and add value to your career while you build your own technical career ladder.

Matt Heusser's picture Matt Heusser
Developers ... Start Your Engines: Reuse with Source Code Searches[magazine]

Source code search engines can help you find chunks of reusable code. These search engines differ from generic text search engines by organizing the results to reflect the way code is organized—into functions, classes, packages, etc. These reviews of some popular engines can help you rev up reuse in your work.

Alan Berg's picture Alan Berg
Incremental and Iterative Development[magazine]

People get wrapped around the axle trying to understand the difference between incremental and iterative development. The Unified Process authors in the 1990s didn't help by indiscriminately calling everything iterative development. The two are different and must be managed differently. Successful teams do both at the same time, usually without thinking about it. Then someone starts thinking about it and does one without the other. Bad news follows.

Alistair Cockburn's picture Alistair Cockburn
Learning the Hardware Lessons[magazine]

Systems and software aren't just about correctness; they are also about solving problems for people. According to the context-driven software testing movement, a problem isn't solved if the product doesn't work. Michael's experience in a hardware store drives that lesson home.

Michael Bolton's picture Michael Bolton
The Art of Persuading Management[magazine]

You can't get your manager to give you what you want if he won't listen to you. Naomi suggests some strategies-including being methodical, gathering data, properly timing your requests, and practicing what you plan to say-that can help you make your case to the powers that be.

Naomi Karten's picture Naomi Karten
Project Negotiations and the Iron Triangle[article]

Negotiation skills are useful in life and essential for professional success. This week, Payson Hall provides a short tutorial on project negotiations that includes a technique to help you look for solutions. The use of motivation and the "Iron Triangle" is a good starting point.

Payson Hall's picture Payson Hall
Lessons Learned About Starting a Development Group in India, Part 3[article]

In this closing segment of a three-part series, Peter Clark explains how he and his company took lessons learned from their first failed attempt at establishing a software development group in India and developed a new and successful plan the second time around.

TechWell Contributor's picture TechWell Contributor


AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!