I will be co-moderating this board together with Stylianos, a formal introduction will come sometime later.
It appears to me that recently there has been a significant interest in designing new methods for verification planning. Classic methods of planning have been known to result in late releases (in some projects multiple months late) and unpredictable quality.
I believe this forum could become a catalyst to understanding the underlying problem we are trying to solve, and to both discuss and shape the solutions that are taking form.
To trigger some discussion, I want to pose a simple question: In what ways is Verification different from Design? (ways which might affect planning)
I believe if we clarify this question, we can better understand why some of the classic methods fail with verification.
Looking forward to your responses,
[ Previous post ran into formatting issues... ]Maybe some core differences are also cultural?If a project succeeds, the designer did a great job.If a projects fails, the verifier did a lousy job.Why then? Well, since we all want the design to succeed, verifiers are really going up against team spirit, aren't they? When a block is "done", they are the ones that make us go back to the drawing board and do it again. They are the ones that make us give management bad news when the week before we reported things were going great. And they are the ones that will never give us a straight answer! (does it work, are you done, when will you be done, what more do you need in order to be sure, etc...) ;-)At the end of the day, all too often verification engineers are the "bad guys". So maybe planning can be an effective way not only to predict, organize and manage the project, but also to help prevent those poor verification guys from getting all that bad vibe :-)PS: Feel free to substitute the <..> fields for your favorite metric of success...