This quote came to mind as we’ve been going through an internal program’s requirements. One of my colleagues regularly refers to, and insists on, using the “Four Eyes” principle. In other words, one should always involve a second set of eyes to verify and validate work product. If the project team is the only arbiter of progress
Too often, the four eyes principle often only gets honored in quality control — e.g., during post-build testing processes. As my colleague’s insistence suggests, we find that an independent opinion is most valuable early in an initiative. For example, wouldn’t it be useful to have an independent validation during planning that the requirements and deliverables really represent (and will make real) the capabilites the project or program is intended to put in place?
It is tough enough to re-work a deliverable that doesn’t conform to requirements. It is worse to have to re-build a deliverable that had conformed to requirements, but find that those requirements were never valid in the first place.
Filed under: Program Management, Project Management, Quality Management, Requirements Management, Scope Management | Tagged: Four Eyes Principle, Pauline Kael, PM Quote of the Day, Quality Assurance, Quality Control |