(R)evolutionary Changes
On codebetter.com Peter van Ooijen has published a blog entry on the evolutionary mechanisms one can find in the selection of tools and t...
Agile & Iterative Development
I just finished Agile & Iterative Development: A Manager's Guide by Craig Larman, the #8 person on the Top 25 list of Most Popula...
Top 25 Most Popular Software Engineers
Today I wanted to know which people are the most popular thinkers and writers in the field of software engineering. So I devised a hopele...
Flight of the Software Bugs
In this week's NewScientist magazine there's an article on software bugs in airplanes. Allow me to quote some parts of it: Softwa...
Traditional versus Agile: Where’s the Proof?
I have a bit of a problem with a recent survey in Dr. Dobb's Journal, carried out by Scott Ambler. The survey is supposed to show tha...
Competence Development: The Cone of Incompetence
Managers are responsible for competence development in an organization. But, for some reason, this doesn't always happen. Steve McCon...
(Very) Frequent Delivery
The frequent delivery principle in agile methods tells us that we should deliver products to our customers frequently. Quite often a fixe...
Complex Problems, Simple Solutions
"For every complex problem there is an answer that is clear, simple, and wrong." – H.L. Mencken Everytime when something ...
Professional Software Development
I just finished reading the book Professional Software Development, by Steve McConnell. I think Steve’s previous books (particularl...
The Software Project Cube
The iron triangle in project management tells us that a product is the result of scope, time and resources. Product = Scope * Time * Reso...
The Quality Improvement Gardener
As CIO in our company it is my job to make sure that quality improvement is an on-going process for which everyone feels responsible. In ...
The S-Curve in Software Projects
I think I have discovered something very significant today… While reading some articles dealing with measuring progress in a softwa...
  |