Introductory Series

Problems in Programmers’ Paradise

I was talking recently to a software company CEO who admitted – with some shame – that he had lost control of his Engineering team. Many of the projects and products in his company were drifting along with seemingly infinite schedules, infinite scope and infinite costs. Given that he [...]

Read more...

How Did I End Up Here?

Before we get into any discussion of frameworks or models, let me talk about the process that landed me here. Many, many years ago, I stumbled across my first struggling development team. After nine years as a relatively successful entrepreneur, the sale of the company and a year of [...]

Read more...

Go with the Flow

In my 29 years of building software, I’ve learned to view the Software Development process as a flow. I’m sure that this doesn’t seem particularly insightful, so bear with me. We all know that there is a standard flow from requirements to coding, testing and through to delivery to the customer. [...]

Read more...

The Flow, Part Deux

In the previous post, I introduced a simple flow model and suggested that the most important part of the Software Development process is the part related to interaction with the Customer. I will continue to build on the model – let’s first add one small component to signify the [...]

Read more...

The First Autopsy

In my previous posts, I presented a flow model to help understand the “Order of Operations” for diagnosing and fixing Engineering projects. As well, I presented the concept of the Customer Membrane and asserted that anything that doesn’t pass across this is generally not important. To allow a better [...]

Read more...