Better Software Magazine Articles

The Kanban Primer: A Cultural Evolution in Software

Kanban,a Japanese word meaning “signal card,” introduces a new way to think about software development. Through signaling, a limit is set on work in progress resulting in a system that is never overloaded. Kanban signals do not need to be based on passing physical cards; any virtual signaling mechanism will do equally well.

David J. Anderson's picture David J. Anderson
What's a Manager to Do?

Self-organizing teams still need managers. But those managers need to rethink how they do their jobs and consider how much self-management the team can take on. Finding the sweet spot between hands on and hands off is the key.

Esther Derby's picture Esther Derby
Follow the Process

Building better software does not rely on methodologies. "Following the process" omits important human factors that ultimately lead us to success.

Lee Copeland's picture Lee Copeland
Keep Non-developers in the Loop

Keeping QA members up to date on changes as they happen–through meetings, wikis, and email–can reduce the number of unnecessary bug reports and save you time and frustration.

Melanie Tayler's picture Melanie Tayler
Is ''Agile'' Distracting You?

If a process tool or service claims to be agile it must be good, right? Not necessarily. The term "agile" has become abused and, since we don't have a standard dictionary definition, it is open to interpretation. So, let's look beyond the label to what really matters—value.

Jonathan Kohl's picture Jonathan Kohl
Encourage Pair Programming

Pair programming is one of the most controversial agile practices. Managers are concerned about the costs and developers are concerned about personal agony. But there also are many benefits. If you are thinking about trying pair programming, here are several reasons why you should.

Rob Myers's picture Rob Myers
How to Fail with Agile

A switch to agile often conflicts with personal career goals such as maintaining the status quo and working no harder than necessary. These twenty guidelines will help you sabotage your agile project, helping you fail quickly and spectacularly.

Stop The Insanity! Using Root Cause Analysis to Avoid Repeating Your Mistakes

We've all heard Einstein's definition of insanity, and it definitely holds true in software development. We "are" going to make mistakes in product development, but root-cause analysis can help us understand those mistakes and be proactive in not repeating them.

Ed Weller's picture Ed Weller
Software Quality and the Prisoner's Dilemma

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 Change Would Do You Good

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

Pages

AgileConnection is a TechWell community.

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