• submit to reddit
Benjamin Mitchell07/27/11
0 replies

How three forks on a hand-drawn chart helped a team improve

After visualising the workflow of a recent client’s software development process, and showing where the work was, the team realised there was a queue of tasks that had been developed and were waiting to be validated (‘tested’).  The...

Giorgio Sironi07/27/11
0 replies

Practical PHP Refactoring: Hide Delegate

The client code is calling a method on a collaborator (delegate) of another object, obtained by getter or another sequence of calls. Hide Delegate is about respecting the Law of Demeter: don't talk to strangers, by avoiding relying objects which are not...

Paul Stack07/26/11
3 replies

Automated UI Testing - Part 1 - WatiN

A few months back I discovered a tool called WatiN. This is based on WatiR and is a web application testing tool for Dot Net developers. After doing a few little test applications i started to see the benefit of using this application in my development....

Benjamin Mitchell07/26/11
0 replies

Removing the bubbles: solving bottlenecks in software product development

A challenge with software product development is visualising the work so that you can spot where there are delays in the process of converting ideas from “concept to cash”. This post shows how a cumulative flow diagram helped identify a pattern of...

Mark Needham07/26/11
0 replies

Retrospectives: The 4 L’s Retrospective

I facilitated the latest retrospective my team had last week and decided to try The 4 L’s technique which I’d come across while browsing the ‘retrospectives’ tag on del.icio.us. We had 4 posters around the room representing each of the L’s:

Sandro Mancuso07/26/11
0 replies

SRP: Simplicity and Complexity

Simplicity does not precede complexity, but follows it. - Alan Perlis

Michael Sahota07/25/11
0 replies

Benjamin Zander on the Art of Possibility

I wanted to share this inspiring video on the art of possibility and how our stance in the world can change everything. Stance is very important for coaching. This video is pretty long, but the best bits for me were in the first 12 minutes. Some great parts:

Venkatesh Kris...07/25/11
0 replies

Understanding Scrum

Even though Scrum has touched souls of most of the software developers across the globe, it still seems to be understood as set of practices.  There are many yet to catch up with the principles behind the Scrum.   In the recent blog, Ken Schwaber ...

Dave Rooney07/25/11
0 replies

Whither Requirements?

We accomplish what we understand. If we are to accomplish something together, we need to understand it together.Signature from Ron Jeffries e-mail, circa 2005. A common issue I've encountered with teams starting to use an Agile approach such as Scrum is...

Gareth Rushgrove07/25/11
1 replies

Jenkins Build Pipeline Example

The idea of a build pipeline for web application deployment appears to have picked up lots of interest from the excellent Continuous Delivery book. Inspired by that, some nice folks have build an excellent plugin for Jenkins unsurprisingly called the Build...

James Betteley07/24/11
0 replies

The Boy Who Cried Wolf – Why Broken Builds Must Not Be Ignored!

We’ve all heard the fable of the boy who cried wolf, an old tale written by a Greek slave who lived a long time ago and liked telling stories. I must stress thought that this was just a story, but like many good stories (Star Wars, Gremlins 2) it’s...

Robert Diana07/23/11
1 replies

When Do You Say A Development Task Is Really Done?

I love when other people write a blog post at the same time you are struggling with the problem that they describe. Today’s timely post comes from Michael Bolton on his DevelopSense blog. In “The Undefinition of Done”, Michael talks about the fact...

Dave Rooney07/23/11
0 replies

A Survival Guide for New Agile Coaches - Why?

When a toddler learns to speak, often his first recognizable word is "Mom" or "Dad" or some variation of those.  His second is "Why?"  If you were to take a teenager and, like, count the number of occurrences of...

James Shore07/23/11
0 replies

Let's Play TDD #125: The Cost Basis Field

The source code for this episode is available here. Visit the Let's Play archive for more episodes! Many thanks to Danny Jones for figuring out the HD Youtube embed code.

Dhananjay Nene07/23/11
3 replies

Jerk Programmers Can’t Be Managed Tactically

Interesting post by Scott Berkun : How to deal with jerk programmers which isn’t exactly consistent with my experiences from both sides of the fence. Scott states: The best place to start is empathy. Why is someone acting like a jerk? There are basic...