• submit to reddit
Mark Needham07/23/10
7 replies

TDD, small steps and no need for comments

I recently came a blog post written by Matt Ward describing some habits to make you a better coder and while he presented a lot of good ideas I found myself disagreeing with his 2nd tip: 2. Write Your Logic through Comments

Matt Stine07/22/10
0 replies

Going Guerilla: Where to Start

Welcome back to another episode of The Agile Guerilla series. The focus of this series of articles is to to help you introduce change, specifically moving to agility, into your organization from the grassroots level.

Eric Hagan07/22/10
0 replies

Video: Human Dynamics and Agile Adoption

In the Agile Manifesto, the first thing it says is "People and Interactions over Process and Tools." But what does that mean? In this interview,...

Peter Schuh07/22/10
0 replies

Schedule Chicken Is an Iterative Disaster

Ostensibly originating in Rebel Without a Cause the game of chicken entails a test of courage between two or more individuals. Each participant is seated in a speeding vehicle (50s sports car, farm tractor, failing project schedule, etc.) racing toward a ...

Jared Richardson07/21/10
0 replies

Responding to Change Is Too Much Work

The fourth tenet of the Agile Manifesto is a difficult one.

Peter Schuh07/21/10
0 replies

An Iteration Zero for Project Recovery: Starting Again Without Starting Over

In my post a few weeks back on How to Start the Next Recovery Project I asserted that I will take the following four steps the next time I take on a recovery project: Assess the Team’s Current CapabilitiesMake Management Understand the Real ProblemHelp...

Robert Diana07/21/10
0 replies

Re-Engineering In Agile Development Can Just Be Refactoring

If you talk to a programmer, almost all software sucks, even the programs they wrote a few months ago. This is typically due to changing technology, increased knowledge or even a market shift. The software you wrote may have been a good idea when you...

Matt Stine07/20/10
0 replies

You Are Your Software's Immune System!

The vertebrate immune system rivals the most intricately engineered security system on a bad day, detecting and destroying most microorganisms that we encounter on a daily basis within minutes or hours [1]. Occasionally a pathogen will breach the early lines...

Cal Evans07/20/10
2 replies

An entirely unscientific look at why people attend conferences.

Dear Reader,Those of you who follow me on twitter (@calevans) know that recently I asked for opinions on conference attendance. I’ve collected what I learned in this blog post.

Mitch Pronschinske07/19/10
0 replies

Go Replaces Cruise - Aligns Devs, QA, and Ops

It turns out that ThoughtWorks Studios' former Cruise product is getting more than just a name change.  DZone spoke with Jez Humble, the Build and Release Principal at ThoughtWorks Studios, about today's launch of Go.   The new replacement for Cruise...

Mike Cohn07/19/10
0 replies

Managing Risk on Agile Projects with the Risk Burndown Chart

Risk management is a central part of traditional project management and is included as one of the knowledge areas in the Project Management Institute’s (PMI) body of knowledge. In many of my classes, participants ask how Scrum and agile address risk...

Alberto Gutierrez07/19/10
1 replies

Waterfall vs. Agile: QA and Management

We saw in the previous articles

Mike Cohn07/19/10
1 replies

Estimating Work Shared Between Two Backlog Items

Product backlog items can be ideally written to be independent. It is the hallmark of a good team that its members can implement product backlog items in any order. However, it would be nearly impossible to remove all dependencies between product backlog...

Mark Needham07/19/10
0 replies

Is 'be the worst' ever limiting?

One of my favourite patterns from Ade Oshineye and Dave Hoover's 'Apprenticeship Patterns' is 'Be the worst' which is described as follows:

Saket Agrawal07/17/10
0 replies

Does (PURE) XP work for non trivial software in most practical scenarios?

Some of the XP practices don’t seem to be practical for non trivial software.