While surfing the internet, looking for information about project measurement and iteration review criteria, I found the following
website.
I can strongly recommend this site for
Process Engineers, as it contains (and will contain) many interesting articles.
The following introduction is copied from the website:
The primary goal is to offer a place for Software Process Engineers (Architects of the development process) to obtain and offer ideas about the role of software Process Engineering. What works and what doesn't. Its also to share the software development process and how to apply it to teams in general. UML and modeling are a large part of this sites interest, but we try and cover all the disciplines, wherever we find useful information.
The site's aim is also to form a central collection point of relevant information about this emergent role of Process Engineering in teams doing software development. A place where useful material can be found by all people of all disciplines, both practical and theoretical, where newcomers to process can get help to get started or more experienced Process Engineers can benefit from others experience. A central junction to all things software process and software process related.