I fully appreciate that language is always evolving, and as we make up new words and definitions they become added to the dictionary.

Reality Check – We Don’t Have Such Documentation

Okay, we did make a big assumption there. So they took me back to their real world.

All that writing?

When I persisted and suggested that requirements and architecture deliverables should be updated as part of the maintenance process, I had another protest. “All that writing? We don’t have time for that!”

I recently suggested to a team that they could make good use of Macroscope documentation in maintenance. There was instant skepticism. I was politely told that I was being naïve – everybody knows there is almost never any existing documentation and what there is will be out of date and can’t be trusted. And so there is no point in creating any new documentation – nobody would use it.

When I asked what they rely on to help with their maintenance work, I heard:

The Perception I was delivering a Macroscope intro course to a client a few weeks ago. One participant was puzzled by the disconnect between my pitch and what he was seeing in Macroscope. He said something like: You've been telling us all morning about doing the right things the right way, agility, eliminating waste, etc. but when I look at your Pr...