This article describes how software process management could be improved by integration of development history recording. This idea is based on the observation that software process management focuses on activity patterns to be enforced, while the dependencies between documents and document parts produced in these activities are not considered. As a complement to that perspective, development history recording pays emphasis on the dependencies between documents. These dependencies are managed to find out whether or not documents are complete, transitively dependent, or related in other ways. Our approach is to combine both perspectives to enforce that software processes follow prescribed patterns and to manage dependencies between documents in order to ensure high-quality software.