Abstract
It is widely used, to prevent failure in software development projects, project management and control techniques such as project reviews or project diagnosis. Unresolved problems and issues occurred in upstream phases such as requirements and specifications, could bring significant impacts on the project at downstream phases such as coding and testing. In response to our several non-trivial project failures, caused by such "escaped issues", we have designed our own diagnosis techniques and have implemented them in our project processes, which are to detect issues remaining in the project, before proceeding to downstream phases. In this paper, we discuss the technique, implementation, and its case studies on our real-life projects.
