We get things wrong before we get things right.

We get things wrong before we get things right.

We are still in the infancy of naming what is really happening on software development projects.

Focusing on skills, communications, and community allows the project to be more effective and more agile than focusing on processes and plans.

Agile is an attitude, not a technique with boundaries. An attitude has no boundaries, so we wouldn't ask 'can I use agile here', but rather 'how would I act in the agile way here?' or 'how agile can we be, here?'

I consider C++ the most significant technical hazard to the survival of your project and do so without apologies.

A well-functioning team of adequate people will complete a project almost regardless of the process or technology they are asked to use (although the process and technology may help or hinder them along the way).