Thomas Grammig

A priori it is not possible to know how these parameters influence each other.  The relations among project participants determine how and when they are linked and when they are independent.  Without other indicators about project implementation, these parameters are often used to compare projects and infer what project design is appropriate.  Based on ethnographic work, I use observable interactional patterns in implementation 'Latent Processes' to describe, compare, design and document implementation.  These processes are latent because the individuals in a project can establish them.  By virtue of the definition, these latent processes allow to group parameters and relate them to a few contextual features.  However, this is impossible in a strong sense, the grouping is far from certain, more often than not the subsumptions are too partial.

So for illustration purposes only, I list below the latent processes that are often determinant for a project parameter and for the influence of the parameter alternative on implementation.  For each parameter and latent process I suggest one contextual feature that could in some cases allow comparisons because this feature is a major precondition why the latent process appears and what project participants do with it (or in other words why the parameter affects that latent process).  This is an illustration that might allow you to see whether your planning concern could benefit from the analysis of the latent processes.