• submit to reddit
Michael Norton11/10/10
3 replies

Code as a Cause of Project Failure

The original questionDuring the speaker panel at SCNA this past weekend, Chad Fowler (@chadfowler) asked, "How many projects fail because of the code?". Given the context, I assumed he was making the point that projects fail due to business...

Robert Diana11/10/10
0 replies

Defining Project Failure

Recently, I wrote about how software development processes do not fail, the people involved with the projects fail. The idea in that post was that the processes are rarely followed the way they are written. The parts that fail are the people adding scope...

Giorgio Sironi11/09/10
0 replies

Practical PHP Testing Patterns: Fresh Fixture

We are exploring the realm of fixtures, the dependencies needed for a test to run. Every test needs a fixture, even if it is only an object, the System Under Test, that must be created.When implementing the Fresh Fixture pattern, each test builds its own...

Michael Norton11/09/10
0 replies

Optimal pairing

What was all that rambling about Harmonic Mean?A while back, I posted a rambling entry about the impact of Harmonic Mean on a team's performance. The post was actually about pairing. My intention was to put a solid mathematical, albeit only...

Stephen Robillard11/08/10
0 replies

A book review of Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation

    They say you never get a second chance to make a first impression, and this book’s hardcover binding makes a great first impression. When was the last time you saw a...

Israel Gat11/08/10
1 replies

The Nine Transformative Aspects of the Technical Debt Metric

No, the technical debt metric will not improve your tennis game. However, using it could help you generate time for practicing the game due to its nine transformative aspects: The technical debt metric enables Continuous Inspection of the code through...

Michael Norton11/08/10
1 replies

Stories are about why; not what or how

Story FomatsI've been on numerous Agile projects with varying methods for capturing stories. Quite popular (and purportedly the ThoughtWorks standard) is the "As a, I want, So that" story format. While I have seen teams do well with this format,...

Giorgio Sironi11/08/10
0 replies

The Dark Side of Lean

Let's start with a definition of Lean software development:

Giorgio Sironi11/08/10
0 replies

Practical PHP Testing Patterns: Standard Fixture

We have entered the realm of fixtures, a term that encompasses all the setup necessary prior to running a test, from instantiating the System Under Test to preparing the input data for it.The Standard Fixture pattern is applied when you attempt to reuse the...

Michael Ceranski11/08/10
1 replies

Using RavenDB with ASP.NET MVC

Traditionally when you think about a database you think of tables, views, indexes and stored procedures. If you have made a career out of developing database centric applications like I have, then chances are that you have spent a great deal of time...

Allan Kelly11/05/10
11 replies

Reuse Myth - can you afford reusable code?

In my Agile Business Conference present (“How much quality can we afford?”) I talked about the Reuse Myth, this is something always touch on when I deliver a training course but I’ve never taken time to write it down. Until now.

Jon Archer11/05/10
1 replies

Highly Distributed Scrum

I'm just about to finish sprint four as the Scrum Master for a team that has a higher than average number of distributed members. And I don’t just mean that we got two offices involved, one in the US and one in Europe or India. We have three software...

Mike Cohn11/04/10
0 replies

Choosing to Start Small or Go All In when Adopting Agile

Conventional, long-standing advice regarding transitioning to Scrum or any agile process has been to start with a pilot project, learn from it, and then spread agile throughout the organization. This approach is the frequently used start-small pattern in...

Jon Archer11/04/10
2 replies

Commitment: what can we really commit to?

I want to discuss a foundational topic that influences the management of software development: commitment. In particular I’m looking at this from the perspective of a business that develops software not for sale, but as an enabler to their operations. As...

David Bernstein11/04/10
1 replies

First Seek to Understand

Sometimes I like to start a project by doing a few hours of design and then spend the rest of an iteration building a proof of concept. Oftentimes I can get a tremendous amount of functionality roughed out in a system very quickly and then spend the next...