Quotes

Hippocrates on Clarity of Language

Apparently, even back in Hippocrates’ day (approximately 450 BC), business professionals had a tendency to confuse their stakeholders with acronyms, jargon, and odd colloquialisms, but one stands a far better chance of ensuring understanding with clear, simple, common language. Some things never change!

Read More

John Dewey on Starting with a Problem to be Solved

By starting with the problem, following up with objectives that articulate the definition of success, and then ensuring that requirements and subsequent solution artifacts and trace cleanly to, and support the original problem, we can avoid the confusion and wasted resources associated with deviating from or adding scope to the solution’s original problem and intent.

Read More

Benjamin L. Kovitz on Requirements

If human communication and human memory were perfect, we may not need deliberation and documentation of requirements. Alas, neither is close to true. It is the iterative exercise of modeling requirements, and then documenting them that enables shared understanding to be affirmed, and then shared with those who use requirements to guide design, construction and quality assurance. Requirements are the link between concept and product, and an important standard for measuring solution...

Read More

Alistair Cockburn – Agile is an Attitude

“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?’” — Alistair Cockburn I’d like to share one of my favorite agile quotes from Alistair Cockburn, because it summarizes my own perspective so well. In my observance, many fail to differentiate agile principles from agile methodologies, and end up with a prescriptive/dogmatic view of the correct way to do or be “agile” that misses the mark. Whether you’re working in an...

Read More