.jpg)
When setting criteria for certifying skills or evaluating talent for projects the most common approach seems to be to try identify the "correct" behaviors from successful projects and build questioning around those behaviors. In the complex world of Enterprise software design and modernization, identifying all of the best behaviors (or finding successful projects) can be nearly impossible.
One solution is to turn the question upside down. Think about projects that have failed and identify behaviors and issues that caused the failure. You can then build the questioning around scenarios that detect the well defined "incorrect" behaviors that should be avoided. At the least, you are able to focus on what not to do, which, by process of elimination, leaves you with a collection of likely "correct" behaviors. Examples of many "incorrect" behaviors are documented in The Anti-Architect. Common behaviors in the software industry and why they are bad post.
